UsbKeyboard driver not recognizing keyboards #14
Comments
|
A friend of mine also reported he is not able to make it work (I have not tried yet) . I will ask kim for details. @cristianoag, I am working in the flash tool because it does not work for 39sf040 because it has different operation bytecodes. Maybe you are also interesed in the discussion. You can see it at #1 |
|
Cristiano, Issalig, please check the MSXUSB version I just checked in. I fixed an issue in the USB STALL mechanism. When a device is not ready it STALLs and then the driver just has to retry after clearing the STALL situation. Somehow the CH376s does not report the status of this correctly and the driver thought it was failing. As a result the keyboard (and other devices) where not recognised at start. You should see a message at MSX start saying:
Where x is bigger or equal to 1, depending if you run behind an USB Hub. |
|
Nice, it is good to see some progress here! I am testing in a real VG8020 MSX1 with a usb hub, a usb drive formatted as 720kb and a keyboard and the new version of MSXUsbHost (nextor.rom) I get correctly the 3 devices (Hub, usb drive and keyboard but I had to capture video and pause it, because this message appears just some ms, maybe a 1s delay would be nice Then tried usbkeybd.com but it gets an error. Is this the right way of using it?
|
|
Now it loads but nothing happens, I mean when I press keys in the keyboard nothing appears. (I use a logitech k120 usb keyboard) @cristianoag did you manage to make it work?
|
|
You should see a couple of messages appearing after running usbkeybd.com and the UNAPI driver should be running. Don’t know how this works on an MSX1 so that might explain what you see. I’ll test this later tonight.
From: issalig ***@***.***>
Date: Tuesday, 15 March 2022 at 12:14
To: S0urceror/MSX-USB ***@***.***>
Cc: S0urceror ***@***.***>, Comment ***@***.***>
Subject: Re: [S0urceror/MSX-USB] UsbKeyboard driver not recognizing keyboards (Issue #14)
Now it loads but nothing happens, I mean when I press keys in the keyboard nothing appears. (I use a logitech k120 usb keyboard)
Also I noticed caps/numeric leds do not work.
@cristianoag<https://github.com/cristianoag> did you manage to make it work?
[image]<https://user-images.githubusercontent.com/7136948/158365521-9fadd6cf-6447-4324-b946-76c8ebaceb52.png>
—
Reply to this email directly, view it on GitHub<#14 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGC6KDKUS2COUELH4XT2T3VABWITANCNFSM5PC6V5DQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
I tested earlier today with real hardware (both MSX1 and MSX2). It is not working. On MSX2, it is not recognizing any of the USB hubs I have (I tested 4, powered and not powered), with the previous version it does say I have multiple USB devices connected but doesn't differentiate the hub from the USB storage device that contains MSX DOS and the utilities I need to load the driver. With my MSX1 is even worse, it starts the boot sequence and after a few seconds says "out of memory".
Another strange symptom is that sometimes with MSX2, it starts the boot sequence and then just restart the computer after a few seconds.
I believe this new version is worse than the previous @***@***.***>. How did you test? Only with the OpenMSX or with real hardware?
Cristiano
From: S0urceror ***@***.***>
Sent: Tuesday, March 15, 2022 10:06 AM
To: S0urceror/MSX-USB ***@***.***>
Cc: Cristiano Goncalves ***@***.***>; Mention ***@***.***>
Subject: Re: [S0urceror/MSX-USB] UsbKeyboard driver not recognizing keyboards (Issue #14)
You should see a couple of messages appearing after running usbkeybd.com and the UNAPI driver should be running. Don't know how this works on an MSX1 so that might explain what you see. I'll test this later tonight.
From: issalig ***@***.***<mailto:***@***.***>>
Date: Tuesday, 15 March 2022 at 12:14
To: S0urceror/MSX-USB ***@***.***<mailto:***@***.***>>
Cc: S0urceror ***@***.***<mailto:***@***.***>>, Comment ***@***.***<mailto:***@***.***>>
Subject: Re: [S0urceror/MSX-USB] UsbKeyboard driver not recognizing keyboards (Issue #14)
Now it loads but nothing happens, I mean when I press keys in the keyboard nothing appears. (I use a logitech k120 usb keyboard)
Also I noticed caps/numeric leds do not work.
@cristianoag<https://github.com/cristianoag> did you manage to make it work?
[image]<https://user-images.githubusercontent.com/7136948/158365521-9fadd6cf-6447-4324-b946-76c8ebaceb52.png>
-
Reply to this email directly, view it on GitHub<#14 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGC6KDKUS2COUELH4XT2T3VABWITANCNFSM5PC6V5DQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID: ***@***.***<mailto:***@***.***>>
-
Reply to this email directly, view it on GitHub<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FS0urceror%2FMSX-USB%2Fissues%2F14%23issuecomment-1067966333&data=04%7C01%7C%7Cca9d767c52d744299f6808da06847ee8%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637829463394949189%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=g26FJ%2BvsliG%2B6VoTK54MHmFq5KBVqLmQlF8ulDKwzZk%3D&reserved=0>, or unsubscribe<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALSAPKR7SCRGQ7L34ERHVATVACDJ7ANCNFSM5PC6V5DQ&data=04%7C01%7C%7Cca9d767c52d744299f6808da06847ee8%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637829463394949189%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=PhywaYRLVaTIu9U4GlN8547yC2MYpURwcm6OSjG35uI%3D&reserved=0>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
|
I tested this with OpenMSX and the test board. I think you are right I should have done extensive testing on real hardware before calling it fixed. I’ll try to reserve some time for this later this week and let you know.
Email written on my mobile device
…________________________________
From: Cristiano Goncalves ***@***.***>
Sent: Monday, March 21, 2022 2:36:05 AM
To: S0urceror/MSX-USB ***@***.***>
Cc: S0urceror ***@***.***>; Comment ***@***.***>
Subject: Re: [S0urceror/MSX-USB] UsbKeyboard driver not recognizing keyboards (Issue #14)
I tested earlier today with real hardware (both MSX1 and MSX2). It is not working. On MSX2, it is not recognizing any of the USB hubs I have (I tested 4, powered and not powered), with the previous version it does say I have multiple USB devices connected but doesn't differentiate the hub from the USB storage device that contains MSX DOS and the utilities I need to load the driver. With my MSX1 is even worse, it starts the boot sequence and after a few seconds says "out of memory".
Another strange symptom is that sometimes with MSX2, it starts the boot sequence and then just restart the computer after a few seconds.
I believe this new version is worse than the previous @***@***.***>. How did you test? Only with the OpenMSX or with real hardware?
Cristiano
From: S0urceror ***@***.***>
Sent: Tuesday, March 15, 2022 10:06 AM
To: S0urceror/MSX-USB ***@***.***>
Cc: Cristiano Goncalves ***@***.***>; Mention ***@***.***>
Subject: Re: [S0urceror/MSX-USB] UsbKeyboard driver not recognizing keyboards (Issue #14)
You should see a couple of messages appearing after running usbkeybd.com and the UNAPI driver should be running. Don't know how this works on an MSX1 so that might explain what you see. I'll test this later tonight.
From: issalig ***@***.***<mailto:***@***.***>>
Date: Tuesday, 15 March 2022 at 12:14
To: S0urceror/MSX-USB ***@***.***<mailto:***@***.***>>
Cc: S0urceror ***@***.***<mailto:***@***.***>>, Comment ***@***.***<mailto:***@***.***>>
Subject: Re: [S0urceror/MSX-USB] UsbKeyboard driver not recognizing keyboards (Issue #14)
Now it loads but nothing happens, I mean when I press keys in the keyboard nothing appears. (I use a logitech k120 usb keyboard)
Also I noticed caps/numeric leds do not work.
@cristianoag<https://github.com/cristianoag> did you manage to make it work?
[image]<https://user-images.githubusercontent.com/7136948/158365521-9fadd6cf-6447-4324-b946-76c8ebaceb52.png>
-
Reply to this email directly, view it on GitHub<#14 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGC6KDKUS2COUELH4XT2T3VABWITANCNFSM5PC6V5DQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID: ***@***.***<mailto:***@***.***>>
-
Reply to this email directly, view it on GitHub<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FS0urceror%2FMSX-USB%2Fissues%2F14%23issuecomment-1067966333&data=04%7C01%7C%7Cca9d767c52d744299f6808da06847ee8%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637829463394949189%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=g26FJ%2BvsliG%2B6VoTK54MHmFq5KBVqLmQlF8ulDKwzZk%3D&reserved=0>, or unsubscribe<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALSAPKR7SCRGQ7L34ERHVATVACDJ7ANCNFSM5PC6V5DQ&data=04%7C01%7C%7Cca9d767c52d744299f6808da06847ee8%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637829463394949189%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=PhywaYRLVaTIu9U4GlN8547yC2MYpURwcm6OSjG35uI%3D&reserved=0>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
—
Reply to this email directly, view it on GitHub<#14 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGC6KEQAMZKWAFQWLLAUPLVA7HALANCNFSM5PC6V5DQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
We can close this one. Keyboard need to follow the specifications to be recognized ok. I got a few already working. |
|
Can you post the keyboard models that work? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Opening this one so we can invest time to discover the reason the UsbKeyboard driver is not recognizing keyboards that it is supposed to support.
The text was updated successfully, but these errors were encountered: