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

[capture] Enable uJSON protocol on CW305 #235

Open
1 of 2 tasks
vogelpi opened this issue Nov 30, 2023 · 1 comment
Open
1 of 2 tasks

[capture] Enable uJSON protocol on CW305 #235

vogelpi opened this issue Nov 30, 2023 · 1 comment
Assignees

Comments

@vogelpi
Copy link
Collaborator

vogelpi commented Nov 30, 2023

The CW305 has a couple of advantages over the CW310/CW340 when it comes to debugging/optimizing countermeasures. However, it currently cannot be used for uJSON captures.

What needs to be done to re-enable captures with it:
- [ ] Capture script and config file adjustments
- [ ] Update AES binary (bitstream should still be fine) to align the software PRNG for generating the key masks (now AES according to DTR is used)
- [ ] Re-enable CI

For the switch to uJSON (OpenTitan repo):

@vogelpi
Copy link
Collaborator Author

vogelpi commented Jan 11, 2024

I turns out captures with the CW305 are possible and some checks are done in CI. We just need to enable the uJSON variant and extend the tests in CI (see also #271).

@vogelpi vogelpi changed the title [capture] Re-enable captures with CW305 [capture] Enable uJSON protocol on CW305 Jan 11, 2024
vogelpi added a commit to vogelpi/opentitan that referenced this issue Sep 20, 2024
For penetration testing, we've been using a second UART on the CW310 and
the silicon platform such that the host can directly communicate with
the target using the uJSON protocol instead of looping this
communication through the simpleserial channel with the scope
(available on Husky only anyways).

This commit now adds a second UART to the English Breakfast top level
such that we can re-align the capture setups again. Ultimately, this
will allow removing the simpleserial-based communication which will
quite notably simplify code maintenance in the future.

For reference, see also lowRISC/ot-sca#235.

Signed-off-by: Pirmin Vogel <[email protected]>
vogelpi added a commit to vogelpi/opentitan that referenced this issue Sep 20, 2024
For penetration testing, we've been using a second UART on the CW310 and
the silicon platform such that the host can directly communicate with
the target using the uJSON protocol instead of looping this
communication through the simpleserial channel with the scope
(available on Husky only anyways).

This commit now adds a second UART to the English Breakfast top level
such that we can re-align the capture setups again. Ultimately, this
will allow removing the simpleserial-based communication which will
quite notably simplify code maintenance in the future.

For reference, see also lowRISC/ot-sca#235.

Signed-off-by: Pirmin Vogel <[email protected]>
vogelpi added a commit to lowRISC/opentitan that referenced this issue Sep 20, 2024
For penetration testing, we've been using a second UART on the CW310 and
the silicon platform such that the host can directly communicate with
the target using the uJSON protocol instead of looping this
communication through the simpleserial channel with the scope
(available on Husky only anyways).

This commit now adds a second UART to the English Breakfast top level
such that we can re-align the capture setups again. Ultimately, this
will allow removing the simpleserial-based communication which will
quite notably simplify code maintenance in the future.

For reference, see also lowRISC/ot-sca#235.

Signed-off-by: Pirmin Vogel <[email protected]>
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

3 participants