Hello,
I am using ChipWhisperer-Husky and the SAM4S target board for SCA.
I want to set the target board operating at a frequency of 24Mhz, and the traces are acquired with the sampling rate of 96MS/s, i.e., four data points per clock cycle are recorded.
So in the python code, I made the following settings：
But what puzzles me is that, compared to the work of other people, I’m collecting many times as many points as they are, for the same operation (the number of points for the operation to be tested)
So, is my setup really the same as I expected? Is there any code elsewhere that I need to modify/set up？
Sorry, maybe I didn’t express myself very accurately.
I didn’t mean the total number of samples (scope.adc.samples). Rather, it’s a certain portion in there that I identified. With the waveform I can identify which part is the operation I want to test.
But this is the part where I have more samples than others.
For example, for the same run of function A, the other guys get x points, while I get significantly more (just for the part of function A).
That’s clear as mud for me!
From your description, your power trace doesn’t look the way you expect it to.
Usually, the reason for this is that you have incorrect assumptions about what the power trace “should” look like.
If you still think that there is an issue with ChipWhisperer, then submit a proper reproducible example so that I can investigate. This means setup details, target firmware, and capture code.
