STM32H503 UART BOOTLOADER TROUBLE

[Mike1992]

Hello everyone, I have a problem with the bootloader of the stm32h503 microcontroller. I can't get a response from the stm32 via any of the UART interfaces. I tried different baud rates (9600,57600,115200) but I don't get an ACK from the STM32H503 in response to 0x7F via any of them.

The BOOT0 pin is set to a logical one, and then the microcontroller is reset using the nRST pin. I tried re-soldering the H503 to a new one, but there is no difference. The F103 responds perfectly to the same requests and correctly displays the CHIP ID with the same adapter and connection.
USART1 on the H503 is working properly, since it is used to transfer data between the 503 and the ESP32.
Please tell me what the problem could be and how to solve it?

I am attaching a screenshot from a logic analyzer, the first signal is pin BOOT0, the second is RESET, the third and fourth are USART

[TDK]

Are you using pins supported by the bootloader as outlined in AN2606? Which ones?

Try waiting longer between NRST high and sending 0x7F.

[Tesla DeLorean]

Does it work with SWD/JTAG ?

Show your FULL wiring, or schematic around the H503 ?

It won't work if the part isn't viable. So look at power supply connections, main supply, analogue.

Check state of NRST pin

Check voltage on VCAP pins is present

Check other pins described in AN2606 as possible noise sources, Especially UART RX inputs like GPS/GNSS that might chirp at start-up. The detection methods in the System Loader are one-shot, so if it's picking up noise you'll have to reset and start-over. You need to suppress other noise sources.

It might take a while for the System Loader to start completely, ie bring up clocks and PLL. Give it several hundred milliseconds

The 0x7F pattern is at 8E1, a TIM is being used to measure the pattern as a means to auto-baud