Got error like ST-LINK error (DEV_TARGET_NOT_HALTED) when to flash the program.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-01-16 12:54 AM
Hi,
I was trying to disable Tzen in my nucleo-l55ze-q (stm32l55), but before disabling i forgot to flash toggle gpio programmer into board, and tried to set RDP to 55 and i clicked apply,
From that moment it is not able to detect the STlink!..
please give me any suggestions .
Thanks and regards
Teju S H
Solved! Go to Solution.
- Labels:
-
ST-Link
-
STM32CubeProgrammer
-
STM32L5 Series
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-01-21 11:21 AM
Hi @Tsh.1​
This is an expected situation in this case.
The tool explicitly give a recommendation to flash a valid secure code jumping to non secure code =)
The only way to recover the board is to boot on RSS : BOOT0 pin PH3 to VDD (hope you are using boot selection through Boot 0).
Try this please and tell me if it solves your issue.
Houda-
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-01-17 10:53 AM
Try to connect under reset or get the device into bootloader mode and then connect the debugger.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-01-17 6:24 PM
Hi @Uwe Bonnes​
i have tried connecting under reset it doesnt worked .....
and now i have connected boot0 pin to vdd and now i am able to flash the bin files as connected to hotplug......
but i am not getting any data in serial port....
can erasing chip will slove this..??
Please suggest me regarding this..
Thanks and Regards
Teju S H
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-01-21 11:21 AM
Hi @Tsh.1​
This is an expected situation in this case.
The tool explicitly give a recommendation to flash a valid secure code jumping to non secure code =)
The only way to recover the board is to boot on RSS : BOOT0 pin PH3 to VDD (hope you are using boot selection through Boot 0).
Try this please and tell me if it solves your issue.
Houda-
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-08-02 12:04 PM
I am facing the same situation. Can you give some more detail about this boot process? I ensured the boot option was checked prior to making the change to RDP.
Edit: I found the relevant section in the manual for the kit, section 6.4.2 Boot from RSS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-08-12 6:02 AM
I had the same issue after flashing a corrupted build.
The solution is to select Hardware reset under Reset mode in STM32Cube Programmer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-05-08 3:47 AM
I have similar issue, using STM32F412G-DISCO board. It worked OK, but while trying to learn how to use the flash memory, suddenly it stopped work.
how cam I boot it?
