ΣSigmaStudio Ask AI Русский Log in

SigmaStudio under Win 7 X64

SigmaDSP & SigmaStudio rszemeti Apr 20, 2013 00:00 3 replies Original on forum ↗
Subscribe
rszemeti Question
Apr 20, 2013 00:00

Hi,

Running SS 3.8 under Win XP with USBi drivers, it all works as expected.

On my laptop, running Win 7 X64, with the x64 CyUSB driver installed from the AnalogDevices directory, it doesnt.

When I plug the device in, I first get the USBi icon on the hardware screen changing state to light orange, and the device appears functional. I can turn the device power on/off for example.

When I hit F7, it says "active downloaded" with the usual green bar .. then a little while later, "comms failed" .. but the bar stays green. I suspect the "active downloaded" as the device never achieves a functional signal path.

The schematic is one that was developed without problem on my desktop, under XP, so no issues there.

Did I miss something obvious?

Audio Signal Processors

usbi

sigmastudio

SigmaDSP Audio Processors

adau1701

KJBob Reply
Apr 20, 2013 00:00

Hi rszemeti,

Since your Win 7 x64 laptop is relatively new, it likely is equipped with USB 3.0 ports. The USBi doesn't work well with these. My laptop has one USB 2.0 port and two 3.0 ports -- my USBi does fine with the 2.0 port, but gives the exact symptom you described with a 3.0 port. Hopefully your machine has at least one 2.0 port -- on my Dell laptop, the 2.0 port is on its left side -- if in doubt, check your manual.

Best regards,

Bob

rszemeti Reply
Apr 20, 2013 00:00

Hi Bob,

Thanks, that solved it. It is indeed a Dell Inspiron Core I7, and checking the manual, it turns out the one on the left is ia a USB2.0 socket (black plastic core) and the others are USB 3.0 (blue core) .. I hadn't noticed they were different until you mentioned it.

All working now, its not often software fails on me because my laptop is too fast!

Thanks for the simpe solution!

ADIApproved Reply
Apr 22, 2013 00:00

Thanks Bob. A brief look at the Cypress forum leads me to believe that this might be a driver issue with USB 3.0. We're investigating it. For now, I would recommend all users to plug the USBi into USB 2.0 ports if possible.