This repository is incomplete and under active development.

🐝 solo2 library and CLI

The device can in one of two modes (USB VID:PID in brackets):

regular mode (1209:BEEE)
bootloader mode (1209:B000)

In regular mode, only the CCID interface to apps is currently implemented. In bootloader mode, NXP's custom HID protocol is used (via lpc55-host).

Solo 2 is supported by Ludovic Rousseau's CCID driver, but there has not been a release. The included Info.plist works.

⚠ DANGER ⚠

If the firmware is invalid according to the bootloader, the device always stays in bootloader mode. This is OK.

BUT: If the firmware is valid according to the bootloader, and the device boots into it, but the firmware has issues (e.g., panics), the only way to get back into bootloader mode and flash a new firmware is by attaching a debugger.

This is quite fiddly, and needs a special cable. We recommend using NXP's development board instead.

Installation

cargo install solo2

For experimental "PKI lite" support, use cargo install --features dev-pki solo2. This is not intended to and will not grow into full PKI creation + management functionality, the goal is only to enable developing and testing all functionality of all official apps.

Examples

If the key is in regular mode, and its firmware contains the admin app:

solo2 app admin uuid reads out the serial number.
solo2 app admin boot-to-bootrom switches to bootloader mode.

If the key is in regular mode, and its firmware contains the NDEF app:

solo2 app ndef capabilities reads out the NDEF capabilities.

If the key is in bootloader mode:

solo2 bootloader reboot switches to regular mode (if the firmware is valid).

Note that subcommands are inferred, so e.g. solo2 b r works like solo2 bootloader reboot.

Logging

Uses pretty_env_logger. For instance, set SOLO2_LOG=info in the environment.

License

SoloKeys is fully open source.

All software, unless otherwise noted, is dual licensed under Apache 2.0 and MIT. You may use SoloKeys software under the terms of either the Apache 2.0 license or MIT license.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

All hardware, unless otherwise noted, is licensed under CERN-OHL-S-2.0.

All documentation, unless otherwise noted, is licensed under CC-BY-SA-4.0.