Loading...
 

Zephyr project on STM32

   Zephyr Workbench, a VSCode extension to manage Zephyr on STM32.
It enables users to easily create, develop, and debug Zephyr applications.
Main features:
  • Install host dependencies.
  • Import toolchain and SDK.
  • Create, configure, build and manage apps.
  • Debug STM32.
You can directly download it from the VSCode marketplace
For more details, visit the Zephyr Workbench

System Workbench for STM32

Forum List Topic List

You are viewing a reply to Can't run debugger - It was working  

Can't run debugger - It was working

Posted by dnbharrin on 2016-11-28 19:13

In my case on the Nucleo 64 STM32L476 board, the debugger was working the previous day. Then today, I got the:

“in procedure ‘ocd_bouncer’

    • OpenOCD init failed **

shutdown command invoked”

error.

All I did was disconnect board from computer and reconnect. Initiated debug and it worked fine again.

Too bad all errors aren’t that easy to solve.

Reads: 2583
Link
Posted by dnbharrin on 2016-11-30 20:10

Debugger was running, now I can’t get it running again. Same board, same configuration, same project, same program with absolutely no changes. Why is it different now!!!
Here is the error box I get when I try to run debug with all the default settings for the Ac6 STM32 Debugging configuration:

Error in final launch sequence
Failed to execute MI command:
load C:\STM32_Nucleo_Projects\GPIO_Test1_20161124\Debug\GPIO_Test1_20161124.elf

Error message from debugger back end:
Error erasing flash with vFlashErase packet
Error erasing flash with vFlashErase packet

Note that Build and Run were accomplished with no errors.

Also I get a strange tab in the Console window labeled “0x800171a”. It contains:

No source available for “0x800171a”

in red font.

Link
Posted by dnbharrin on 2016-12-06 01:10

Found answer to problem in another thread:

Use Task Manager to kill any openocd.exe processes that are still running.

Debug ran fine after killing the openocd.exe process.

Link