Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Feature: Segmented Memory #301

Open
colinoflynn opened this issue Jan 29, 2021 · 0 comments
Open

New Feature: Segmented Memory #301

colinoflynn opened this issue Jan 29, 2021 · 0 comments
Assignees

Comments

@colinoflynn
Copy link
Contributor

colinoflynn commented Jan 29, 2021

ChipWhisperer is adding segmented memory - see https://github.com/newaetech/chipwhisperer-jupyter/blob/master/demos/Using%20Segmented%20Memory%20for%20Hardware%20AES%20(STM32F4).ipynb for the best example of it. You need to use the debug FPGA bitstream in that example.

See https://chipwhisperer.readthedocs.io/en/latest/api.html for details in:

  • fifo_fill_mode talks about enabling this mode.
  • capture_segmented and get_last_trace_segmented are needed instead of capture and get_last_trace

This is only useful for short captures (think - hardware AES). But you can bump up your capture rates in the range of 1000-4000 traces/second in my testing. More may even be possible, there is still a lot of overhead right now that isn't optimized away. But at some point I'm not sure how much faster becomes useful, since you can capture 1M traces in ~15 mins, 1B traces in ~a week. You'll need a lot of GPUs to process those traces.

Keeping this issue tracker open to get issues/feedback on it until it goes into the main FPGA build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant