Troubleshooting Fault Injection with CWNano

1

Hello,

I’m trying to understand how to see the effect of glitch on the powertrace. as I’m trying to solve the fault101 labs with CWNano.
so I used something like in below screenshot to see the trace when I do a glitch, however when I plot it it doesn’t show any shortage in voltage or power, what i’m doing wrong?

image
image1208×505 64.8 KB

2

What target firmware are you running? The target is likely not issuing a target to the scope. If there is no trigger, your scope.capture() will time out, and no glitch will occur. You’ll still get a power trace but it’s just a power trace of your idle target.

If you look at e.g. Fault 2_1B, you’ll see that we do this:

scope.arm()
target.simpleserial_write("g", bytearray([]))
scope.capture()

Here the simpleserial_write() sends a command to the target, which makes it in turn raise the trigger line back to the scope.

This is FW-dependant; in 2.1B, the simpleserial-glitch.c firmware responds to this specific ‘g’ command.

1 Like
3

Thanks for the feedback.
May I have another question, if I want to capture this with a picoscope that I have here.
what kind of hardware connection I need to do?

4

You would connect your probe to the unpopulated 3-pin “measure” header. You probably also want a way to trigger your picoscope; if you’re running our notebooks, that would be the GPIO4 line which you can access on J6.

1 Like