forked from Nitrokey/nitrokey-pro-firmware
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
14 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,12 +1,15 @@ | ||
| Firmware side work is done in wip-bootloader_pro. | ||
| Check TODOs in the wip-bootloader branch. | ||
| Check libnitrokey (for execution), and dapboot (for actual bootloader) projects. | ||
| Random notes regarding used bootloader: | ||
| - Check [libnitrokey] (for execution of bootloader activation command), and [dapboot] (for actual bootloader) projects. | ||
| - Data retention tests done - PWS tested only. | ||
| - Full libnitrokey test suite for Pro passed both after the update, and on merged firmware flashing. | ||
| - GnuPG tested and seems fine. | ||
| - Merged firmware (bootloader+fw) for one-pass flashing works. | ||
| - Firmware is write-verified by the bootloader, and the process is cancelled on write failure. This might result in broken firmware state. | ||
| - Interrupting DFU update procedure may result in broken firmware state on device (having parts of two firmwares). Bootloader will not start by default in such case with current configuration, but rather start the potentially broken firmware. | ||
| - Firmware is replaced on-the-fly, monotonically. | ||
| - Bootloader does not have access to the user space memory (over 110kB). | ||
| - When bootloader is activated, and the device is power-cycled without any action, it safely comes back to the main firmware application, without any change to the memory flash. | ||
|
|
||
| Data retention tests done - PWS tested only. | ||
| Full libnitrokey test suite for Pro passed after the update, and on merged firmware flashing. | ||
| GnuPG tested and seems fine. | ||
| Merged firmware (bootloader+fw) for one-pass flashing works. | ||
| Firmware is write-verified by the bootloader, and the process is cancelled on write failure. | ||
| Interrupting DFU update procedure may result in broken firmware state on device. Bootloader will not start by default in such case with current configuration, but rather start the broken firmware. | ||
| Firmware is replaced on-the-fly, monotonically. | ||
| Bootloader does not have access to the user space memory (over 110kB). | ||
|
|
||
| [libnitrokey]: https://github.com/Nitrokey/libnitrokey/blob/master/unittest/test_pro_bootloader.py | ||
| [dapboot]: https://github.com/Nitrokey/dapboot |