You are signed in. Close

You are signed out. Close

Thank you. Your subscription has started. Close

Thank you. You will get an email when a new comic comes out. Close

We could not confirm your payment. If you paid, use the link "Sign in" at the bottom of the page. Close

Something went wrong on our side. Please try again in a moment. Close

Previous episode RTOS: how one small chip does two jobs and still keeps its deadline

How embedded systems work: the hidden computers in everyday things, and how engineers build them

Debugging firmware: how to find a bug in a device with no screen

When an app crashes on your phone, you at least see an error. When a small device goes wrong, it simply stops, or quietly starts over, and there is nothing to read. So how do engineers see inside a chip while it runs?

  1. 1 Three weeks later, the first PCBs arrive. Rono fits one into a real flap, with four real batteries this time.the first PCBsRono++

    Three weeks later, the first PCBs arrive. Rono fits one into a real flap, with four real batteries this time.

  2. 2 Miva's cat comes, the latch clicks once, then nothing. The little light blinks as if the flap had just been switched on, and there is no screen to tell you why.clickblinkyou

    Miva's cat comes, the latch clicks once, then nothing. The little light blinks as if the flap had just been switched on, and there is no screen to tell you why.

The rest of this episode is for subscribers

Subscribe to read every premium episode. You can cancel when you want.

Paid yearly: $99 instead of $119.88

Next episode Hardware testing: why some device bugs only show up after 49 days

Share this comic

More comics