2026-04-10 11:20 AM - last edited on 2026-04-10 11:37 AM by mƎALLEm
Hello everyone.
I have recently made my own STM32 board based on the STM32F405. After soldering all the components and testing all pads and connections, finding them to be wired correctly and checking that the 3.3V is being supplied to all the correct pins, I tried to upload some code but to my shock the STM32F405 isn't establishing a connection via the ST-Link V2 nor the USB cable. After trying multiple fixes, I suspect the issue might be the STM32F405 chip that I got off AliExpress itself.
So before I took any further steps to replace it, I decided to post my schematics on here for review in case the problem was in my PCB design. If you have any remarks on what might have caused this problem, please share them.
NOTE: The -B label is referring to ground, and P is the VCC.
schematics:
Solved! Go to Solution.
2026-04-10 2:05 PM
VBAT is pin 1. But where is pin 1 on the package?
Read my previous post.
2026-04-10 2:10 PM
Ok, so from what I understand, this pinout diagram I followed is faulty, as pin 1 (VBAT in the STM32F405 case) is shown at the very top of the row next to the pin 1 indicator and not directly next to it. Is this correct?
2026-04-10 2:15 PM
2026-04-10 2:15 PM - edited 2026-04-10 2:23 PM
Don't rely on the CubeMx figure, it's just a photo.
Please check the datasheet / Figure 76. LQFP64 - Outline
And this is pin 1:
.
In CubeMx: VBAT is indeed pin 1. But your reference of the package on the PCB is wrong.
2026-04-10 2:19 PM - edited 2026-04-10 2:26 PM
Personally, I don't think that datasheet is very clear. TN1433 (Reference device marking schematics for STM32 microcontrollers) is better:
Especially as the datasheet also has this:
which could be misinterpreted.
2026-04-10 2:19 PM
Yeah, I have read it seems that the pinout diagram i followed was wrong, as pin 1 VBAT is shown to be at the very top of the row that's next to the PIN indicator instead of next to it and i found this other diagram that seems to confirm my suspicions:
-the faulty one I used:
- the one from the Utmel website and the STM32CubeMX interface:
2026-04-10 2:23 PM
Yep, this seems to be the issue. Thanks for your help. It will take some time before i can fix it if the issue presist ill keep you updated