PCBA Studio checks that your firmware and your hardware agree.
A board can route one pin, CubeMX can configure another, and the firmware can still compile. PCBA Studio reads the schematic, the CubeMX file, and the firmware on your machine and reports the contradiction with the file, the location, and the quoted evidence.
Schematic
PD8
USART3_TX
CubeMX
PB10
USART3_TX
Firmware
PD8
GPIOD, GPIO_PIN_8
Eight checks, five of them across domains
Connectivity comes from the wires on the sheet. A net label only supplies a name.
| Rule | What it reports |
|---|---|
| cross_domain.pin.mismatch | The same peripheral signal is routed to different pins in the schematic and in the .ioc. |
| cross_domain.firmware.hardcoded_pin_drift | Hand-written firmware names a pin that the .ioc now assigns elsewhere. |
| cross_domain.pin.unconfigured | A peripheral signal on the schematic is absent from the .ioc. |
| cross_domain.mcu_config.incomplete | The .ioc covers almost none of the schematic. One finding is reported instead of a list of individually true and collectively useless pin findings. |
| cross_domain.peripheral.unconnected | A peripheral configured in the .ioc has no matching schematic connection. |
| schematic.net.mislabelled | A net label's pin prefix disagrees with the geometric connection. |
| schematic.net.open_circuit | A part nearly touches an MCU pin and stops short. This rule is heuristic. |
| stm32.pin.alternate_function_impossible | The selected pin cannot carry that peripheral signal, according to the MCU database installed with CubeMX. A review on this website skips this rule and says so, because that database is not included with PCBA Studio. |
Where the product stops
- Gerber, ODB++, Excellon, BOM, pick-and-place, and panel data belong to Gerbtrace.
- Component price, stock, and lifecycle belong to Elexess.
- Flashing a device and writing option bytes stay with ST's programmer.
- Clearance, creepage, and impedance stay with Altium's design-rule check and with Gerbtrace.
- PCBA Studio reports evidence for a person to review. It does not certify a board and it does not sign off a release.
The checker stays on the machine
The pcba command and the VS Code extension read the project where they run. They do not send the schematic, the .ioc, or the firmware to this website.
A review on this website runs in your browser and does not upload the design. Saving a project, on the paid plans, keeps the file until you delete the project or the account.
How a review is run
- 1
pcba inspect . shows the schematic directory, the .ioc, the firmware roots, and which rules can run.
- 2
pcba review . writes the findings. Exit 0 means the chosen severity was clean, 1 means findings met it, and 2 means the review could not run.
- 3
Read coverage.skipped before you trust a clean result. A rule that could not run is listed there.