STM32H750VB custom board isn't programming with ST-Link

PNare · ‎2020-08-07

Hello,

We've developed a custom board with STM32H750VB at the core. The relevant page of the schematic is attached. It is not communicating properly with the ST-Link on a STM32L053R8 Nucleo board. STMCube Programmer is the software used on Windows. The SWD connections are fine since it is able to read back the version and the device ID sporadically. The option bytes aren't being read and that's the error showing. Flash erase isn't working at all. Please let me know the possible issue. The log is below

Thanks, Prithvi

19:02:29:293 : STLinkUSBDriver.dll loaded
19:02:29:294 : STLinkUSBDriver.dll loaded
19:02:29:294 : ST-LINK SN  : 066EFF535254887767183010
19:02:29:294 : ST-LINK FW  : V2J37M26
19:02:29:294 : Board       : NUCLEO-L053R8
19:02:29:295 : Voltage     : 3.24V
19:02:29:304 : SWD freq    : 1800 KHz
19:02:29:304 : Connect mode: Normal
19:02:29:305 : Reset mode  : Software reset
19:02:29:308 : Device ID   : 0x450
19:02:29:318 : Revision ID : Rev V
19:02:29:335 : Buffer program...
19:02:29:338 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:02:29:338 : Reading data...
19:02:29:339 : r ap 0 @0x58000528 0x00000004 bytes Data 0x00000000
19:02:29:342 : Buffer program...
19:02:29:344 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:02:29:344 : Buffer program...
19:02:29:348 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:02:29:349 : Buffer program...
19:02:29:349 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:02:29:349 : Reading data...
19:02:29:349 : r ap 0 @0x58000528 0x00000004 bytes Data 0x00000000
19:02:29:349 : Buffer program...
19:02:29:350 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:02:29:350 : Reading data...
19:02:29:352 : r ap 0 @0x58000528 0x00000004 bytes Data 0x00000000
19:02:29:357 : Buffer program...
19:02:29:357 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:02:29:357 : Reading data...
19:02:29:358 : r ap 0 @0x58000528 0x00000004 bytes Data 0x00000000
19:02:29:358 : Buffer program...
19:02:29:358 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:02:29:358 : Reading data...
19:02:29:358 : r ap 0 @0x58000528 0x00000004 bytes Data 0x00000000
19:02:29:367 : Reading data...
19:02:29:379 : r ap 0 @0x1FF1E880 0x00000004 bytes Data 0x00000080
19:02:29:383 : Reading data...
19:02:29:383 : r ap 0 @0x1FF1E880 0x00000004 bytes Data 0x00000080
19:02:29:384 : Buffer program...
19:02:29:384 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:02:29:384 : Reading data...
19:02:29:384 : r ap 0 @0x58000528 0x00000004 bytes Data 0x00000000
19:02:29:384 : Database: There's no active configuration for this device. All the 8 configurations are disabled!
19:02:29:395 : flash loader C:\Program Files (x86)\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/FlashLoader/0x450.stldr is loaded
19:02:29:409 : Reading data...
19:02:29:420 : r ap 0 @0x0000FFFF 0x00000004 bytes Data 0x00000000
19:02:29:420 : failed to read the requested memory content
19:02:29:772 : UPLOADING OPTION BYTES DATA ...
19:02:29:773 :   Bank          : 0x00
19:02:29:773 :   Address       : 0x5200201c
19:02:29:773 :   Size          : 308 Bytes
19:02:29:774 : Reading data...
19:02:29:774 : r ap 0 @0x5200201C 0x00000134 bytes Data 0x00000000
19:02:29:774 : Error: Uploading Option Bytes bank: 0 failed
19:02:29:807 : Error: Initializing the Option Bytes failed
19:02:29:840 : Disconnected from device.
19:02:29:844 : Error: Connection to target must be established before performing the read command.
19:03:47:957 : STLinkUSBDriver.dll loaded
19:03:47:957 : STLinkUSBDriver.dll loaded
19:03:47:957 : ST-LINK SN  : 066EFF535254887767183010
19:03:47:957 : ST-LINK FW  : V2J37M26
19:03:47:958 : Board       : NUCLEO-L053R8
19:03:47:958 : Voltage     : 3.25V
19:03:47:958 : SWD freq    : 1800 KHz
19:03:47:958 : Connect mode: Normal
19:03:47:958 : Reset mode  : Software reset
19:03:47:987 : Device ID   : 0x450
19:03:47:989 : Revision ID : Rev V
19:03:47:989 : Buffer program...
19:03:47:989 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:03:47:990 : Reading data...
19:03:47:990 : r ap 0 @0x58000528 0x00000004 bytes Data 0x00000004
19:03:47:993 : Buffer program...
19:03:47:994 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:03:47:994 : Reading data...
19:03:47:994 : r ap 0 @0x58000528 0x00000004 bytes Data 0x00000000
19:03:47:994 : Buffer program...
19:03:47:995 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:03:47:995 : Reading data...
19:03:48:005 : r ap 0 @0x58000528 0x00000004 bytes Data 0x00000000
19:03:48:011 : Reading data...
19:03:48:011 : r ap 0 @0x1FF1E880 0x00000004 bytes Data 0x00000080
19:03:48:011 : Database: Config 2 is active.
19:03:48:020 : flash loader C:\Program Files (x86)\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/FlashLoader/0x450.stldr is loaded
19:03:48:035 : Reading data...
19:03:48:036 : r ap 0 @0x1FF1E880 0x00000004 bytes Data 0x00000080
19:03:48:036 : failed to read the requested memory content
19:03:48:245 : UPLOADING OPTION BYTES DATA ...
19:03:48:246 :   Bank          : 0x00
19:03:48:246 :   Address       : 0x5200201c
19:03:48:246 :   Size          : 308 Bytes
19:03:48:247 : Reading data...
19:03:48:247 : r ap 0 @0x5200201C 0x00000134 bytes Data 0x000000F0
19:03:48:247 : Error: Uploading Option Bytes bank: 0 failed
19:03:48:273 : Error: Initializing the Option Bytes failed
19:03:48:297 : Disconnected from device.
19:03:48:301 : Error: Connection to target must be established before performing the read command.
19:04:07:245 : STLinkUSBDriver.dll loaded
19:04:07:247 : STLinkUSBDriver.dll loaded
19:04:07:248 : ST-LINK SN  : 066EFF535254887767183010
19:04:07:248 : ST-LINK FW  : V2J37M26
19:04:07:249 : Board       : NUCLEO-L053R8
19:04:07:250 : Voltage     : 3.25V
19:04:07:314 : SWD freq    : 1800 KHz
19:04:07:315 : Connect mode: Under Reset
19:04:07:315 : Reset mode  : Hardware reset
19:04:07:318 : Device ID   : 0x450
19:04:07:319 : Revision ID : Rev V
19:04:07:319 : Buffer program...
19:04:07:320 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:04:07:320 : Reading data...
19:04:07:320 : r ap 0 @0x58000528 0x00000004 bytes Data 0x00000000
19:04:07:321 : Buffer program...
19:04:07:321 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:04:07:321 : Buffer program...
19:04:07:322 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:04:07:322 : Buffer program...
19:04:07:323 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:04:07:323 : Reading data...
19:04:07:323 : r ap 0 @0x58000528 0x00000004 bytes Data 0x00000000
19:04:07:323 : Buffer program...
19:04:07:324 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:04:07:324 : Reading data...
19:04:07:324 : r ap 0 @0x58000528 0x00000004 bytes Data 0x00000000
19:04:07:325 : Buffer program...
19:04:07:325 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:04:07:326 : Buffer program...
19:04:07:326 : w ap 0 @0x580244F4 0x00000004 bytes Data 0x00000002
19:04:07:326 : Reading data...
19:04:07:327 : r ap 0 @0x58000528 0x00000004 bytes Data 0x00000000
19:04:07:327 : Reading data...
19:04:07:327 : r ap 0 @0x1FF1E880 0x00000004 bytes Data 0x00000080
19:04:07:328 : Reading data...
19:04:07:328 : r ap 0 @0x1FF1E880 0x00000004 bytes Data 0x00000080
19:04:07:328 : Database: There's no active configuration for this device. All the 8 configurations are disabled!
19:04:07:329 : flash loader C:\Program Files (x86)\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/FlashLoader/0x450.stldr is loaded
19:04:07:329 : Reading data...
19:04:07:329 : r ap 0 @0x0000FFFF 0x00000004 bytes Data 0x00000000
19:04:07:329 : failed to read the requested memory content
19:04:08:039 : UPLOADING OPTION BYTES DATA ...
19:04:08:039 :   Bank          : 0x00
19:04:08:040 :   Address       : 0x5200201c
19:04:08:040 :   Size          : 308 Bytes
19:04:08:041 : Reading data...
19:04:08:041 : r ap 0 @0x5200201C 0x00000134 bytes Data 0x000000F0
19:04:08:042 : Error: Uploading Option Bytes bank: 0 failed
19:04:08:081 : Error: Initializing the Option Bytes failed
19:04:08:114 : Disconnected from device.
19:04:08:120 : Error: Connection to target must be established before performing the read command.

PNare · ‎2020-08-07

Also, the BOOT0 pin is grounded in the above circuit in the assembly. Thanks.

Tesla DeLorean · ‎2020-08-07

Consider using stand-alone ST-LINK

For Nucleo, double check the local target is disconnected via jumpers

Check supplies on your own board, double check voltages/capacitors on VCAP pins, and what's happening with the NRST line.

Any watchdog hardware on the board?

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

Tesla DeLorean · ‎2020-08-07

The blank device should enter the system boot loader, you should perhaps try UART based connectivity to establish signs-of-life, and inject test code.

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

TDK · ‎2020-08-07

Is the ST-Link on the Nucleo disconnected from the on-board STM32 chip? Schematic seems fine.

If you feel a post has answered your question, please click "Accept as Solution".

PNare · ‎2020-08-07

Thanks a lot everyone for the replies. It is working now (yay!), and we don't know why it wasn't working earlier.

It is very strange because in the log that I posted you can see

19:04:07:318 : Device ID   : 0x450
19:04:07:319 : Revision ID : Rev V

Which says that it was able to recognize that it is talking to a STM32H750 chip but it was failing afterwards.