Git-Mirrors/tillitis-key
1
0
Fork 0
mirror of https://github.com/tillitis/tillitis-key1.git synced 2024-10-01 01:45:38 -04:00
Code Issues Packages Projects Releases Wiki Activity
70f5cbf22e
tillitis-key/doc/release_notes.md
Joachim Strömbergson 97c0a2152e
Prepare for new official release, add initial context 
Signed-off-by: Joachim Strömbergson <joachim@assured.se>
2022-11-30 14:12:35 +01:00

2.5 KiB
Raw Blame History

Release Notes

Descriptions of the tagged TKey releases.

Tag XYZ

XYZ is a general release of the development kit first presented as a limited engineering-release. The main changes ar polishing, completion and bug fixing since the engineering-release.

New and improved functionality

  • (HW) The rosc TRNG has now been completed and tested. The TRNG can now be used to generate seeds by applicaitons.

  • (HW) The main clock frequency has been increased to 18 MHz.

  • (HW) The FW now has a separate RAM used during loading and measurement of applications.

  • (HW) The UART Rx FIFO is now able to handle 512 bytes.

  • (HW) The UART default bitrate has been icreased to 62500 bps.

  • (FW) The firmware has been restructured to be a Finite State Machine (FSM) with defined states for booting, loading applications, measure applications, calculate the CDI and start the loaded application.

Limititations

User Supplied Secret - Breaking change!

Nota bene From commit 99efb78ed8 the computed CDI secret is also taking the User Supplied Secret into account even if the USS is not supplied! This means if you start using firmware from this commit and onwards your CDI and with it the private key of the signerapp will change even if you haven't changed the app in any way.

engineering-release-1

Hardware

Limitations

  • The entropy generated by the TRNG has not yet been thoroughly tested, and the generator has not been adjusted to generate good, unbiased randomness. Any application that wants to use the entropy source SHOULD NOT use the output directly, but only as seed to a Digital Random Bit Generator (DRBG), such as Hash_DRBG.

  • The UART is currently running at 38400 bps. Future releases will increase the bitrate when communication at higher bitrates has been verified as stable and error free.

  • The internal clock frequency is currently limited to 12 MHz. Future releases will increase the clock frequency to provide improved performance.

  • The functionality in the firmware is currently not exposed to the applications via a stable name space, API. Future releases will provide access to FW functions such as the BLAKE2s hash function.

  • The timer currently does not include a timeout interrupt. Applications using the timer must check the status in order to detect a timeout event.

  • The timer currently does not provide a set of typical settings. Applications using the timer must set timer and prescaler as needed to get the desired time given the current clock speed.