Loading...
 
Skip to main content

System Workbench for STM32

Forum List Topic List

Forums » System Workbench for STM32 » Unable to debug with ST-LinkV2-1 » Unable to debug with ST-LinkV2-1
You are viewing a reply to Unable to debug with ST-LinkV2-1
 
Thread actions
Print this page
  • Print all pages

    • Unable to debug with ST-LinkV2-1

    Posted by SLESCISYS on 2015-10-30 08:06

    I also had this error! None of your proposed solutions helped!
    For me it worked to press the reset button on the evaluation board at the moment I started the debugger!

    Reads: 3379
    Posted by W.G. on 2015-10-30 16:58

    Hi, All,

    We really need downgrade stlink firmware from v2.1(latest) to v2?

    When you create sw4stm32 project for customised board, you need select correct stlink version for OpenOCD, and that selection will appear in .cfg.

    Under you project tree view, that .cfg file can be modified to match correct stlink version...

    Regards,
    W.G.


         Posted by grinch on 2015-10-31 16:28

    "We really need downgrade stlink firmware from v2.1(latest) to v2?
    When you create sw4stm32 project for customised board, you need select correct stlink version for OpenOCD, and that selection will appear in .cfg.
    Under you project tree view, that .cfg file can be modified to match correct stlink version..."

    When generating a project for nucleo, STLink V2.1 is properly set (as if putting V2.1 in custom board) but OpenOCD indicate a libusb problem and it doesn't work.
    It's working properly with a STlink V2 but not with a STLink V2.1.I even tried the custom thing with success..
    My V2 F4Discovery is working properly while my L15RE Nucleo fails.