Pico commissionner not working

[Tartasprint]

Hello, first of all thank you for your amazing work !
I was able to set up a FIDO key on Pico2 following the instructions on picokeys.com:

1. download the firmware and write it from the getting started page
2. use the commisionner
   I tried to follow the same steps with the OpenGPG and HSM firmware, but the commissionner/browser/OS is not detecting the device properly. I am on Windows, and I tried both Chrome and Firefox (the latter only with WebAuthn).

Kleopatra (a GUI for gpg on windows) successfully detects the "smart card". I tried to use several trivial PINs, before finding out that the default PIN from the HSM firmware worked also on OpenGPG firmware. The behaviour is different, Kleopatra prompts for changes instead of saying "Incorrect PIN". At the last step I get "Conditions d'utilisations non-satisfaites" which translates to "Usage condition are not met/satisfied".

Did I miss a step between writing the firmware and commissionning it ? I did try to unplug and replug, even if it is not supposed be needed.

[polhenarejos]

Commissioner uses WebUSB and it requires permission from your browser. Check whether you granted the proper access.

[nmwael]

I seem to have the same problem, on pico_openpgp_waveshare_rp2040_plus_16mb-3.2 , version 3.4 is not booting on my board.

Attached screenshot of ui.

[MuRongPIG]

The same problem .I was using esp32-s3 and after commissioning the vid/pid turned 0000:0000 no matter what the preset vendor is. @polhenarejos Could you help check where the problem is? thank you! <3 (after flashing the vid/pid is normal FEFF:FCFD)

[MuRongPIG]

btw ,Can I change the vid/pid without the commissioner for esp32-s3? (like pico-fido)(because I dont know how to build for esp32)

[polhenarejos]

You need to use development firmware.

[petrm]

The same problem .I was using esp32-s3 and after commissioning the vid/pid turned 0000:0000 no matter what the preset vendor is. @polhenarejos Could you help check where the problem is? thank you! <3 (after flashing the vid/pid is normal FEFF:FCFD)

I am facing the same issue on rp2040, after using the commissioner the vid:pid is 0000:0000. Works fine with pico fido.

[mtorromeo]

Same issue with a rp2040 zero. The only discernible thing accomplished by the commissioner is turning the LED from red to green until the device is reset.

[mtorromeo]

The issue is not limited to the commissioner, actually the problem is that the firmware is not working correctly at all.

I tried compiling it by myself and the only difference was that the LED did not work at all (I am sure I am missing something), but the device was still recognized but with the wrong VID:PID 0000:0000, and this is the symptom of the real issue, since the default VID:PID is supposed to be FEFF:FCFD even when not using the commissioner.

So I tried to flash the older stable releases, one at a time, hoping to find one that worked, and I did.

The first working release was 2.0, which got me the blinking green led and the proper lsusb listing:

Bus 003 Device 016: ID feff:fcfd Pol Henarejos Pico Key

Something after that changed, and any release from 3.0 onward results in red LED and 0000:0000.

[mtorromeo]

Actually, a small correction: the last working release is v2.2 not v2.0. Sorry about that.

[mtorromeo]

I bisected commits from v2.2 to v3.0 and when I found the commit that updated pico-keys-sdk I started bisecting those commits and found the culprit in polhenarejos/pico-keys-sdk@0638409

Starting from the commit the vid:pid became 0000:0000.

Before that the device was recognized used 1234:5678, even when led became solid red, or blinking red before that, and solid even cyan at one point.

lsusb output at commit polhenarejos/pico-keys-sdk@802df9e:

Bus 003 Device 085: ID 1234:5678 Brain Actuated Technologies Pico Key

lsusb output at commit polhenarejos/pico-keys-sdk@0638409:

Bus 003 Device 087: ID 0000:0000 Pol Henarejos Pico Key

It's interesting that the device manufactured also changed between commits of pico-keys-sdk.