Open source hardware TOTP token. Currently targets the LPC1756, LPC1758 and LPC1759 (with a small change it should also run on the LPC1754).
- keys never leave the token after setup
- support for 6 and 8 digit tokens
- enter button types 6/8 digit token using HID keyboard (any device that supports HID keyboards should work)
- supports up to 32 profiles
- rechargable RTC battery
- USB mode to add/delete profiles using a CSV file (supports base32, hex and hex string)
- support to change the RTC calibration values in the settings
- support for setting the time + timezone (currently only GMT)
- 60 seconds screen timeout
- support for different intervals (supports 1 - 180 seconds)
Images can be found in the project logs at hackaday
- encrypt profiles
- add support for more than 32 profiles (needs a rework if more profiles are required. The profiles are copied to ram and there is not enough for more at the moment. If we leave them in flash we can store a lot more)
- rework the calibration and time settings screens
TOTP uses klib. This repo can be cloned in the klib project folder. See build.yml for more info on compiling this project.
Is intended to be used with USB dfu bootloader. To build without bootloader support delete set(TARGET_LINKERSCRIPT ...) from the CMakeLists.txt in this project.
The LPC1756 does not have enough ram to hold a full framebuffer (240 * 135 * 2 = 64'800 bytes). To work around this issue, we use 2 smaller framebuffers we alternate between. While one framebuffer is being transferred to the screen using DMA we fill the other.
To make it easier (for me) the whole screen is written to this smaller framebuffer. The pixels that do not fit the framebuffer are thrown away. This does waste CPU cycles but is not limiting the framerate. Filling a full frame with pixels takes around 6 milliseconds. Writing a full frame of framebuffers takes around 11 milliseconds. This limits the maximum framerate to ≈ 85FPS. To get a consistant frame rate there is a limit of 60FPS.
The main screen takes the longest to draw. This is caused by the amount of pixels of the circle it needs to draw. The circle is generated on compile time to work around that the LPC175x family does not have a FPU. These generated pixels use 8640 bytes of flash.