2025-10-22 2:20 PM - edited 2025-10-23 8:40 AM
Hi. I designed a stm32 board an am trying to program it with a stm32 development board. i am having issues with programming it. This is my board design and my programming setup. I have connected the stm32f4 to my laptop to program it and the Integrated Circuit I'm using on my board is the stm32 g431. I know i have not pulled boot0 to low which is a problem i tried to resolve using option bytes where i set the nBoot1 byte to 0. But i have my boards boot up and then after clearing flash storage, they are usually stable. The board isn't dead since current is being drawn but the stm32 status LED is blank and when i try to connect to it with the stm32 programmer, i get ' Unable to detect Core ID. No stm32 target found. If your product uses debug authentication, please enable debug authentication. Please help me figure out what is wrong. This is the second board that has gone this way. I only have 3 more left.
2025-10-22 4:21 PM
STM32Cube Programmer shows you're connected to a STM32F4Discovery, not your custom STM32G4.
Pull the JP1 jumper so that the STM32F4 is no longer powered. Then you should be able to connect to the STM32G4.
2025-10-22 4:42 PM
The jumper is pulled. The reason that is showing is prolly because i am programming the stm32g431 though the debug pins of the stm32f4.
2025-10-22 9:01 PM
From the image, the jumper JP1 is there.
2025-10-22 10:16 PM - edited 2025-10-22 10:17 PM
the image isnt very clear but there is no jumper there. Am i looking in the wrong location ??
2025-10-23 12:18 AM
Technically, JP1 is spelled "JP1", lol. But CN3 will also do.
Can't tell which wire on the Disco connected at CN2-2 is going to your board. Not sure if both wires are white, or one of them is gray? So can't tell if SWCLK and SWDIO are swapped?
I have an STM32F4 Discovery and I am able to remove JP1 or CN3 jumpers. STM32Cube Programmer can connect to an STM32F072 with no issues. I'm only using CN2-2, CN2-3 and CN2-4 connected to the STM32F072. The STM32F072 is powered by USB.
2025-10-23 2:48 AM
@Karl Yamashita wrote:STM32Cube Programmer shows you're connected to a STM32F4Discovery, not your custom STM32G4.
I think that's just because @aks1 is using the ST-Link on the Discovery board?
2025-10-23 2:54 AM - edited 2025-10-23 3:20 AM
You haven't shown the schematic of your custom board.
To be honest, a standalone ST-Link isn't expensive - Why not just get one?
Although it is technically possible to use the one in a Dev Board, using a standalone is a lot more straightforward!
The thing about using the one from a Dev Board is that you need to be sure that the Dev Board's target processor is completely disconnected - so as not to interfere with the connection.
2025-10-23 4:37 AM
One more vote for a standalone ST-Link.
I really like that they built into the ST-Link a USB-VCP so that you only have one connector for flashing and UART-debugging.
Just working with it, I prefer the UART & LED debugging so much to the standard (?) debugging with CubeIDE, which I use only with really bad faults.
2025-10-23 6:02 AM
@LCE wrote:I really like that they built into the ST-Link a USB-VCP
Only in the ST-Link v3.
But this would be an added advantage over a Dev Board - as they don't make external access to the VCP at all convenient!
@aks1 : With an STLINK-V3SET you also get an extra SPI/UART/I2C/CAN/GPIO bridge.
With an STLINK-V3PWR you also get power measurement.
These options are obviously a bit more expensive!
Full range here: https://www.st.com/en/development-tools/hardware-debugger-and-programmer-tools-for-stm32.html