What To Do When SWD Port is Non-Responsive to STLINK?

[JOlso.12]

I have a newly-birthed target board based on 32F413. My programmer is an STLINK V2 with STMCubeProgrammer code.

What are good strategies when the SWD port is non-responsive to the STLINK programmer?

Must the micro's unused JDTO and JTDI pins be terminated with a pull up or pull down resistor?

Any heartbeat pin on the micro that would tell me that it awaits a firmware download on the SWD port?

[Tesla DeLorean]

Review schematic, PCB, and netlist.

More likely the part isn't functional in your circuit.

SWD pin complement should be sufficient.

Check part orientation

Check voltage at VCAP pin(s)

Check VDDA connected, check VDD/VDDA voltage

With BOOT0 pulled high you should be able to connect via USART1 PA9/PA10 at 9600 8E1, send an 0x7F data pattern, check if you get an 0x79 response.

[Tesla DeLorean]

Prior thread https://community.st.com/s/question/0D53W000011vQxcSAE/swd-or-jtag-how-does-recentlybirthed-target-know-which

[TDK]

Hold the chip in reset and SWD will be active. This is an option in STM32CubeProgrammer. If that doesn't work, look for a solution elsewhere. Power rails, signal connections, etc.

[Tesla DeLorean]

New thread, part orientation. https://community.st.com/s/question/0D53W000012UwA9SAK/ambiguous-lqfp100-pin-1-markings

From 2014 (but it's been a issue since before then)

https://community.st.com/s/question/0D50X00009Xka68SAB/stm32f401-64pin-pin1-marking-orientation