STM32WB55RE

bytespectrum · ‎2024-01-29

Hello,

I am using STM32WB55RE (MCU) in my custom HW.

For testing the HW I have flashed BLE_HeartRateFreeRTOS example firmware.

"..\..\STM32Cube_FW_WB_V1.16.0\Projects\P-NUCLEO-WB55.Nucleo\Applications\BLE\BLE_HeartRateFreeRTOS"

I am getting the advertisement of the HRSTM. So HW is working now but some how I am not able to reflash it.

Looks like my flashing setup stopped working.

I have rechecked all the flashing connections.

1. NRST

2. SYS_JTCK_SWCLK (PA14)

3. SYS_JTMS_SWDIO (PA13)

4. GND

Can you please help to fix this issue?

Thanks.

bytespectrum · ‎2024-01-31

I have figured out the problem, it is not related to ST-Link.
The reset IO was staying high all the time, so manually grounded the reset IO for very small amount of time, then flashing works fine now.

Steps to solve:
1. Connect JTAG cables, split Reset io into two cables one to regular device IO pin and another should be used for manually grounding the IO
2. Keep the Reset IO grounded and then click click on Connect button on STM32CubeProgrammer.
3. Unground the Reset IO after 1-2 seconds(before Connect Timeout) occurs.
4. device will flash successfully.

Possible reason, the Reset IO might held high either in the Heartrate firmware or hardware.

View solution in original post

STTwo-32 · ‎2024-01-31

Hello @bytespectrum

Are you using a genuine ST-LINK to flash your firmware?

If so, can you double-check your wires?

Please check those two proposals.

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Andrew Neil · ‎2024-01-31

@bytespectrum wrote:
I am not able to reflash it.

Please give more details of what, exactly, you've tried, and what happens.

Any error messages?

Can you debug?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

bytespectrum · ‎2024-01-31

Error: No STM32 target found!

bytespectrum · ‎2024-01-31

I have figured out the problem, it is not related to ST-Link.
The reset IO was staying high all the time, so manually grounded the reset IO for very small amount of time, then flashing works fine now.

Steps to solve:
1. Connect JTAG cables, split Reset io into two cables one to regular device IO pin and another should be used for manually grounding the IO
2. Keep the Reset IO grounded and then click click on Connect button on STM32CubeProgrammer.
3. Unground the Reset IO after 1-2 seconds(before Connect Timeout) occurs.
4. device will flash successfully.

Possible reason, the Reset IO might held high either in the Heartrate firmware or hardware.

Andrew Neil · ‎2024-01-31

The ST-Link should be able to assert the NRST line.

Did you have the ST-Link configured to do a hardware reset?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

bytespectrum · ‎2024-01-31

Hey Andrew Neil,

@Andrew Neil wrote:
The ST-Link should be able to assert the NRST line.
Did you have the ST-Link configured to do a hardware reset?

Yes, I have configured the hardware reset from the debug configuration, I have also tried hardware reset and other options from STM32CubeProgrammer options, but it didn't work.

So I had to do it manually.

Thanks