S0urceror
commented
2 years ago I saw you mentioned this on your GitHub. I haven’t come across this but maybe my endpoints on all 5 or so usb sticks where all the same.
In my setup I have a CH376s module on a breadboard connected to a Teensy. The Teensy is just kind of a relay to the CH376s. Then I have patched OpenMSX to have a virtual MSXUSB cartridge that sends the commands to the Teensy.
This way it behaves like in a real MSX with some timing differences. This enables me to load up everything and also use the OpenMSX debugger. I even rolled my own version of Dezog so that I can step through my assembly code in Visual Studio Code.
Maybe I should make a full write up of this.
PS. I will make a Mac and Windows build of OpenMSX and share it on GitHub this way you can maybe also take the Arduino route and create an emulator.
PS2. While I’m at it I will also check what the endpoint issue is.
Get Outlook for iOShttps://aka.ms/o0ukef
From: issalig @.> Sent: Tuesday, December 28, 2021 11:45:14 PM To: S0urceror/MSX-USB @.> Cc: Subscribed @.***> Subject: [S0urceror/MSX-USB] USB drive support (Issue #9)
I have been able to connect with usb drives with the following values l usb -v | grep bEndpointAddress
WORK bEndpointAddress 0x01 EP 1 OUT bEndpointAddress 0x82 EP 2 IN WORK bEndpointAddress 0x01 EP 1 OUT bEndpointAddress 0x81 EP 1 IN
DOES NOT WORK bEndpointAddress 0x81 EP 1 IN bEndpointAddress 0x02 EP 2 OUT
I checked the one that does not work under serial protocol ch376s and it works for parallel I can read the FAT type so I assume hardware is ok and the problem is in the rom.
I have modified the rom and I am printing the communication with ch376s for working and non working usbs. However, this is a tedious process (modify code,flash memory with tl866, extract memory, insert into cartridge, power up, test) and I do not still have a solution. How do you do the development? From the video you sent, it looks like you are simulating it, FPGA?
— Reply to this email directly, view it on GitHubhttps://github.com/S0urceror/MSX-USB/issues/9, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABGC6KHHOVHFFFM3BVRKCJLUTI4XVANCNFSM5K44Q2NA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://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 are subscribed to this thread.Message ID: @.***>
issalig
cristianoag
I have been able to connect with usb drives with the following values l usb -v | grep bEndpointAddress
WORK bEndpointAddress 0x01 EP 1 OUT bEndpointAddress 0x82 EP 2 IN
WORK bEndpointAddress 0x01 EP 1 OUT bEndpointAddress 0x81 EP 1 IN
DOES NOT WORK bEndpointAddress 0x81 EP 1 IN bEndpointAddress 0x02 EP 2 OUT
I checked the one that does not work under serial protocol ch376s and it works and for parallel I can read the FAT type so I assume hardware is ok and the problem is in the rom code.
I have modified the rom and I am printing the communication with ch376s for working and non working usbs. However, this is a tedious process (modify code,flash memory with tl866, extract memory, insert into cartridge, power up, test) and I do not still have a solution. How do you do the development? From the video you sent, it looks like you are simulating it, FPGA?
Excuse for my ignorance, but given for the use case that there is only one device, I think it should be an easier way to bind it to 1. Other projects just set address to 1 0x45 0x01, then select device 1 0x13 0x01 and configuration 1 0x49 0x01
I would like to contribute to your project by fixing this bug/feature but I do not know exactly where else to look.