-
Notifications
You must be signed in to change notification settings - Fork 890
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hid-keyboard not working on nvidia agx orin #4267
Comments
Is the NVIDIA AGX Orin you mentioned the one from the following URL? Does it recognize other keyboards? For example, does it recognize ones made with Arduino? https://connecttech.com/product/hadron-carrier-for-nvidia-jetson-orin-nx/ If it works with Arduino but not with TinyGo's hid-keyboard, there is likely a difference in USB enumeration. I would like you to try creating a simple keyboard with Arduino to see if it works. @dwSun |
The device you've linked is one type, whereas I'm using a different model. According to the tests conducted by the device supplier, NVIDIA Orin devices can recognize standard keyboards and mice, but they are unable to identify the tinygo hid-keyboard. I don't have an Arduino device at hand; however, I do possess an ESP32-C3 device. When attempting to compile, the following error message is displayed:
I will attempt to use an Arduino Nano to see if it succeeds. |
You need to specify an actual board, you cannot just name the processor. For example: tinygo flash -target xiao-esp32c3 . |
You can create an Arduino environment using the RP2040. If you let me know which RP2040 board you are using, I might be able to create it as well. |
Thank you, but I have tried all possible device targets and none have been successful.
|
The following is not made by me, but it's firmware for a keyboard using the RP2040-Zero. It is created with QMK Vial. Please try writing this UF2 to your board and see if it is recognized as a keyboard. https://darakuneko.booth.pm/items/4557796 |
thanks. This firmware is functional, recognizable, and supports character input, having been tested on the following systems:
Within these systems, the keyboard is identified as:
Accordingly, the failure to recognize the |
I have created a custom keyboard using QMK firmware, and in terms of key functions alone, this keyboard already satisfies my usage requirements. However, implementing custom features like LED blinking and buzzer control with QMK code can be somewhat cumbersome. I remain interested in utilizing TinyGo for this custom keyboard project. Therefore, please continue to attempt to resolve this issue when it is convenient and time permits. thanks. |
@dwSun I suspect one of the following causes:
|
To write the firmware, use the following command:
On a Mac, it is recognized as:
On Debian Sid, it is identified as:
On Ubuntu 20.04 (x86), it is recognized as:
On all the above-tested machines, the device responds to the initial input but fails to respond to subsequent inputs, requiring a re-plug to again react to the first input and then ignore further inputs. On Ubuntu 18.04 (NVIDIA Jetson Nano), it is identified as:
On this device, it only acknowledges with "AT" upon plug-in; manual inputs thereafter receive no response. On both Ubuntu 20.04 NVIDIA Jetson AGX Orin (JetPack 5.1.2) and Ubuntu 20.04 NVIDIA Jetson Orin Nano (JetPack 5.1.1), the device is not recognized, and cannot be found via |
I plan to make the USB enumeration process more similar to what is done with QMK Vial. I will create this in the near future, so please test the connection when it is ready. @dwSun |
I've created a small keyboard using the RP2040, utilizing the code from hid-keyboard. This keyboard has been successfully tested on every other computer in the office, including:
It functions properly on all the aforementioned hardware. However, on the NVIDIA AGX Orin (running Ubuntu 20.04 with JetPack 5.1.2), the keyboard is not recognized, and it doesn't even show up when using lsusb.
Could you please advise where I should start troubleshooting to enable this keyboard to work correctly on the NVIDIA AGX Orin?
The text was updated successfully, but these errors were encountered: