dearsky/pico-fido
1
0
Fork 0
Code Issues 46 Pull Requests 1 Actions Packages Projects Releases 22 Wiki Activity

what happened with pico commissioner and about other devices firmware support #247

New Issue
Closed
opened 2026-01-10 15:13:42 +08:00 by editznmemes · 21 comments
editznmemes commented 2026-01-10 15:13:42 +08:00 (Migrated from github.com)
Copy Link

i was testing my custom firmware after that i flash the old one had then saw in github all things are gone why ? the app is good but atleast keep the commsion maybe just VID and PID functionalty

i was testing my custom firmware after that i flash the old one had then saw in github all things are gone why ? the app is good but atleast keep the commsion maybe just VID and PID functionalty
zyp114514 commented 2026-01-10 19:33:15 +08:00 (Migrated from github.com)
Copy Link

The only one way is build it by your self

The only one way is build it by your self
PaddyPat commented 2026-01-10 22:35:43 +08:00 (Migrated from github.com)
Copy Link

he removed also wayback machine, shitty move,.. project is dead

he removed also wayback machine, shitty move,.. project is dead
👍 16
gitxmax commented 2026-01-10 23:31:47 +08:00 (Migrated from github.com)
Copy Link

Just received 2 S3 board and found that it's actually an expensive project to run. The license cost is obnoxious for per key. I tried to compile from source with PICO_SDK_PATH=~/stm32/pico-fido/pico-keys-sdk/ cmake .. -DPICO_BOARD=board_type=Fido -VIDPID=Yubikey5 but getting an error
CMake Error: Unknown argument -VIDPID=Yubikey5

Just received 2 S3 board and found that it's actually an expensive project to run. The license cost is obnoxious for per key. I tried to compile from source with PICO_SDK_PATH=~/stm32/pico-fido/pico-keys-sdk/ cmake .. -DPICO_BOARD=board_type=Fido -VIDPID=Yubikey5 but getting an error CMake Error: Unknown argument -VIDPID=Yubikey5
editznmemes commented 2026-01-10 23:52:26 +08:00 (Migrated from github.com)
Copy Link

Just received 2 S3 board and found that it's actually an expensive project to run. The license cost is obnoxious for per key. I tried to compile from source with PICO_SDK_PATH=~/stm32/pico-fido/pico-keys-sdk/ cmake .. -DPICO_BOARD=board_type=Fido -VIDPID=Yubikey5 but getting an error CMake Error: Unknown argument -VIDPID=Yubikey5

Yeah you have provide the hex identifier basically if you remmeber in commisner app

> Just received 2 S3 board and found that it's actually an expensive project to run. The license cost is obnoxious for per key. I tried to compile from source with PICO_SDK_PATH=~/stm32/pico-fido/pico-keys-sdk/ cmake .. -DPICO_BOARD=board_type=Fido -VIDPID=Yubikey5 but getting an error CMake Error: Unknown argument -VIDPID=Yubikey5 Yeah you have provide the hex identifier basically if you remmeber in commisner app
editznmemes commented 2026-01-10 23:52:37 +08:00 (Migrated from github.com)
Copy Link

he removed also wayback machine, shitty move,.. project is dead

Yeah lol

> he removed also wayback machine, shitty move,.. project is dead Yeah lol
gitxmax commented 2026-01-10 23:55:21 +08:00 (Migrated from github.com)
Copy Link

Just received 2 S3 board and found that it's actually an expensive project to run. The license cost is obnoxious for per key. I tried to compile from source with PICO_SDK_PATH=~/stm32/pico-fido/pico-keys-sdk/ cmake .. -DPICO_BOARD=board_type=Fido -VIDPID=Yubikey5 but getting an error CMake Error: Unknown argument -VIDPID=Yubikey5

Yeah you have provide the hex identifier basically if you remmeber in commisner app

I have an original yubikey5, can I pull hex identifier somehow? Just wanted to have a cheap backup key..

> > Just received 2 S3 board and found that it's actually an expensive project to run. The license cost is obnoxious for per key. I tried to compile from source with PICO_SDK_PATH=~/stm32/pico-fido/pico-keys-sdk/ cmake .. -DPICO_BOARD=board_type=Fido -VIDPID=Yubikey5 but getting an error CMake Error: Unknown argument -VIDPID=Yubikey5 > > Yeah you have provide the hex identifier basically if you remmeber in commisner app I have an original yubikey5, can I pull hex identifier somehow? Just wanted to have a cheap backup key..
editznmemes commented 2026-01-10 23:58:58 +08:00 (Migrated from github.com)
Copy Link

Just received 2 S3 board and found that it's actually an expensive project to run. The license cost is obnoxious for per key. I tried to compile from source with PICO_SDK_PATH=~/stm32/pico-fido/pico-keys-sdk/ cmake .. -DPICO_BOARD=board_type=Fido -VIDPID=Yubikey5 but getting an error CMake Error: Unknown argument -VIDPID=Yubikey5

Yeah you have provide the hex identifier basically if you remmeber in commisner app

I have an original yubikey5, can I pull hex identifier somehow? Just wanted to have a cheap backup key..

I think you can but never done also . a way can be youtube vedio showcasing pico fido and then commisnor just get the VID from there

> > > Just received 2 S3 board and found that it's actually an expensive project to run. The license cost is obnoxious for per key. I tried to compile from source with PICO_SDK_PATH=~/stm32/pico-fido/pico-keys-sdk/ cmake .. -DPICO_BOARD=board_type=Fido -VIDPID=Yubikey5 but getting an error CMake Error: Unknown argument -VIDPID=Yubikey5 > > > > > > Yeah you have provide the hex identifier basically if you remmeber in commisner app > > I have an original yubikey5, can I pull hex identifier somehow? Just wanted to have a cheap backup key.. I think you can but never done also . a way can be youtube vedio showcasing pico fido and then commisnor just get the VID from there
lockedmutex commented 2026-01-11 00:11:06 +08:00 (Migrated from github.com)
Copy Link

@gitxmax @editznmemes

CMake Error: Unknown argument -VIDPID=Yubikey5

the argument is wrong, it should be - -DVIDPID=Yubikey5

Checkout my custom script that i use to build the project if it can help:
https://github.com/lockedmutex/pico-fido/blob/suyog-pico/patches/build.py

@gitxmax @editznmemes Also you can still commission, there are open source tools out there that you can use to commission the firmware, search and you will find it.

@gitxmax @editznmemes > CMake Error: Unknown argument -VIDPID=Yubikey5 the argument is wrong, it should be - `-DVIDPID=Yubikey5` Checkout my custom script that i use to build the project if it can help: https://github.com/lockedmutex/pico-fido/blob/suyog-pico/patches/build.py @gitxmax @editznmemes Also you can still commission, there are open source tools out there that you can use to commission the firmware, search and you will find it.
❤️ 4
gitxmax commented 2026-01-11 02:47:32 +08:00 (Migrated from github.com)
Copy Link

-DVIDPID=Yubikey5

thanks. I managed to compile the bin firmware with PICO_SDK_PATH=/home/balb/32/pico-fido/pico-sdk cmake .. -DVIDPID=Yubikey5 problem is, when I flash it, it doesn't work. I flashed the pico_fido_esp32-s3_7.0.bin file I downloaded in the repository and it seems to work fine. Any other Esp32-S3 /fido specific flags Ineed to pass to cmake when compiling?

> -DVIDPID=Yubikey5 thanks. I managed to compile the bin firmware with PICO_SDK_PATH=/home/balb/32/pico-fido/pico-sdk cmake .. -DVIDPID=Yubikey5 problem is, when I flash it, it doesn't work. I flashed the pico_fido_esp32-s3_7.0.bin file I downloaded in the repository and it seems to work fine. Any other Esp32-S3 /fido specific flags Ineed to pass to cmake when compiling?
lockedmutex commented 2026-01-11 03:38:19 +08:00 (Migrated from github.com)
Copy Link

@gitxmax wait you are compiling for esp32 s3 right? idt you need to pass the pico-sdk-path env variable? BTW you can run the following command to get all the flags u can pass to the final build command:

cmake -LAH .

Also if I am not wrong then these are all the flags you can pass:

-DENABLE_DELAYED_BOOT=ON|OFF
-DENABLE_EDDSA=ON|OFF
-DENABLE_OATH_APP=ON|OFF
-DENABLE_OTP_APP=ON|OFF
-DENABLE_POWER_ON_RESET=ON|OFF
-DVIDPID=Yubikey5
-DPICO_BOARD=pico2
-DPICO_PLATFORM=rp2350-arm-s
-DCMAKE_BUILD_TYPE=Release
-DPICO_DEBUG_INFO_IN_RELEASE=ON|OFF
-DPICO_DEOPTIMIZED_DEBUG=ON|OFF
-DPICO_STDIO_UART=ON|OFF
-DPICO_STDIO_USB=ON|OFF
-DPICO_STDIO_RTT=ON|OFF
-DPICO_STDIO_SEMIHOSTING=ON|OFF
-DPICO_SDK_PATH=/path/to/sdk
-DCMAKE_TOOLCHAIN_FILE=/path/to/toolchain.cmake
-DCMAKE_EXPORT_COMPILE_COMMANDS=ON
-DCMAKE_VERBOSE_MAKEFILE=ON
-DCMAKE_COLOR_MAKEFILE=ON

I might have missed some flags, but these are some of the flags u can pass, some of the above flags might not work, idk

also I think for esp32-s3 you will need to pass sdk path of esp32, more specifically esp-idf path if i am not wrong.

@gitxmax wait you are compiling for esp32 s3 right? idt you need to pass the pico-sdk-path env variable? BTW you can run the following command to get all the flags u can pass to the final build command: `cmake -LAH .` Also if I am not wrong then these are all the flags you can pass: ``` -DENABLE_DELAYED_BOOT=ON|OFF -DENABLE_EDDSA=ON|OFF -DENABLE_OATH_APP=ON|OFF -DENABLE_OTP_APP=ON|OFF -DENABLE_POWER_ON_RESET=ON|OFF -DVIDPID=Yubikey5 -DPICO_BOARD=pico2 -DPICO_PLATFORM=rp2350-arm-s -DCMAKE_BUILD_TYPE=Release -DPICO_DEBUG_INFO_IN_RELEASE=ON|OFF -DPICO_DEOPTIMIZED_DEBUG=ON|OFF -DPICO_STDIO_UART=ON|OFF -DPICO_STDIO_USB=ON|OFF -DPICO_STDIO_RTT=ON|OFF -DPICO_STDIO_SEMIHOSTING=ON|OFF -DPICO_SDK_PATH=/path/to/sdk -DCMAKE_TOOLCHAIN_FILE=/path/to/toolchain.cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON ``` I might have missed some flags, but these are some of the flags u can pass, some of the above flags might not work, idk also I think for esp32-s3 you will need to pass sdk path of esp32, more specifically esp-idf path if i am not wrong.
gitxmax commented 2026-01-11 03:45:44 +08:00 (Migrated from github.com)
Copy Link

cmake -LAH .

Thanks, will try that next

> cmake -LAH . Thanks, will try that next
metabo7000 commented 2026-01-11 16:21:16 +08:00 (Migrated from github.com)
Copy Link

@gitxmax @editznmemes

CMake hiba: Ismeretlen argumentum -VIDPID=Yubikey5

az érvelés hibás, annak kellene lennie --DVIDPID=Yubikey5

