Software Support > PowerMAME
USB problem isolated!!
2600:
--- Quote from: RandyT on March 22, 2006, 11:34:39 am ---
Please feel free to give Mike any information about the device he needs. He's a trusted party :)
--- End quote ---
Pics sent. Should of CC'ed Randy, but don't have time to look up his email right now.
The two scenarios are using a PC with an 865g. In one case, the LEDWiz is directly connected. In the Second, a USB 2 hub with an NEC IC is being used.
--- Quote ---As for the device not being fast enough to pick up the data, this doesn't really sound correct to me. If this were the case, then simply adding gross delays between reports should have corrected the problem. It was my understanding that it didn't. It was also my understanding that there were spec limits on how fast a hub or controller would send reports to a device that has identified itself as a "low-speed" device.
Have I missed something?
--- End quote ---
An OHCI controller can group multiple Control Transfers together in a frame. I'm not clear on the size of the gross delays. If large enough, your right it would have to work. Speed was only one scenario. It could also be HW implementation, which I would doubt, or something simple like not expecting multiple packets. On the outside looking in so you would know more about your device.
--- Quote ---BTW, the LED-Wiz is doing a *lot* of stuff. Providing 48 levels of PWM and HW modulation FX on 32 individual outputs without flicker takes a lot of work. But the data coming in should be serviced in plenty of time. We are only talking 8-bytes of data per packet and the receiver is interrupt driven.
--- End quote ---
I was thinking the other day about how much it is doing. It is a lot.
Also, remember that it is 16 byte's. 8 byte's for the setup packet. 8 byte's for the data.
--- Quote ---And whether this is an Nvidia thing or not, I can't say. But the only other chipset that has reported problems so far is an outdated Intel chipset. The later chipset from Intel works fine. So whatever Intel was doing that caused problems on the early one was changed in a newer version. Coincidence? Maybe.
Thanks, and please keep me updated.
RandyT
--- End quote ---
Hadn't heard of the other Intel Chipset being affected. Which one? I think I may be able to test another scenario tonight. We'll see if I can get to it.
MikeQ:
--- Quote from: 2600 on March 22, 2006, 01:45:29 pm ---Hadn't heard of the other Intel Chipset being affected. Which one? I think I may be able to test another scenario tonight. We'll see if I can get to it.
--- End quote ---
The Intel system was an 82801 AB or EB. Can't remeber which now. I tried it on both the AB and EB and it works on one fails the other. I think it failed on the AB but can't say for sure. Also, this doesn't fail on either system when the LEDWiz is plugged directly into the system. It only fails when the HUB is connected and the LEDWiz is connected to the hub. This hub also gives my ASUS motherboard fits. The computer won't boot with the hub plugged in. I have to boot the system and then plug the hub in. The hub very well could have a problem.
However, the same workaround that fixed the Nvidia problem fixed the hub problem on the 82801.
I don't know off hand what chipsets these systems are running.
RandyT:
--- Quote from: 2600 on March 22, 2006, 01:45:29 pm ---An OHCI controller can group multiple Control Transfers together in a frame. I'm not clear on the size of the gross delays. If large enough, your right it would have to work. Speed was only one scenario. It could also be HW implementation, which I would doubt, or something simple like not expecting multiple packets. On the outside looking in so you would know more about your device.
--- End quote ---
I believe a delay of roughly 1000ms (1 second) between the reports was used and the problem still existed. The SIE is a very slightly altered reference design from a very respected and oft utilized USB chip producer. That doesn't seem like it would be the culprit either (but I'm not ruling anything out.)
--- Quote ---I was thinking the other day about how much it is doing. It is a lot.
Also, remember that it is 16 byte's. 8 byte's for the setup packet. 8 byte's for the data.
--- End quote ---
I understand. 8 bytes per packet, but there seem to be 2 packets coming in rapid succession. What I have read is that when dealing with a "low-speed" device, there should not be more than 1 packet transmitted by or intended to be received by the device but once every 10ms. Is this information in error? Obviously, the setup and data packets are being sent much closer together. The question is: why is it only a couple of chipsets that appear to be doing this?
Thanks for the help, BTW!
RandyT
RandyT:
--- Quote from: MikeQ on March 22, 2006, 02:23:30 pm ---
--- Quote from: 2600 on March 22, 2006, 01:45:29 pm ---Hadn't heard of the other Intel Chipset being affected. Which one? I think I may be able to test another scenario tonight. We'll see if I can get to it.
--- End quote ---
The Intel system was an 82801 AB or EB. Can't remeber which now. I tried it on both the AB and EB and it works on one fails the other. I think it failed on the AB but can't say for sure. Also, this doesn't fail on either system when the LEDWiz is plugged directly into the system. It only fails when the HUB is connected and the LEDWiz is connected to the hub. This hub also gives my ASUS motherboard fits. The computer won't boot with the hub plugged in. I have to boot the system and then plug the hub in. The hub very well could have a problem.
--- End quote ---
FWIW, I have a 98SE system here with the Intel AB/EB (the later model) and it works just fine, even with a hub.
RandyT
Howard_Casto:
--- Quote from: southpaw13 on March 21, 2006, 07:55:09 am ---Yes, that is the driver that is giving everyone the problems. FWIW, I decided to use NVIDIA chipsets because my cabs double as a Daphne emulator also. Daphne and ATI don't mix well together. I have not run into any major problems with NVIDIA and Mame...
Maybe I should switch to Via chipsets with a NVIDIA video card?
Southpaw
--- End quote ---
Sorry to respond to this so late but.
This is a complete and utter falsehood.
Ati cards at one point (not anymore) had an issue with hwaccel in daphne. The thing nobody mentioned though (because the daphne team, unfortuantely are nvidia fanboys) is that ati's 2d support is so much better than the average geforce card that daphne STILL performed better with an ati card with acceleration turned off than a similar nvidia card with it turned on. How do I know? Cause I tested it of course. :)
To answer your second quesiton.. no you should switch to via chipsets with an ATI video card. Ati cards have better tv out and arguably use the mame filters better. So you'll get a better picture regardless of the monitor you choose to use. While daphne used to have issues with ati cards it doesn't anymore. Even if it did that's only 20 games and it's not a emulator crippling issue, vs the 5000 in mame that will look better on an ati. Not to mention the fact that the nvidia drivers still totally screw up visual pinball, making the tables unplayble so that's 500+ games with issues on the nvidia side vs the 20 in daphne that are now (and always were) a non-issue.
Again... we haven't preached the benefits of ati and the evils of nvidia for the past 9 YEARS just for our health. Nvidia sucks, only buy ATI!!!
(Howard_Casto awaits all the free stuff ati owes him for that winning endorsment.)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version