Host setup and compatibility¶
Most OpenPGP problems are host problems first.
Pico OpenPGP is a CCID smart-card device, so the minimum host stack is not optional:
- PC/SC must be running
- the reader must be recognized
- the middleware must know how to talk to the card
- the client tool must expose the workflow you want
Check the card is visible¶
Start with the boring check first:
gpg --card-status
If that fails, do not jump straight into key generation or card policy changes.
Upstream also explicitly points to:
- OpenSC
- PKCS#11-capable applications
pkcs15-tool
So a sensible validation order is:
- confirm enumeration at the operating-system level
- confirm PC/SC is running
- confirm
gpg --card-statusor an equivalent read-only command works - only then test a PIN-gated operation
VID/PID and middleware recognition¶
The upstream README is explicit about a recurring CCID problem: host middleware may need the device identity to be recognized correctly.
In practice that can mean:
- using PicoKey App to help commission the board
- building with a chosen VID/PID
- adjusting local driver or middleware configuration
This is annoying, but it is normal in the smart-card ecosystem.
Warning
"The board flashed successfully" and "the host stack will recognize the device properly" are different conditions.
What usually works¶
When the host is healthy, the straightforward paths are usually:
- card detection
- metadata and status reads
- mainstream signing and decryption flows through GnuPG or OpenSC-backed clients
What is more uneven¶
The less predictable paths are:
- advanced card management
- specialized APDU sequences
- AES-related functionality
- client behaviors that depend on a tool exposing a newer OpenPGP card feature cleanly
Recommended compatibility checklist¶
For every platform you want to call supported, verify at least:
- card detection
gpg --card-status- one
PW1-gated action - one
PW3-gated action - one signing operation
- one decryption operation if you need it
If that checklist is not repeatable, the platform is not really validated yet.