sierra29

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • sierra29
    Participant

    Problem solved:

    After some friggling tests i recognized that the reinstallation has removed my winusb driver. I´ve installed winusb again and the problem was solved.

    sierra29
    Participant

    Hello,

    I first had the same problem, but after doing above steps to solve the problem it did not dissapear but another error message appears now:

    Licensed under GNU GPL v2
    For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
    Info : auto-selecting first available session transport “hla_swd”. To override use ‘transport select <transport>’.
    Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
    adapter speed: 1000 kHz
    adapter_nsrst_delay: 100
    none separate
    Info : Unable to match requested speed 1000 kHz, using 950 kHz
    Info : Unable to match requested speed 1000 kHz, using 950 kHz
    Info : clock speed 950 kHz
    in procedure ‘init’
    in procedure ‘ocd_bouncer’

    and a message box tells me “Open OCD exited with code 1. Please check your settings”

    But before the last update all my projects run fine with exactly this settings and project files, now not one is working.

    I use stm32F1xx devices with a ST-Link v2, what big shit happened there? Is there a solution to go back to my old configuration tho get my pending projects working again?

    Thank you

    in reply to: STM32F407VG without HAL but StdFWLib #8021
    sierra29
    Participant

    P R O B L E M   S O L V E D

    I´ve got the needed tip in another Forum, but I want to describe the solution in short:

    When creating a new project, you can decide to create a c-file or a c++ file. When you create a C-File (that what I need) you can select the type of template. When you let the radio button on C++-File (what I did, but non meant) you get only a template based on the HAL.

    So this is solved.

    in reply to: Linker Error on sprintf #3106
    sierra29
    Participant

    OK, thank you. Now i know why 😉
    This behavior was a little strange for me, because until now i used Keil uVision4 MDK ARM, where an printf to uart or sprintf to string was implemented.
    So I can create a workaround.
    Thank´s again….

Viewing 4 posts - 1 through 4 (of 4 total)