Nézd meg az egyéni szkriptemet, amit a projekt felépítéséhez használok, hátha az segít: https://github.com/lockedmutex/pico-fido/blob/suyog-pico/patches/build.py

@gitxmax @editznmemesEzenkívül továbbra is üzembe helyezheted, vannak nyílt forráskódú eszközök, amelyeket használhatsz a firmware üzembe helyezéséhez, keress rá, és megtalálod.

He uses another project and puts a paid license in it! Users will realize this in a short time! But this is not how marketing should be built if you want to make money from what you are building! Token2 is built nicely but there is almost no advertising behind it, that would be a success! Product descriptions should be replaced with video product advertisements!

> [@gitxmax](https://github.com/gitxmax) [@editznmemes](https://github.com/editznmemes) > > > CMake hiba: Ismeretlen argumentum -VIDPID=Yubikey5 > > az érvelés hibás, annak kellene lennie -`-DVIDPID=Yubikey5` > > Nézd meg az egyéni szkriptemet, amit a projekt felépítéséhez használok, hátha az segít: https://github.com/lockedmutex/pico-fido/blob/suyog-pico/patches/build.py > > [@gitxmax](https://github.com/gitxmax) [@editznmemes](https://github.com/editznmemes)Ezenkívül továbbra is üzembe helyezheted, vannak nyílt forráskódú eszközök, amelyeket használhatsz a firmware üzembe helyezéséhez, keress rá, és megtalálod. He uses another project and puts a paid license in it! Users will realize this in a short time! But this is not how marketing should be built if you want to make money from what you are building! Token2 is built nicely but there is almost no advertising behind it, that would be a success! Product descriptions should be replaced with video product advertisements!
My1 commented 2026-01-15 01:40:30 +08:00 (Migrated from github.com)
Copy Link

there being not much advertising is likely intentional as the picofido does come without attestation and all, which especially for services as AGOV and other e-government or banking services will definitely fail, would cause major support chaos, as people would likely just get it to save some money and then wonder why stuff doesnt work.

there being not much advertising is likely intentional as the picofido does come without attestation and all, which especially for services as AGOV and other e-government or banking services will definitely fail, would cause major support chaos, as people would likely just get it to save some money and then wonder why stuff doesnt work.
tokinasin commented 2026-01-17 20:19:06 +08:00 (Migrated from github.com)
Copy Link

It seems the patcher page is still accessible.
https://www.picokeys.com/pico-patcher/

It seems the patcher page is still accessible. https://www.picokeys.com/pico-patcher/
cinehorse commented 2026-01-18 04:38:02 +08:00 (Migrated from github.com)
Copy Link

It seems the patcher page is still accessible. https://www.picokeys.com/pico-patcher/

The patcher is also available offline in the source code, but since you have to configure the firmware for your board anyway, you'll set the PID:VID at the same time. Therefore, the link is just a nice-to-have feature, allowing you to quickly change the identifier.

> It seems the patcher page is still accessible. https://www.picokeys.com/pico-patcher/ The patcher is also available offline in the source code, but since you have to configure the firmware for your board anyway, you'll set the PID:VID at the same time. Therefore, the link is just a nice-to-have feature, allowing you to quickly change the identifier.
lockedmutex commented 2026-01-22 01:41:29 +08:00 (Migrated from github.com)
Copy Link

@gitxmax Prebuilt firmwares for all available boards if you are still having issues building the firmware, esp32 firmwares might be add soon in future: https://github.com/librekeys/pico-fido-firmwares/releases/tag/picofido-7.2-1

@gitxmax Prebuilt firmwares for all available boards if you are still having issues building the firmware, esp32 firmwares might be add soon in future: https://github.com/librekeys/pico-fido-firmwares/releases/tag/picofido-7.2-1
👍 2
KaustubhPatange commented 2026-01-26 22:31:13 +08:00 (Migrated from github.com)
Copy Link

Anyone looking for a CLI based commissioner tool check out my fork https://github.com/KaustubhPatange/pico-fido/tree/main/tools/commissioner-cli. It is still early and could contain bugs but it is free and does not require license.

Anyone looking for a CLI based commissioner tool check out my fork https://github.com/KaustubhPatange/pico-fido/tree/main/tools/commissioner-cli. It is still early and could contain bugs but it is free and does not require license.
👍 1
chengnan049 commented 2026-01-26 22:40:25 +08:00 (Migrated from github.com)
Copy Link

Just received 2 S3 board and found that it's actually an expensive project to run. The license cost is obnoxious for per key. I tried to compile from source with PICO_SDK_PATH=~/stm32/pico-fido/pico-keys-sdk/ cmake .. -DPICO_BOARD=board_type=Fido -VIDPID=Yubikey5 but getting an error CMake Error: Unknown argument -VIDPID=Yubikey5

Yeah you have provide the hex identifier basically if you remmeber in commisner app是的，你必须提供十六进制标识符，基本上如果你在Commisner应用里记得的话

I have an original yubikey5, can I pull hex identifier somehow? Just wanted to have a cheap backup key..我有一台原装Yubikey5，我能不能用某种方式提取十六进制标识符？只是想有把便宜的备用钥匙......

Yubikey 4/5 VID:1050,PID:0407

Source: https://support.yubico.com/s/article/YubiKey-USB-ID-values

> > > Just received 2 S3 board and found that it's actually an expensive project to run. The license cost is obnoxious for per key. I tried to compile from source with PICO_SDK_PATH=~/stm32/pico-fido/pico-keys-sdk/ cmake .. -DPICO_BOARD=board_type=Fido -VIDPID=Yubikey5 but getting an error CMake Error: Unknown argument -VIDPID=Yubikey5 > > > > > > Yeah you have provide the hex identifier basically if you remmeber in commisner app是的，你必须提供十六进制标识符，基本上如果你在Commisner应用里记得的话 > > I have an original yubikey5, can I pull hex identifier somehow? Just wanted to have a cheap backup key..我有一台原装Yubikey5，我能不能用某种方式提取十六进制标识符？只是想有把便宜的备用钥匙...... Yubikey 4/5 VID:1050,PID:0407 Source: https://support.yubico.com/s/article/YubiKey-USB-ID-values
lockedmutex commented 2026-01-26 23:04:46 +08:00 (Migrated from github.com)
Copy Link

@KaustubhPatange maybe you can help us with https://github.com/librekeys/picoforge

@KaustubhPatange maybe you can help us with https://github.com/librekeys/picoforge
KaustubhPatange commented 2026-01-26 23:16:38 +08:00 (Migrated from github.com)
Copy Link

@KaustubhPatange maybe you can help us with https://github.com/librekeys/picoforge

Woah I didn't knew about this, my use case was very limited so built a cli instead. Definitely gonna check this one and contribute as I learn.

> [@KaustubhPatange](https://github.com/KaustubhPatange) maybe you can help us with https://github.com/librekeys/picoforge Woah I didn't knew about this, my use case was very limited so built a cli instead. Definitely gonna check this one and contribute as I learn.
polhenarejos commented 2026-01-26 23:19:26 +08:00 (Migrated from github.com)
Copy Link

This issue has drifted away from its original purpose.

Please avoid using PicoKeys issues as a place to advertise or coordinate third-party tools or forks. Alternative projects are welcome in the ecosystem, but they should be discussed in their own repositories.

Further off-topic promotion will be moderated to keep the issue focused.

This issue has drifted away from its original purpose. Please avoid using PicoKeys issues as a place to advertise or coordinate third-party tools or forks. Alternative projects are welcome in the ecosystem, but they should be discussed in their own repositories. Further off-topic promotion will be moderated to keep the issue focused.
👍 2 👎 5
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dearsky
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dearsky/pico-fido#247
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?