2025-02-18 12:42 PM
Hello!
New to the STM controllers, failed to realize that PA13 was necessary to connect the debugger and was quite dismayed to realize my mistake after looking to program it as a GPIO.
I have tried connecting with the IDE and Programmer alike, both with BOOT0 (PA13) to Vdd and without. My latest attempt is shown below which I found another thread about -- even with PA13 shorted to 3.3V and shorted to GND I see the same result -- have I killed my poor STM?
I'm using the NUCLEO-G031J6 while I get accustomed to this microcontroller.
Any advice would be greatly appreciated! Thanks
Solved! Go to Solution.
2025-02-19 06:48 AM
I got it working thanks to this thread:
https://community.st.com/t5/stm32-mcus-products/can-t-program-stm32g031j6-disco-no-device-found-on-target-quot/m-p/98012#M14488
Have to jiggle Idd jumper on board, disconnect and connect quickly simultaneously as the Programmer ST-Link is trying to connect -- kludgy but worked !
2025-02-18 01:40 PM - edited 2025-02-18 01:40 PM
> BOOT0 (PA13)
PA14 is BOOT0, not PA13. Tie to the VDD during reset to enter the bootloader. Once in the bootloader, you can connect over SWD and erase the chip to recover.
I can't find a NUCLEO-G031J6 board. Is this perhaps the NUCLEO-G031K8? Same answer applies.
2025-02-19 06:32 AM
Thank you for the feedback!
I now have pin 8 shorted to Vdd, but the response is exactly the same. I've also made sure to update my STLink. It definitely recognizes the ST-Link, but the connect button gives me this response below.
Have I killed my poor boy?
Thank you for your considerations
N
2025-02-19 06:48 AM
I got it working thanks to this thread:
https://community.st.com/t5/stm32-mcus-products/can-t-program-stm32g031j6-disco-no-device-found-on-target-quot/m-p/98012#M14488
Have to jiggle Idd jumper on board, disconnect and connect quickly simultaneously as the Programmer ST-Link is trying to connect -- kludgy but worked !