[capture] Enable uJSON for KMAC #238
Assignees
Labels
Comments
nasahlpa
added a commit
to nasahlpa/ot-sca
that referenced
this issue
Dec 5, 2023
Similar to lowRISC#218, this PR enables uJSON support for capturing KMAC traces. The device command handler code can be found in #20563. Closes lowRISC#238 Signed-off-by: Pascal Nasahl <[email protected]>
nasahlpa
added a commit
to nasahlpa/ot-sca
that referenced
this issue
Dec 6, 2023
Similar to lowRISC#218, this PR enables uJSON support for capturing KMAC traces. The device command handler code can be found in #20563. Closes lowRISC#238 Signed-off-by: Pascal Nasahl <[email protected]>
nasahlpa
added a commit
to nasahlpa/ot-sca
that referenced
this issue
Dec 6, 2023
Similar to lowRISC#218, this PR enables uJSON support for capturing KMAC traces. The device command handler code can be found in #20563. Closes lowRISC#238 Signed-off-by: Pascal Nasahl <[email protected]>
nasahlpa
added a commit
to nasahlpa/ot-sca
that referenced
this issue
Dec 6, 2023
Similar to lowRISC#218, this PR enables uJSON support for capturing KMAC traces. The device command handler code can be found in #20563. Closes lowRISC#238 Signed-off-by: Pascal Nasahl <[email protected]>
nasahlpa
added a commit
that referenced
this issue
Dec 6, 2023
Similar to #218, this PR enables uJSON support for capturing KMAC traces. The device command handler code can be found in #20563. Closes #238 Signed-off-by: Pascal Nasahl <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Similar to AES (#218), we need to enable uJSON communication for KMAC. This requires adaptions in the ot_communication file as well as on Opentitan (#20386).
The text was updated successfully, but these errors were encountered: