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


You are viewing a reply to Can't enter to debug session  

Re: Re: Re: Can't enter to debug session

Hi,

I’m having same issue on windows xp with Nucleo-L053R8.

Here is some debug data I could get:

Open On-Chip Debugger 0.9.0-dev-00101-g3a546c5-dirty (2014-09-23-14:54)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : This adapter doesn’t support configurable speed
Info : STLINK v2 JTAG v20 API v2 SWIM v4 VID 0x0483 PID 0x374B
Info : using stlink api v2
Info : Target voltage: 3.238345
Error: init mode failed
in procedure ‘init’
in procedure ‘ocd_bouncer’
in procedure ‘transport’
in procedure ‘init’


Prompted error :
--------
Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:3333

Error message from debugger back end:
localhost:3333: The system tried to join a drive to a directory on a joined drive.
localhost:3333: The system tried to join a drive to a directory on a joined drive.


This board should work, isn’t ? Do you have an idea of what should be done ?

Thanks,
Regards,
Sylvain

The same problem here, only with the F05-Nucleo!

I also got the same problem. I am using stm32f4Discovery board(stm32f407vg) which is having ST-Link V2(not ST-link V2-1) Flasher/Debugger. But the Debugger configuration in eclipse is uisng ST-Linkv2-1 openocd config in it’s config file.

I just chaned the openocd config file in plugins directory(file path: /plugins/fr.ac6.mcu.debug_1.8.0.201603291114/resources/openocd/scripts/st_board/stm32f407g_disc1.cfg).

I modified “source find interface/stlink-v2-1.cfg” to “source find interface/stlink-v2.cfg” in the above file.

After this change I am able to connect to the board and everything is fine.

-Harsha

France

Hi Harsha,

Be careful, looking at your message it seems that you are using an stm32f4discovery board, which indeed includes an STLink-V1 probe, but the script you use is the one for the stm32f407g-disc1, which use the same chip, but includes an STLink-V2-1...

That mean that you probably select the wrong board when creating your project... You should probably delete (do not click “Delete content on disk”) and re-create your project (in the same directory) using the correct board, then port the changes you may have done to the project properties; changes to source files (edits, adds, etc.) will be kept automatically.

Hope this helps,

Bernard (Ac6)


 

Newest Forum Posts

  1. Монтаж камина с грилем в Москве - установка и барбекю by KpddomErorb, 2025-05-10 18:28
  2. SPI on Nucleo_STMH533RE by royjamil, 2025-05-04 20:13
  3. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-25 07:37
  4. SPI on Nucleo_STMH533RE by royjamil, 2025-03-23 11:31
  5. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-23 09:33
  6. Configuring DMA for ADC in SW? by sam.hodgson, 2025-03-04 12:58
  7. Build a project in "release" mode by info@creosrl.it, 2025-02-20 18:12
  8. Build a project in "release" mode by info@creosrl.it, 2025-02-20 17:05
  9. Build a project in "release" mode by tang, 2025-02-20 10:36
  10. Build a project in "release" mode by info@creosrl.it, 2025-02-19 17:35

Last-Modified Blogs