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

Can not recorgnize in window server 2019 #92

New Issue
Closed
opened 2025-01-22 09:12:39 +08:00 by lijicheng168 · 12 comments
lijicheng168 commented 2025-01-22 09:12:39 +08:00 (Migrated from github.com)
Copy Link

Can not recorgnize in window server 2019. Can you test it?

Can not recorgnize in window server 2019. Can you test it?
polhenarejos commented 2025-01-22 15:46:33 +08:00 (Migrated from github.com)
Copy Link

What do you mean by recognized?

What do you mean by recognized?
lijicheng168 commented 2025-01-24 16:40:42 +08:00 (Migrated from github.com)
Copy Link

After tested it, I found that it will have a same situation when I push the reset button.

Image
Maybe caused by the init step.
When the system comunicate with board by usb. But the board has pass the init step.

After tested it, I found that it will have a same situation when I push the reset button. ![Image](https://github.com/user-attachments/assets/df8d41d3-91cd-45bb-9d37-bbdd26f23999) Maybe caused by the init step. When the system comunicate with board by usb. But the board has pass the init step.
polhenarejos commented 2025-01-25 00:29:38 +08:00 (Migrated from github.com)
Copy Link

But does it work with a browser?

But does it work with a browser?
lijicheng168 commented 2025-01-26 10:18:56 +08:00 (Migrated from github.com)
Copy Link

But does it work with a browser?

Yes, the USB cannot be successfully started. It also cannot be used in the browser.
After repeated attempts, it should now be possible to determine where the problem occurs.
I think there is a problem when the system tries to connect to the USB twice. The situation can be abstracted as if I attach a battery or external power supply to the pico, I disconnect the USB connection from the computer and re-insert the connection, but the rp2040 does not restart, but it is equivalent to re-initiating the USB handshake.
Why does this happen?
I think my fido is integrated into the keyboard, so sometimes disconnecting does not cause the rp2040 to restart.
If I do not disconnect the power, but just unload and load the USB device in the computer, the rp2040 will not re-execute the USB initialization and handshake process. This will cause problems.
I think there is a problem when handling the USB disconnection and reconnection.
Can you handle this situation in detail?

To reproduce this error, you can download the tool
https://www.uwe-sieber.de/usbtreeview_e.html#download
Right-click the device and click "restart port"

> But does it work with a browser? Yes, the USB cannot be successfully started. It also cannot be used in the browser. After repeated attempts, it should now be possible to determine where the problem occurs. I think there is a problem when the system tries to connect to the USB twice. The situation can be abstracted as if I attach a battery or external power supply to the pico, I disconnect the USB connection from the computer and re-insert the connection, but the rp2040 does not restart, but it is equivalent to re-initiating the USB handshake. Why does this happen? I think my fido is integrated into the keyboard, so sometimes disconnecting does not cause the rp2040 to restart. If I do not disconnect the power, but just unload and load the USB device in the computer, the rp2040 will not re-execute the USB initialization and handshake process. This will cause problems. I think there is a problem when handling the USB disconnection and reconnection. Can you handle this situation in detail? To reproduce this error, you can download the tool https://www.uwe-sieber.de/usbtreeview_e.html#download Right-click the device and click "restart port"
polhenarejos commented 2025-01-31 19:08:37 +08:00 (Migrated from github.com)
Copy Link

There was a problem with the keyboard interface and Windows that might be related with your issue, see #97. Can you test the latest nightly development build?

There was a problem with the keyboard interface and Windows that might be related with your issue, see #97. Can you test the latest nightly development build?
lijicheng168 commented 2025-02-07 10:00:43 +08:00 (Migrated from github.com)
Copy Link

There was a problem with the keyboard interface and Windows that might be related with your issue, see #97. Can you test the latest nightly development build?

I use 6265992162. Still not work.
I got an usb hub between the pico and pc. The usb not handle right.

> There was a problem with the keyboard interface and Windows that might be related with your issue, see [#97](https://github.com/polhenarejos/pico-fido/issues/97). Can you test the latest nightly development build? I use 62659921628a68475cd10de34980331b7df17cb6. Still not work. I got an usb hub between the pico and pc. The usb not handle right.
polhenarejos commented 2025-02-07 15:33:35 +08:00 (Migrated from github.com)
Copy Link

Try using the nightly development build.

Try using the nightly development build.
lijicheng168 commented 2025-02-07 16:53:29 +08:00 (Migrated from github.com)
Copy Link

Try using the nightly development build.

That's the nightly development build.

> Try using the nightly development build. That's the nightly development build.
polhenarejos commented 2025-02-07 17:04:35 +08:00 (Migrated from github.com)
Copy Link

But the nightly dev build does not use commit 6265992. How are you sure?

But the nightly dev build does not use commit 6265992. How are you sure?
lijicheng168 commented 2025-02-08 08:09:58 +08:00 (Migrated from github.com)
Copy Link

Image
Could you please give me a link? I use the waveshare zero.

![Image](https://github.com/user-attachments/assets/93c52ffd-a064-49f2-8051-20f590476db6) Could you please give me a link? I use the `waveshare zero`.
lijicheng168 commented 2025-02-08 08:44:59 +08:00 (Migrated from github.com)
Copy Link

I still use 353d782970 build and doesn't work too.

Image
Cmake options

-DPICO_BOARD=waveshare_rp2040_zero -DENABLE_UP_BUTTON=0 -DVIDPID=Yubikey5 -DENABLE_DELAYED_BOOT=1

The usb is flashing, but usb not work well. The system not start the device successful.
In UsbTreeView the good device looks like

Image

I still use 353d78297053c814aa7c182292644e007381a932 build and doesn't work too. ![Image](https://github.com/user-attachments/assets/1d05acba-1f17-4fe0-b386-bc009df609cd) Cmake options ``` -DPICO_BOARD=waveshare_rp2040_zero -DENABLE_UP_BUTTON=0 -DVIDPID=Yubikey5 -DENABLE_DELAYED_BOOT=1 ``` The usb is flashing, but usb not work well. The system not start the device successful. In `UsbTreeView` the good device looks like ![Image](https://github.com/user-attachments/assets/6820ada5-5605-4fbf-bcf8-a135a155b857)
lijicheng168 commented 2025-02-20 11:44:08 +08:00 (Migrated from github.com)
Copy Link

I notice that you only have

void tud_mount_cb() {
    mounted = true;
}

There is no tud_umount_cb() which maybe fix this?

I notice that you only have ``` void tud_mount_cb() { mounted = true; } ``` There is no `tud_umount_cb()` which maybe fix this?
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#92
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?