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


Can't run debugger - It was working

I have more information. First I was able to confirm JackN’s observation that an improper break point will stop the debug. In this case I put a breakpoint on a comment line and debug fails. Removing that breakpoint allowed success on the Nucleo board. At this point I can debug the Nucleo board but not the L476_Discovery Board.

I got the debug log from OpenOCD and this is the important error:
Debug: 256 29 stlink_usb.c:1602 stlink_usb_open(): stlink_usb_open
Debug: 257 29 stlink_usb.c:1619 stlink_usb_open(): transport: 1 vid: 0x0483 pid: 0x374b serial:
Error: 258 270 stlink_usb.c:1632 stlink_usb_open(): open failed
Debug: 259 270 hla_layout.c:49 hl_layout_open(): failed
Debug: 260 270 command.c:628 run_command(): Command failed with error code -4
User : 261 270 command.c:689 command_run_line(): in procedure ‘init’
in procedure ‘ocd_bouncer’

Device manager sees the programming device like this:
USB\VID_0483&PID_3748

Is it significant that OpenOCD thinks the PID is 0x374B and Device Manager thinks PID is 0x3748? B versus 8?
I should also say this is 64bit Windows 7 on a Dell Latitude laptop. STM ST-Link Utility loads the L476 fine.

Can anyone suggest further troubleshooting?