Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please allocate VID:PID
1209:5453to TapShard.TapShard is a battery-powered TOTP token on an nRF52840 Pro Micro /
SuperMini-style board, running upstream Zephyr. It types codes over BLE HID on
button press. Its USB interface is a Mass Storage configuration drive: users
edit
config.iniwith a text editor, without a companion application.mi-v)https://github.com/mi-v/tapshard/blob/main/THIRD_PARTY.md
bootloader contains no USB implementation; factory recovery keeps the
existing board bootloader's USB identity.
This is a firmware project for existing boards, with documented battery and
button wiring rather than a new custom PCB. Linux and Windows configuration,
pairing, and keyboard operation have been tested on hardware. A project PID
would provide a consistent configuration-device identity across installations
and allow distributing ready-to-install firmware instead of requiring each
user to obtain an ID and rebuild. The source currently defaults to private-test
1209:0001; the allocated PID will be adopted after approval.