Skip to content

PCB Bring-Up & Debug — question 5 of 10

Write a real answer. It is graded against the question's rubric, and the mastery movement is computed by the same engine the product uses. Scoring here is deterministic rather than model-written, so this page costs nothing to run and nothing is saved. In a track built from your own posting, the same rubric is graded by the model, which is what produces feedback about your reasoning rather than about coverage.

Assume you have a two-channel scope and the board's power sequencer is configurable via resistor straps or firmware.

A board has a 1.0V core rail and a 3.3V I/O rail. The datasheet requires the core rail to reach 90% of nominal before the I/O rail turns on, with the two enables no more than 5ms apart. You scope both rails on power-up, triggered on the same event, and see the I/O rail cross its threshold 2ms before the core rail even reaches 0.5V. The board intermittently fails to enumerate on USB. How do you confirm sequencing is actually the cause, and what could happen inside the chip if this violation persists?

How sure are you?

Being confidently wrong costs more mastery than admitting a guess — that is deliberate, and it is how misconceptions get found.

Neither is graded, and nothing here is recorded.