Duffman wrote on 2022-11-11, 02:54:

@sofakng

I wouldn't rule out a power issue just yet, try with a separate powered USB hub and see if that works with it.

I've bought a NEC versa s260 laptop which has an EHCI controller with OHCI, I'm now testing with it.
I've got a different error, I'm gonna fix it first.

crazii wrote on 2022-10-07, 23:55:

sofakng wrote on 2022-10-07, 19:06:

OK - No problem... Thanks for the information. […]
Show full quote

OK - No problem... Thanks for the information.

However, I'm trying to use this on my weeCee x86 PC and when I plug the RetroWave into the PC, it causes the PC to reboot.

After the reboot, if I attempt to run RWDDOS.EXE it throws an assertion error:

After a few seconds, EMM386 also throws an error:

Sorry for the photos instead of screenshots.

Do you have any ideas?

I never tested OHCI on a real hardware. 🤣 I guess there's some bug in my code and it only works for VirtualBox emulation. Same thing happened when I test on QEMU and it works but crashes on real hardware and I fixed that.

Hey I've fixed 2 bugs and uploaded the new binary, you can try it. If it doesn't work, you can try the RWDDOSPM one which may be less buggy on memory mapping issue.
I tested both on my NEC versa S260 and it works good.

Hmmm, it still doesn't work but I think the problem is between the Vortex86 (weeCee PC) and the RetroWave PotatoPi Lite. (ie. the RetroWave OPL3 is connected to the PotatoPi Lite)

As I mentioned, when I plug the PotatoPi + OPL3 into the weeCee, the PC immediately reboots. I've tried using a USB Y-splitter (for adding additional power) but it doesn't seem to help.

RWWDOS:

RWDDOSPM:

Immediate reboot? I'll bet on a power issue. It maybe irrelevant but Before my NUC is dead, every time I plugged any USB device to the front panel the HDPMI signal is black out for once, I didn't pay attention and it finally died.
Meanwhile I'll talk to Sudomaker to check if there is any driver difference between lite and express.
I can make a debug version to see the logs, it might help.

Update: protected mode games support added.
Detail added in the original post.

sofakng wrote on 2022-12-05, 20:48:

Hmmm, it still doesn't work but I think the problem is between the Vortex86 (weeCee PC) and the RetroWave PotatoPi Lite. (ie. t […]
Show full quote

Hmmm, it still doesn't work but I think the problem is between the Vortex86 (weeCee PC) and the RetroWave PotatoPi Lite. (ie. the RetroWave OPL3 is connected to the PotatoPi Lite)

As I mentioned, when I plug the PotatoPi + OPL3 into the weeCee, the PC immediately reboots. I've tried using a USB Y-splitter (for adding additional power) but it doesn't seem to help.

RWWDOS:
IMG_6081.JPEG

RWDDOSPM:
IMG_6080.JPEG

I've attached more devices to my laptop and found 3 bugs and got them fixed. I think those bugs might relate to you problem. Did you have other USB divices attached? Or maybe other drivers/TSRs loaded. I guess you can try a clean boot with HIMEM.SYS and EMM386.EXE.
BTW if you still wanna try, here's my bug-fixed version, name changed to USBDDOSP.EXE and added some switches. you can use 'USBDDOSP.EXE /RW' to enable Retrowave OPL3.
--download link deleted, use original post's new uploads--

You can also test the newly added feature for USB disks (FATs FS only), use 'USBDDOSP.EXE /disk' to enable the USB disk feature, can be combined with /RW.
I'm trying to add keyboard & mouse support if it is possible.

Ugh ... Same problem.

It reports "Retro wave device not found." and then a few seconds later "Internal stack overflow, System Halted"

I'm also trying a separate power source:

1weeCee  VCC -> N/C
2weeCee  D- -> RW D-
3weeCee  D+ -> RW D+
4weeCee  GND ->  RW GND+weeCee GND
5
6PSU  -> RW VCC
7PSU GND -> RW GND+weeCee GND

This prevents the weeCee reboot when I plug in the device but it still doesn't work. I don't have any other USB devices or hubs. There might be something with this RetroWave PotatoPi Lite that is just incompatible with the weeCee 🙁

sofakng wrote on 2022-12-21, 18:35:

Ugh ... Same problem. […]
Show full quote

Ugh ... Same problem.

It reports "Retro wave device not found." and then a few seconds later "Internal stack overflow, System Halted"

I'm also trying a separate power source:

Copy code to clipboard

1weeCee  VCC -> N/C
2weeCee  D- -> RW D-
3weeCee  D+ -> RW D+
4weeCee  GND ->  RW GND+weeCee GND
5
6PSU  -> RW VCC
7PSU GND -> RW GND+weeCee GND

This prevents the weeCee reboot when I plug in the device but it still doesn't work. I don't have any other USB devices or hubs. There might be something with this RetroWave PotatoPi Lite that is just incompatible with the weeCee 🙁

Okay, I think there also might be problems on my driver 🤣. Unfortunately I don't have a weeCee to test, nor can I buy it. Actually it looks cute and I'd like to have one but there's nothing listed on my local market.

sofakng wrote on 2022-12-21, 18:35:

Ugh ... Same problem. […]
Show full quote

Ugh ... Same problem.

It reports "Retro wave device not found." and then a few seconds later "Internal stack overflow, System Halted"

I'm also trying a separate power source:

