2025-03-01 7:55 AM
I am using the STLINK-V3SET. I have tried both the JTAG and SWD headers.
10:03:14 : UR connection mode is defined with the HWrst reset mode
10:03:15 : ST-LINK SN : 002600353532511031333430
10:03:15 : ST-LINK FW : V3J15M7B5S1
10:03:15 : Board : STLINK-V3SET
10:03:15 : Voltage : 3.26V
10:03:15 : Error: Unable to get core ID
10:03:15 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication
BOOT0: Pulled to GND (0V) through 10k pull-down resistor
NRST: Pulled to GND through 0.1uF capacitor
SWCLK (PA14), SWDIO (PA13) tied directly to header pins.
I have tried to discover using Debug Authentication, I've tried disabling and enabling shared. I've tried lowering the frequency to 50khz and 5khz from 8000 khz. I have my PCB gnd and 3.3V tied to the STLINK-V3SET as well.
I've also tried multiple MCU's.
One of the problems with my schematic is I have a 24mhz clock tied to the LSE input rather than the HSE input. Could this be the source of my problem? Or is there something else I have forgotten to try?
Thanks
P.S Here is a picture of the STM32's orientation. I aligned the small dot on the chip with the dot on the silkscreen.
2025-03-03 5:02 AM
Hello @bmorse and welcome to the community;
I recommend you to refer to AN4938 Getting started with STM32H74xI/G and STM32H75xI/G MCU hardware development and check your PCB.
Try to connect the board "under reset" using STM32CubeProgrammer.
May be this FAQ "How to solve debugger connection issues" can help you to solve the issue.
Thank you.
Kaouthar
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2025-03-03 5:23 AM
Hello,
Before going ahead, please make sure you are not in the same situation as described in this thread.