ST-Link broken after upgrade on Nucleo card

[Cedric Boudinet]

Hello

When I try to connect to my Nucleo board, I have the following message:

Error in initializing ST-LINK device.

Reason: (4) No device found on target.

I think I have this error message because I didn't disconnect the board physically before upgrading the firmware.

I don't know what is broken the ST-link or the nucleo itself?

Is there a way to repair the board?

Bests

[Uwe Bonnes]

It looks like the stlink is still available, but not the connection to the target. Probably no need to fear for the stlink.

[Cedric Boudinet]

Yes it seems, since the board is still recognized by the computer.

Does it means the target is dead or is there a way to use it again?

Regards

[Uwe Bonnes]

Doubel check connections and setup.

[Cedric Boudinet]

I did.

[Tesla DeLorean]

Pull BOOT0 pin high so it stops running your code, connect with ST-LINK Utilities and erase.

Could try connect under reset or low power options.

Your code likely disables SWD interface or reconfigures debug pins. Or goes into low power state.​

[Cedric Boudinet]

I tried as you described, I still have the same error.

[Tesla DeLorean]

Definitely pointing to the STM32 chip being dead/unresponsive

[Brian TIDAL]

Hi,

can you check that the power LED (LD3) is ON (RED LED). If not, can you check that the JP6 (IDD) is properly ON (remove it and put it back) and that JP5(PWR) is in the proper position (U5V).

Rgds

BT

[Cedric Boudinet]

My card is a Nucleo144, not a Nucleo64. I check that all the jumpers configuration are in their default state.

LD4 is red and LD6 lights up.

[Brian TIDAL]

​Hi,

which STM32 Nucleo-144 boards do you have? NUCLEO-F207ZG, NUCLEO-F303ZE, NUCLEO-F412ZG, NUCLEO-F413ZH, NUCLEO-F429ZI, NUCLEO-F439ZI, NUCLEO-F446ZE, NUCLEO-F722ZE, NUCLEO-F746ZG, NUCLEO-F756ZG, NUCLEO-F767ZI and NUCLEO-H743ZI? Is there any HW modification (e.g. Solder Bridge changed) ? Any modification in the jumper settings compared to default ones? any thing (shields) connected to the board?

As explained by Clive, the Serial Wire Debug is probably disabled by your software. Have you properly tried to put a jumper between pins 5-7 of CN11 in order to set BOOT0 to 1 and have the default bootloader running? Make sure to reset or power cycle.

Have you tried to Connect under reset with ST-Link utilities?

Rgds

BT

[Cedric Boudinet]

Hi

It is a NUCLEO-F429ZI.

There are two HW modifications: I put off SB12 (for external Vref) and SB121. I put on SB122.

The card was still working after the HW modification.

No shield is connected to the board and all jumpers are in their default config.

I tried to short pins 5 and 7 of CN11.

I tried all the modes and reset modes when connecting with STM32CubeProgrammer.

Bests

[Brian TIDAL]

Hi,

some additional tests before autopsy:

• can you plug an ammeter instead of JP5 and check whether there is still some life here (possibly remove SB13 as explained in UM1974).
• can you try to revert back the SB12 modification or provide VDDA/VREF though pin6 of CN7

How is provided your VREF?

Have you connected a shield that might have provided a VREF while SB12 was ON, possibly damaging the board?

Rgds

BT

P.-S. Ense3 is not so far. Just walking 500m...

[Cedric Boudinet]

Thanks a lot, it works by providing a VREF again.

I put an ammeter and when there is no VREF, the ammeter shows 0A. It seems that the MCU cannot start without AVDD.

It has no link with the firmware upgrade, but from the fact that I removed my shield providing the VREF as the same time.

[Brian TIDAL]

Hi,

good to know this is working again.

See RM0090 §5.2.1 "The device remains in Reset mode when VDD/VDDA is below a specified threshold,"

Rgds

BT

[Tesla DeLorean]

What firmware did you update? The firmware on the ST-LINK or that of the Target?

[Cedric Boudinet]

The ST-link one I guess, I used STLinkUpgrade.