Cannot connect to STM32H747BIT6 anymore

[peter627]

I have been running into an issue with the cubeprogrammer very recently where I am unable to connect to my MCU anymore. I get the following log: using v2.22
12:41:28 : STM32CubeProgrammer API v2.22.0 | Windows-64Bits
12:43:17 : UR connection mode is defined with the HWrst reset mode
12:43:17 : ST-LINK SN : 34FF6A0630514B3840362443
12:43:17 : ST-LINK FW : V2J47S7
12:43:17 : Board : --
12:43:17 : Voltage : 3.56V
12:43:17 : SWD freq : 4000 KHz
12:43:17 : Connect mode: Normal
12:43:17 : Reset mode : Hardware reset
12:43:17 : Device ID : 0x450
12:43:17 : Revision ID : Rev V
12:43:17 : Error: Database: There's no active configuration for this device. All the 8 configurations are disabled!
12:43:17 : Debug in Low Power mode is not supported for this device.
12:43:18 : UPLOADING OPTION BYTES DATA ...
12:43:18 : Bank : 0x00
12:43:18 : Address : 0x5200201c
12:43:18 : Size : 308 Bytes
12:43:18 : Error: Uploading Option Bytes bank: 0 failed
12:43:18 : Error: Initializing the Option Bytes failed
12:43:18 : Error: Unable to get core ID
12:43:18 : Error: Unable to get core ID
12:43:18 : Warning: Connection to device 0x450 is lost
12:43:18 : Disconnected from device.
12:43:18 : Disconnected from device.


Mode hotplug:
12:44:17 : UR connection mode is defined with the HWrst reset mode
12:44:17 : ST-LINK SN : 34FF6A0630514B3840362443
12:44:17 : ST-LINK FW : V2J47S7
12:44:17 : Board : --
12:44:17 : Voltage : 3.57V
12:44:17 : SWD freq : 4000 KHz
12:44:17 : Connect mode: Hot Plug
12:44:17 : Reset mode : Hardware reset
12:44:17 : Device ID : 0x450
12:44:17 : Revision ID : Rev V
12:44:17 : Error: Database: There's no active configuration for this device. All the 8 configurations are disabled!
12:44:17 : Debug in Low Power mode is not supported for this device.
12:44:18 : UPLOADING OPTION BYTES DATA ...
12:44:18 : Bank : 0x00
12:44:18 : Address : 0x5200201c
12:44:18 : Size : 308 Bytes
12:44:18 : Error: Uploading Option Bytes bank: 0 failed
12:44:18 : Error: Initializing the Option Bytes failed
12:44:18 : Disconnected from device.

Mode under reset:
12:44:45 : UR connection mode is defined with the HWrst reset mode
12:44:45 : ST-LINK SN : 34FF6A0630514B3840362443
12:44:45 : ST-LINK FW : V2J47S7
12:44:45 : Board : --
12:44:45 : Voltage : 3.57V
12:44:45 : SWD freq : 4000 KHz
12:44:45 : Connect mode: Under Reset
12:44:45 : Reset mode : Hardware reset
12:44:45 : Device ID : 0x450
12:44:45 : Revision ID : Rev V
12:44:45 : Error: Database: There's no active configuration for this device. All the 8 configurations are disabled!
12:44:45 : Debug in Low Power mode is not supported for this device.
12:44:46 : UPLOADING OPTION BYTES DATA ...
12:44:46 : Bank : 0x00
12:44:46 : Address : 0x5200201c
12:44:46 : Size : 308 Bytes
12:44:46 : Error: Uploading Option Bytes bank: 0 failed
12:44:46 : Error: Initializing the Option Bytes failed
12:44:46 : Disconnected from device.


Any ideas?

[TDK]

Most likely:

How to unbrick an STM32H7 after setting the wrong ... - STMicroelectronics Community

[peter627]

That is not the issue. I tried setting boot high to connect via swd and I get the same errors. I have used that guide before but this is a different issue.

[TDK]

> 12:44:45 : Voltage : 3.57V

This seems high for a 3.3 V rail. Could something have happened to the board? How is it being used?

[peter627]

My power supply rails are fine, there are no shorts.

I was able to use this chip / connect to the board just fine a week ago and no I cannot despite not making any changes to the board.

If I power cycle the board with boot0 low, it only gives me this:

15:24:35 : UR connection mode is defined with the HWrst reset mode
15:24:35 : ST-LINK SN : 34FF6A0630514B3840362443
15:24:35 : ST-LINK FW : V2J47S7
15:24:35 : Board : --
15:24:35 : Voltage : 0.60V
15:24:35 : Error: Unable to get core ID
15:24:35 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication

If I hold boot0 high at power cycle then I get this again:

15:25:17 : UR connection mode is defined with the HWrst reset mode
15:25:17 : ST-LINK SN : 34FF6A0630514B3840362443
15:25:17 : ST-LINK FW : V2J47S7
15:25:17 : Board : --
15:25:17 : Voltage : 3.45V
15:25:17 : SWD freq : 4000 KHz
15:25:17 : Connect mode: Normal
15:25:17 : Reset mode : Hardware reset
15:25:17 : Device ID : 0x450
15:25:17 : Revision ID : Rev V
15:25:17 : Error: Database: There's no active configuration for this device. All the 8 configurations are disabled!
15:25:17 : UPLOADING OPTION BYTES DATA ...
15:25:17 : Bank : 0x00
15:25:17 : Address : 0x5200201c
15:25:17 : Size : 308 Bytes
15:25:17 : Error: Uploading Option Bytes bank: 0 failed
15:25:17 : Error: Initializing the Option Bytes failed
15:25:17 : Disconnected from device.

This is the new error:
Error: Database: There's no active configuration for this device. All the 8 configurations are disabled!

I saw a similar post talking about here: https://community.st.com/t5/stm32cubeprogrammer-mcus/quot-error-database-there-s-no-active-configuration-for-this/td-p/770170

But they said it was fixed with v2.22?

[TDK]

> 15:24:35 : Voltage : 0.60V

Obviously not enough voltage to run the chip.

> 15:25:17 : Voltage : 3.45V

And here the voltage is too high again.

It seems something funny is going on with your board. This is a hardware problem and not something than can be fixed by software settings. Look over your board power configuration again.

You didn't answer how it's being used, or what it's hooked up to. A full picture of the setup may help explain things.

[MHoll.2]

As TDK point's out why is the Voltage 0.6V when not pulling up the BOOT0 pin?

I think in the 2. case 3.45V is OK, but :

> 15:25:17 : Error: Database: There's no active configuration for this device. All the 8 configurations are disabled!

Is a known problem with some STM32CubeProgrammer version!

What version are You using?

[peter627 · Accepted solution]

GOT IT WORKING!

Turns out for some reason some of my pins on my stlink that are supposed to be ground are not actually working correctly. I swapped one of the ground pins and got the target voltage back up to where it was suppose to be and was able to pull boot high then connect and erase the chip. Now I can connect normally again.

Thank you