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


Degugging locks up at "Initializing PLDs..."

Hello Laurent,
 
thanks for replying.
 
I made sure ST-Link Utility did not have any conncetion anymore before using Debugger. Does ST-Link Utility has to run or not ? Nevertheless I tried the following sequence
- Before Starting ST-Link Utility : failed on Initializing PLDs...
- ST-Link Utility started but not yet connected : failed on Initializing PLDs...
- Connecting the board took two attempts before successful .
- ST-Link Utility started and connected: failed at
Debug: 261 83 hla_transport.c:171 hl_transport_init(): current transport hla_swd
Debug: 262 83 hla_interface.c:44 hl_interface_open(): hl_interface_open
Debug: 263 83 hla_layout.c:42 hl_layout_open(): hl_layout_open
Debug: 264 83 stlink_usb.c:1698 stlink_usb_open(): stlink_usb_open
Debug: 265 83 stlink_usb.c:1716 stlink_usb_open(): transport: 1 vid: 0x0483 pid: 0x3748 serial:
Error: 266 287 libusb1_common.c:97 jtag_libusb_open(): libusb_open() failed with LIBUSB_ERROR_ACCESS
Error: 267 287 stlink_usb.c:1729 stlink_usb_open(): open failed
Debug: 268 287 hla_layout.c:49 hl_layout_open(): failed
Debug: 269 287 command.c:628 run_command(): Command failed with error code -4
User : 270 287 command.c:689 command_run_line(): in procedure ‘init’
in procedure ‘ocd_bouncer’
Debug: 271 288 command.c:628 run_command(): Command failed with error code -4
User : 272 288 command.c:689 command_run_line():
Debug: 273 288 hla_interface.c:119 hl_interface_quit(): hl_interface_quit
- ST-Link Utility no more running: failed on Initializing PLDs...
 
I am using
Eclipse IDE for C/C++ Developers
Version: Mars.2 Release (4.5.2)
Build id: 20160218-0600
 
On update, I did not receive any updates, hence I assume I have the latest version
  ARM Compiler for MCU (for Windows 32 bits) 1.7.0.201602121829            fr.ac6.feature.mcu.externaltools.armnone.win32.feature.group   Ac6
  Eclipse IDE for C/C++ Developers      4.5.2.20160218-0600     epp.package.cpp         null
  External Tools for Windows (32 bits)   1.3.0.201507241045      fr.ac6.feature.mcu.externaltools.win32.feature.group            Ac6
  OpenOCD (for Windows 32 bits)         1.10.0.201607261143            fr.ac6.feature.mcu.externaltools.openocd.win32.feature.group   Ac6
  OpenSTM32 IDE         1.10.0.201607251855    fr.ac6.feature.mcu.ide.feature.group     Ac6
  OpenSTM32 Linker Script editor          1.7.0.201602121829      fr.ac6.feature.mcu.ldscript.feature.group           Ac6
  OpenSTM32 Remote debugging support        1.10.0.201607251855    fr.ac6.feature.mcu.debug.feature.group Ac6
 
Best regards

Michael