Skip to main content
Tsh.1
Associate
January 16, 2021
Solved

Got error like ST-LINK error (DEV_TARGET_NOT_HALTED) when to flash the program.

  • January 16, 2021
  • 4 replies
  • 4280 views

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

Best answer by Houda GHABRI

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-

4 replies

Uwe Bonnes
Chief
January 17, 2021

Try to connect under reset or get the device into bootloader mode and then connect the debugger.

Tsh.1
Tsh.1Author
Associate
January 18, 2021

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

Houda GHABRI
Houda GHABRIBest answer
ST Employee
January 21, 2021

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-

MSher.1
Associate II
August 2, 2021

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

Hueli.1
Associate III
August 12, 2022

I had the same issue after flashing a corrupted build.

The solution is to select Hardware reset under Reset mode in STM32Cube Programmer0693W00000QNa8kQAD.png