Copy code to clipboard

1weeCee  VCC -> N/C
2weeCee  D- -> RW D-
3weeCee  D+ -> RW D+
4weeCee  GND ->  RW GND+weeCee GND
5
6PSU  -> RW VCC
7PSU GND -> RW GND+weeCee GND

This prevents the weeCee reboot when I plug in the device but it still doesn't work. I don't have any other USB devices or hubs. There might be something with this RetroWave PotatoPi Lite that is just incompatible with the weeCee 🙁

BTW I think it will be much better to make a portable retro palmtop with LCD & mini keyboards, with function like weeCee but looks more like a GPD Win.

Meanwhile I'm gonna ask Sudomaker to check the Lite's vendor id, I use vendor id to detect the device, don't know if the Lite & Express use the same vendor id.

I've checked my device and the VendorID (VID) is 0483 and ProductID (PID) is 5740.

However, I'm still not convinced the problem is with the Vortex86 SOM. When I plug in my KVM it allows me to type a few characters and then displays the exact same message ("Internal stack overflow, System Halted"). The KVM is self-powered so it shouldn't be a power issue I don't think.

I've modified the CONFIG.SYS to increase the STACKS to (9,256) but it doesn't help.

I've talked to Sudomaker and the vendor id is as you said, but I didn't use it, the express and lite have different ids. I'll try fix the id and that will solve the device not found problem,
the other error, internal stack overflow, I think it is a bug of the driver, but I didn't see it in VirtualBox or real hardware, probably need more test.

sofakng wrote on 2022-12-23, 15:39:

I've checked my device and the VendorID (VID) is 0483 and ProductID (PID) is 5740.

However, I'm still not convinced the problem is with the Vortex86 SOM. When I plug in my KVM it allows me to type a few characters and then displays the exact same message ("Internal stack overflow, System Halted"). The KVM is self-powered so it shouldn't be a power issue I don't think.

I've modified the CONFIG.SYS to increase the STACKS to (9,256) but it doesn't help.

I uploaded the new build to the original post. you can try it, the vendor id is fixed, and with other problems fixed.

Any idea if this can work with the MiSTer FPGA platform in the AO486 core? Would be the missing link! The core is otherwise fantastic, but the OPL3 support is lacking and the dev has no interest in finishing it.

Unfortunately it won't work as-is. I've also asked the developers of the ao486 core to add USB or parallel (ie. OPL2LPT/OPL3LPT) support so we can add devices like this but it doesn't look too promising. 🙁

ferropop wrote on 2023-02-26, 17:38:

Any idea if this can work with the MiSTer FPGA platform in the AO486 core? Would be the missing link! The core is otherwise fantastic, but the OPL3 support is lacking and the dev has no interest in finishing it.

This project is experimental and as sofakang said, it's not working on his WeCee machine. I only tested on my 2 laptops (one OHCI and one UHCI) and virtualbox.
I need more machines to test with. I think other platform can be supported after it settles stable enough.

my system has uhci, ohci and ehci usb controllers. i'm trying to get a keyboard working on a usb 2.0 hub connected to the nec usb 2.0 pci card (ehci/ohci), but both usbddos/usbddosp just hang the system immediately on execution. usb keyboard support is disabled in the bios (there is no usb mouse option). is what i'm trying to do even supported by your driver?

i can get this keyboard working with bret johnson's driver when the usb 2.0 hub is connected to the onboard uhci controller, but the keyboard is either undetected or completely unusable under win98se (nusb36e also installed) which is a deal breaker. the keyboard is just as wonky as hell in dos using the bios keyboard support so something is just incompatible between the hub and onboard uhci. amazingly, bret johnson's driver just works in the exact same scenario and i wish it had ehci/ohci support so i could get my keyboard setup working when switching between dos and win98se without having to unplug constantly. (keyboard works fine under windows with hub plugged into ehci/ohci controller.)

Hi, I just tested USBDDOS(P) driver (the latest release Releases 4 1.0 bugfix2 from Github) on my Gigabyte P67 (it has all USB via onboard intel EHCI) and it just hang the system, write no line of message. Only if I call it with /? it prints help info but even if I use some non-existing parameter like /bla it hangs too. I tried separately /hid and /disk parameter. I used with included hdpmi32i and also with newer version from SBEMU package. I tried with JEMM386 and MS EMM386. Under DOS 6.22 and 7.x (from W98) all the same behavior just hang. Sometimes it hangs so hard that even the HW RESET button doesn't work normal way but I have to hold it for more than 10s and then PC will perform a power off/on clycle. So something went very wrong...

Tested both USBDDOS and USBDDOSP on an IBM T42 laptop with the /HID option for USB mouse support. Both detected the mouse but CTMOUSE (tried version 2.0 and 2.1) gives an error: device not found.

Bret E. Johnson's USB drivers in combination with CTMOUSE works on this laptop btw. If you need more information or want me to to test something let me know.

Sorry as this is a bit off topic, but my RetroWave OPL3 Express arrived today. The official VGM Player off github works fine, but are there any alternatives out there? As opposed to having to specify the proper COM port through the CMD every time I want to play a track? I'm on Win10. Also, what does the right button (marked with a gear) even do? 🤣. Thanks!

Also, how do you use this thing in ScummVM? From what I can tell, I have the ini lines setup correctly, but it seems ScummVM just ignores it and uses the default Adlib emulation...