Hi there, I’m new to the Chipwhisperer. I’ve successfully completed the SCA101 and SCA201 courses, and never had issues with capturing traces etc.
I’m struggling with the fault101 course, namely that even with using the solution code, and correct configuration, I cannot seem to get any results, the glitches have no effect, the only output in the displayed stats is “normal”.
I’m using a STM32F415 connected to a CWLITE-ARM target board. I have connected them using the 20pin, the microusb, and the coax cable to the “glitch” port.
My configuration is as follows:
The solution involved changing the width and offset range in the program.
I’ve had success with the following:gc.set_range("width", 2, 14) gc.set_range("offset", -14, 14)
Thanks for the update. For glitch attacks it can be hard to provide glitch parameters that work out-of-the-box for everyone; many things like cable length, small variations in parts (different batches), and even temperature can affect the results. But, those are all real-life glitching issues. Good job on finding parameters that work for you!
Hello
But does this also applies to the labs, I thought it should work out of the box, maybe can you shed some lights on how can we trouble shoot to just apply one voltage glitching lab?
I’m facing the same issue with CWNano, both labs applicable to CWNano just not working, I followed SCA101 and side channel analysis lab to bypass password is working fine, however for glitching all I’m getting is Normal count.
In CWNano I can’t change the width of the glitch, I trtied to increase offset or repeat parameters but no success, any suggestion how can I test voltage glitching with the Nano.
Yes the nano has fewer glitching options. The hardware that lets us finely tweak glitch shapes in the other ChipWhisperers doesn’t fit into the Nano’s price point or form factor.
Parts shortages has led to some part substitutions in the Nano and these can potentially impact where successful glitch parameters can be found. I would increase the range of glitch parameters and run more iterations.
The point of the labs is not that they should work out of the box; you won’t learn very much if you can just “shift-enter” your way to success. That’s why we only have some “solution” notebooks. Most labs require you to write code and figure things out. Glitching usually involves lots of trial and error!