2025-06-03 12:29 AM
Hey friends,
Until yesterday, my custom board with the STM32H753ZI100_24 MCU—connected to an IMU sensor, magnetometer, and barometric sensor via SPI—was detected successfully by STM32CubeIDE. But today, when I came to the office, I’m unable to initialize the ST-Link device, which I used to program the board through Vaap, GND, SDIO and SWCLK pins in the st-link.
Here are the steps I’ve tried so far:
Restarted my Linux PC
Removed all power from the board and the ST-Link V2, checked the connection and then reconnected everything
Connected the ST-Link to another STM32 MCU on the same board, and it works fine
Verified 3.2 V power supply to the MCU with a multimeter which is needed for mcu to power up.
Despite this, I still can’t get the ST-Link to detect the board. Could this be caused by something in the last code I flashed, or is it likely a hardware issue?
Any advice or suggestions would be greatly appreciated!
Thanks in advance.
Solved! Go to Solution.
2025-06-09 9:51 PM
i have followed the stm32 stack overflow forum the 4th answer which mention to using the cubeprogrammer i have reduced the swd frequency lesser than 4000 khz. And now its also get connected in 4000 khz.
2025-06-03 1:47 AM - edited 2025-06-03 6:11 AM
Additional to this there is an another dialog box arises when i debug or run the code.
what are the reasons this might get
2025-06-03 6:18 AM
Can you connect with STM32CubeProgrammer?
Can you show the board schematic? Could be a design issue.
Can you monitor power drawn by the board? If it's drawing excessive current, it could be dead.
Put the chip into bootloader mode and then try to connect (in STM32CubeProgrammer).
2025-06-05 12:58 AM
No im unable to connect with stm32cubeprogrammer
i discuss with the hardware designer and send the design
current drawn is increasing slightly over the few days
the bootloader is in given to ground by default in hardware so is there any other option to enable bootloader
2025-06-05 1:00 AM - edited 2025-06-05 2:12 AM
and now i connect it to through stlink commands in linux terminal. shows chip id and core id as 0.
is it due to its not recommended for new designs as they said in their website. https://www.st.com/en/development-tools/stsw-link004.html
2025-06-05 4:28 AM
> current drawn is increasing slightly over the few days
Not a good sign. I'd guess a hardware issue.
I would stick with STM32CubeProgrammer.
2025-06-05 6:37 AM
yeah here the schematics
2025-06-05 6:41 AM - edited 2025-06-05 6:43 AM
the current consumption is increasing 1 milliamps than the previous day is this a problem
but im unable to connect with stm32cubeprogrammer
2025-06-09 5:44 AM - last edited on 2025-06-09 5:47 AM by mƎALLEm
Post merged
Hey friends,
In my custom board with the STM32H753ZI100_24 MCU—connected to an IMU sensor, magnetometer, and barometric sensor via SPI—was detected successfully by STM32CubeIDE. But today, when I came to the office, I’m unable to initialize the ST-Link device, which I used to program the board through Vaap, GND, SDIO and SWCLK pins in the st-link.
original post - stm32 chip id erased
kindly help with this im new to stm32. i have attached updates in that old post
2025-06-09 5:48 AM
Hello @santhosh16 ,
Please don't duplicate/re-post the same question/request.
If you need more assistance you need to keep asking in the same thread.
Thank you for your understanding.