So I wanted to follow tutorial #B1 but when I select “ChipWhisperer-Rev2: SimpleSerial Target” from Example Scripts in the project menu, the script automatically connect to the capture hardware. Instead of running 2 example traces, i get this error
Found programmed device
EZ-USB Microcontroller: Skipped firmware download (already done)
FPGA: Skipped configuration (already done)
No phase shift loaded
OpenADC Found, Connecting
WARNING: Response too short (len=0):
This happens when there is no “response” from the DUT. The most typical errors are (1) wrong/no firmware loaded, (2) wrong/no clock source, or(3) trigger at incorrect time.
What target are you using, can you post details of configuration? Is the “ADC Clock” an appropriate frequency?
On the trigger pins setup, I unselected Front Panel A and checked Target IO4(Trigger Line) and the clock source is Target IO-IN
Target INn Pins-Target IO1:serial RXD and Target IO2:serial TXD
Hmm… can you scope the “TX” and “RX” jumpers? Just to see if data is flowing only one way… for example I suspect only one of them will have activity when you hit the “Capture 1” button, and would like to confirm this to narrow down possible error sources.
It was a problem with the jumper settings…I am able to capture traces even thou there is still “?” on Expected. I ignored the warning
Another thing, I just wanted to find out how one can program the microcontroller with other algorithms from the crypto folder .eg.rsa and des from C:\chipwhisperer-0.12RC1\hardware\victims\firmware\crypto\avrcryptolib and and AES 256 from C:\chipwhisperer-0.12RC1\software\chipwhisperer\analyzer\attacks\models , will the results table from the analyzer software expand because of the longer key? What changes need to be made?
Alright, great… the ? on expected means it’s not getting the ciphertext back. It could still indicate there was a problem as it’s not receiving the data, although if you are getting a trigger and an ok-looking waveform you can still do the attack (the response sin’t needed for the system to work).
Right now attacking other modules needs some “hacking” in the analyzer, which is done via making a custom script. An example of attacking AES-256 is available at newae.com/sidechannel/cwdocs/tut … 6boot.html.
We’re in the middle of re-writing the software, so will have some updates after that is done, as it will in the future be a lot easier to perform some specialized attacks…
