STM32H7 PCB Design Review – What Are the Most Common Layout Mistakes?

[ST Migration account]

This topic was created on June 8 2026 10:14 PM. 

​@MariaWilliams posted:

Hi everyone,

I'm designing my first custom PCB around an STM32H7 microcontroller and would appreciate some advice before sending it for fabrication.

The board will run at high clock speeds and includes:

• STM32H7 MCU
• External QSPI Flash
• Ethernet PHY
• TFT display interface
• Several ADC inputs

I've already followed the reference schematic, but I'm unsure about the PCB layout side of things.

What are the most common mistakes you have seen in STM32H7 PCB designs?

In particular, I'd like to know:

• How critical is crystal placement and routing?
• Do all decoupling capacitors need to be on the same side as the MCU?
• Any recommendations for ground plane partitioning?
• Are there any Ethernet or QSPI routing pitfalls that beginners often overlook?

I'd appreciate any tips, design guides, or examples from people who have successfully brought up STM32H7 boards.

Thanks!

[ST Migration account]

This reply was created June 8 2026 10:20 PM.
user ​@ahsrabrifat replied:

For STM32H7 boards, the biggest mistakes I usually see are related to power distribution and decoupling rather than the MCU itself.

Make sure each VDD pin has its recommended decoupling capacitor placed as close as possible to the pin. Also pay attention to the power supply layout, because the H7 can generate fairly large current spikes when running at high clock speeds.

For the crystal, keep the traces short and avoid routing any high-speed signals nearby. If you're using Ethernet, follow the PHY manufacturer's layout recommendations closely and try to maintain a solid ground plane underneath the differential pairs.

For QSPI Flash, keep the traces short and avoid excessive vias. It may work fine on a prototype, but poor routing can cause intermittent issues once you increase the clock frequency.

I would also recommend doing a design review against ST's hardware design guidelines before ordering boards. Catching one layout issue before fabrication can save a lot of time.

That might help: https://www.pcbway.com/blog/PCB_Design_Tutorial/Tutorial__How_to_Design_Your_Own_Custom_STM32_Microcontroller_Board.html

[ST Migration account]

This reply was created June 8 2026 10:39 PM. 
user ​​​​​​@MariaWilliams replied:

Thanks for the detailed suggestions.

The board is still in the layout stage, so fortunately I haven't sent it for fabrication yet. I was already planning to use a solid ground plane and place the decoupling capacitors close to the MCU, but I wasn't paying as much attention to the QSPI routing as I probably should have.

One thing I'm still debating is how to connect the external modules. The main board will connect to a small sensor board and a display board, so I'm looking at different connector options. Initially I was thinking about simple pin headers, but now I'm considering Molex-style locking connectors because the device may be installed in an environment with vibration.

I'm also wondering whether it's better to run dedicated cables between the boards or use some type of wire splice arrangement within the enclosure to simplify assembly and maintenance.

Has anyone dealt with connector reliability issues on STM32-based products? I'm curious what connector families or wiring approaches have worked well for field-installed equipment.

[ST Migration account]

This reply was created June 8 2026 10:46 PM.
user ​@ahsrabrifat replied: 

We've built a few STM32-based industrial and monitoring systems, and after dealing with field failures, we stopped using standard pin headers for anything that might experience vibration or frequent maintenance.

For board-to-board and cable-to-board connections, locking connectors are definitely worth considering. They add some cost, but they greatly reduce the chances of intermittent faults caused by loose connections.

Regarding wiring, I generally prefer dedicated connectorized harnesses over wire splices whenever possible. Troubleshooting becomes much easier because individual modules can be disconnected and replaced without cutting or reworking wiring. Splices can work well in fixed installations, but they can become a headache during servicing if multiple sensors or peripherals share the same wiring bundle.

Another thing to think about is strain relief. Even with good connectors, cable movement can eventually stress solder joints if the wiring isn't secured properly inside the enclosure.

For a first revision, I'd probably choose locking connectors and a simple harness unless there is a strong cost or space constraint pushing you toward splices.

Useful Resources:

https://www.qwterminals.com/locking-connectors/

https://www.unikeyic.com/blog/wire-splice-types.html

[ST Migration account]

This reply was created June 8 10:48 PM. 
user ​​​​​​@Ozone replied:

Not that you won't get helpful and competent answers here, but I think an "embedded software" forum is not the most optimal place to ask. Most people here are focussed on the 'software' part.

I would place that question on specific hardware/PCB design boards as well, and perhaps a help forum of your design tool. And the websites/communities of other vendors, as the design requirements for MCUs of similiar clock rate and complexity are basically identical.

ST themselves has reference designs, and kowledge base articles for this topic.
Supposedly ST staff or experienced users present here can point you in the right direction.

[Andrew Neil]

​@MariaWilliams 

What are the most common mistakes

Probably omitting a thorough review of the datasheet, application notes, and other design resources provided by the manufacturer; eg,

AN4938, Getting started with STM32H74xI/G and STM32H75xI/G MCU hardware development

Also look for specific guides for Ethernet, external memories, ADCs, etc …

You can find these on the ‘Documentation’ tab of the Product Page for whichever chip you’ve chosen.

You didn’t say what specific STM32H7 chip you’re using, so here’s one at random:

https://www.st.com/en/microcontrollers-microprocessors/stm32h723ve.html#documentation

 

Not specific to STM32, but a common mistake is not to have prototyped first before committing to a PCB design.

This is what dev boards are for!