Sorry to say that I didn’t find the v5.6.1 in your github. Could you tell me where I can update my ChipWhisperer installation?
Magnolia
Sorry to say that I didn’t find the v5.6.1 in your github. Could you tell me where I can update my ChipWhisperer installation?
Magnolia
We haven’t released 5.6.1 yet. You can get the new code if you use our git develop branch.
However this is a lot of trouble just to go from floating point to integer samples, so I suggest you stay with your current installation (with the understanding that the ADC’s full range is [-0.5, +0.5], or, if you really want the power sample measurements as ints, then convert each sample by adding 0.5 and multiplying by 2^10.
The issue you linked is marked as closed. However the issue still persists.
What issue are you referring to?
Sorry, I tried to quote but failed.
This is the one.
It looks fixed to me. Which version of ChipWhisperer are you using: print(cw.__version__)
(if you have an old version, it won’t have the fix).
But given the information in your other thread, the problem is likely with your capture setup, i.e. the fact that your CW ADC clock is unlocked and/or that CW doesn’t have the target clock.
My version is 5.6.1 but lets continue this in the other thread if it’s an unrelated issue.
To close the loop here: neither 5.6.1 nor 5.7.0 (the latest release) have the fix; you will need to use the “develop” branch to get the fix. The next release will include it.