Ask questions and find answers on STM32 hardware set-ups, including schematic-related challenges, debugging probes, power configurations, and more.
After updating CubeIDE to version 1.4.0 (Linux), the debugger does not work.A window appears "ST-LINK firmware verification"in which there is a message - "STLink server is required to launch the debug session".How to fix it?
Hello, I recently purchased an STM32F429i-eval1 board. I followed the manual, made sure nothing is loose and unseated, and powered on the device. I read that the board ships with a default image that will display in the UI and flash LEDs. When I powe...
Hello folk, I hope you are just fine and safe at this unusual time.I am working on a project but I am stuck in its USB VCP Host section. I have a Proxmark3 board which probably you are familiar with. It has an Atmel microcontroller AT91SAM7s265 that ...
Thank you for helping.When changing from STM32F769NIH6 to STM32F769BIT6That is, when changing from BGA to LQFPI think the software can be used as it is.Is this perception correct?Thank you.
I have IC samples are unable to be detected the SWD ID through ST Link and J-LinkThe hardware circuit is as follows. Are there any suggestions or improvements?Thanks
I want to attach the 14 pin STDC14 debug connector (CN5) found on STLInkV3 Mini to a PCB. However, I can't seen to find the exact model. Any idea what the exact part number of that connector (CN5) is?
How can I connect to a running target (without re-flashing and resetting) using STM32CubeIDE and STLink ?
The development board is STM32H757I-EVAL which has a ST link V3 on it,but after I download my program (just once) and update the firmware, it cannnot work correctly.Here is the situation when I try to debug it:
I purchased a 32F469IDSICOVERY board and I connected it to the PC using a Type A - MINI B cable to the USB STLINK port. The board is powered normally (LD5 is RED) and the demo application worked fine but the board itself is not detected on the PC at ...