Hello everyone,
Working on the STM32U5G9ZJT6Q on a custom board.
On STM32CubeProgrammer (V2.20), I face an unexpected issue when trying to program my board.
The ST-Link (official, V3PWR, power not used) simply cannot communicate anymore with the mcu with BOOT0=0 (tied with gnd). The stlink isn't broken as it still works on other custom boards.
Error: Unable to get core ID
Error: No STM32 target found! [...]
With the USB and PH3 BOOT0=1 (tied to Vdd), I can erase the chip and program it, however, when trying to run the program, the mcu resets and gets back into the idle usb waiting mode.
Here is the current consumption diagram without running after programming (left) and with running after programming (right). The base reset pattern for reference is the 3rd image.
The run seems to trigger the reset and put it back to idle/wait for device at the bootloader base address.
It's worth noting that with BOOT0=1, stlink still doesn't work.
I tried all possibilities to communicate with the board from stlink BOOT0=0, especially under reset.
I never had short-circuit on the board or at least not a prolonged one as I monitored the current consumption the whole time.The voltages are correct at the intended levels (VDDA, VDD, VDD core, ...).
It had been working before for weeks, and when I lost the possibility to communicate with the board (BOOT0=0, ST-LINK), the previous uploaded program was still running perfectly fine on the board (a simple internal DAC/VREF). I erased the memory from usb today so no code isn't running anymore.
The whole situation should mean (I hope) that the mcu in itself is not broken, or only the reset/run part, which I find difficult to believe.
