[Gnuk-users] Upgrading gnuk on a nitrokey start

Szczepan Zalega | Nitrokey szczepan at nitrokey.com
Thu Dec 29 11:27:53 UTC 2016


Hi Remy!

I have noticed that you have used .hex file for regnual update. The tool
does not understand this format and in consequence it sends ASCII
hexdump representation directly to device, which obviously will not
work. This was the cause of the update issues mentioned in previous
email. The stm32flash tool handles both .bin and .hex.

Just for testing purposes I have converted the firmware you have
received to binary [3] with srecord tools (not checked it though):

```
 srec_cat nitrokey-start-firmware-1.0.4-1a.hex -intel -offset
-0x08000000 -o nitrokey-start-firmware-1.0.4-1a.bin -binary

```

Have you tried upgrading using regnual with prebuilt binaries? [2]

As for compiling firmware for first release on Ubuntu 16.10, I have done
the same successfully on Virtualbox with image downloaded from OSBoxes
(to make it fully reproducible) - full log attached [1]. Please try the
compilation on a clean repository.

Additionally regnual tool might need recompilation (make clean; make) on
each ./configure run since it uses files generated with it.

SHA sum for downloaded Ubuntu image from OSBoxes:
$ sha512sum Ubuntu_16.10_Yakkety-VB-64bit.7z
fa16b1fc694679a7e470030eddc3fc1e842e94e6cb62ac5ea3f346a2ccbc39b8c909395655b3134a189021e8c02fdd001fb2fe544f012e18dffb14e369a79a6e
 Ubuntu_16.10_Yakkety-VB-64bit.7z


[1] http://paste.ubuntu.com/23664245/
[2]
https://github.com/Nitrokey/nitrokey-start-firmware/tree/gnuk1.2-regnual-fix/prebuilt
[3]
https://github.com/Nitrokey/nitrokey-start-firmware/tree/gnuk1.2-regnual-fix/prebuilt/RTM.1

-- 
Best regards,
Szczepan



More information about the gnuk-users mailing list