Component Overrides and Grounding Advice

flux

1:31

Seeking electronic advice.

Analyzing the schematic.

Running design review.

Accessing knowledge base.

Analyzing the PCB layout.

Looking for "3V3 pin power output capability and whether 3V3 is a regulated output" in nRF52840_PS_v1.5.pdf

Running multiple web searches.

Found 10 results.

Found 10 results.

Considering I2C pull-ups.

Reviewing PCB Layout.

Refining Component Links.

No changes made.
What the “component overrides” errors actually mean
Those errors are layout override warnings, not schematic connection faults. They indicate some footprint/model/text properties were set with !important, so the review flags them.

Overrides I can see

ItemWhat looks overriddenLikely meaning
U13V3 pad position, 5V pad position, 3D model hiddenManual footprint/model edits
U33D model hiddenUsually cosmetic/mechanical
U4RX pad positionManual pad adjustment
[MicroSD pins](MicroSD pins)footprint text/shapes hiddenUsually cosmetic
[Breakout board - SEN66](Breakout board - SEN66)footprint text/shapes hiddenUsually cosmetic
Bottom line on overrides
  • These are not automatically dangerous
  • They usually come from:
    • hiding reference/value text
    • hiding a 3D model
    • nudging a pad or shape manually
  • They do matter if a pad was moved and no longer matches the real physical part
So for your board, the main ones worth actually caring about are:
  • the pad overrides on U1
  • the pad override on U4
The hidden text/model ones are mostly cosmetic.
Are your connections safe and good?
From the current checks:
  • Pin-to-pin conflicts: none
  • Undriven nets: none
  • Single-pin nets: none
  • No-connect violations: none
So electrically, your net connections look basically sane.
About the 3V3 warning you said to ignore
That matches what I found:
  • The only ERC power complaint is U4:VCC not driven
  • For U1, the extracted documentation shows the 3V3 header is 3V3_OUT from a regulator and includes **3.3 V; 250 mA**
So your reasoning is consistent: ERC is likely complaining because it does not classify U1 3V3 as a formal power-output pin, even though it is a real regulated output.
Things I would still keep an eye on
  • There is still 1 airwire in the layout, so the board is not fully routed yet
  • I do not see discrete I2C pull-ups in the visible schematic on I2C_SDA / I2C_SCL
    • that may be fine if they already exist on the external sensor board connected via [Breakout board - SEN66](Breakout board - SEN66)
    • but it is worth confirming
  • C4 and C5 are both 100 nF decouplers on 3V3_SENSOR, which is good as local high-frequency decoupling
  • I cannot fully verify the input-voltage requirements of U4 from the project itself because that part has no datasheet attached in the project
Do you need copper pours for grounding?
Yes, I would recommend using ground copper.
For your board, ground copper is beneficial because it gives:
  • lower return-path impedance
  • better signal return paths for SPI/UART/I2C
  • less noise coupling
  • easier routing and fewer long ground traces
Practical recommendation
  • Since your layout is already 4-layer, the best approach is:
    • keep one internal layer as a solid GND plane if possible
    • also use top/bottom ground pours where helpful
  • If you use pours:
    • avoid skinny isolated ground islands
    • stitch top/bottom ground together with vias where needed
    • keep return paths continuous under SPI traces where practical
Short answer
  • No, the board does not strictly require pours to function
  • Yes, you should probably use them, especially for a mixed board with U1, [MicroSD pins](MicroSD pins), U4, and the sensor connection on [Breakout board - SEN66](Breakout board - SEN66)
My overall take
  • Your schematic connections look mostly good
  • The 3V3 ERC warning is probably benign in your case
  • The component override errors are mostly about manual footprint/model overrides, not broken nets
  • The two things I would still treat as real follow-up items are:
    • the remaining airwire
    • confirming the pad overrides on U1 and U4 were intentional and still match the real hardware
If you want, I can next do a read-only checklist review of the likely risk points without changing anything.
@review check airwire
Ask about D10_MOSI
Ground pour guidance
Check U1 overrides
Ask about pull-ups
15 days

Ready.

Sign up to send
U1 P1.11_TX_D6 - U4 RX
U1 P0.05_SCL_A5_D5 - Breakout board - SEN66 4
U1 P0.29_A3_D3 - MicroSD pins Pin_1
U1 D9_MISO_P1.14 - MicroSD pins Pin_4
U1 D7_RX_P1.12 - U4 TX
U1 D8_SCK_P1.13 - MicroSD pins Pin_2
U1 P0.04_SDA_A4_D4 - Breakout board - SEN66 5
U1 D10_MOSI_P1.15 - MicroSD pins Pin_3
U1
GND
 
Hollow Moccasin Lightcycle thumbnail
Welcome to your new project. Imagine what you can build here.

Properties

Pricing & Availability

Distributor

Qty 1

Arrow

$15.25

Digi-Key

$15.99

LCSC

$43.61

Mouser

$15.25

Verical

$14.40–$14.79

Assets

Assets are files uploaded to this project which can be used in various ways.

Controls