Robin Krahl

1. What is the output of `lsusb`, `nitropy nk3 list` and `solo2 ls` before running this step? 2. This is directly caused by (1) failing. 3. I can reproduce the...

@bamontales Thanks. Please try to re-run the failing step `make -C utils/lpc55-builder fw-provision-certs` with this PR: https://github.com/Nitrokey/nitrokey-3-firmware/pull/638

I need to check that but the current state of the device should be fine for testing. The only difference is that it also contains the provisioner app that is...

No, this is not normal. A red LED indicates a panic (i. e. a crash) in the firmware. Do you have a debugger?

You can also use that as a debugger, see Section 4.4 of [UM11158](https://www.mouser.com/pdfDocs/UM11158.pdf).

I think you have to run `make -C utils/lpc55-builder run FEATURES=log-error,log-semihosting`. Then you should see a panic message in the output.

Regarding the third problem from the original post: I think you can just run `make -C utils/lpc55-builder flash`. We forgot to update that line in https://github.com/Nitrokey/nitrokey-3-firmware/commit/26c64145525e14cb438ad7ddeef6c96d1e9bc1a4.

@bamontales Strange. I’m not sure if this is the actual error we see here or a problem with the debugger setup. Anyway, please repeat the test with gdb and hit...

The `CC` environment variable is not set to in the CI docker container, so the `cc` crate should default to the `cc` binary AFAIS which is `gcc` in the container....

I’m closing this issue as the question has been answered. Feel free to re-open or create a new issue if the AES encryption and decryption does not work as expected.