Cypress I/O Module doesn't work with the Driver Station

[amsardesai]

Hey,
When we connect our Cypress I/O Module into the driver station, we get the following error in the Diagnostics tab, hovering over "I/O":

Unable to locate I/O unit over USB.
Check the cable.
Make sure the CyMiniProg3Service has been started in the Service Manager.
Make sure the unit has been programmed.

And on the I/O module itself, when we press the button, a red LED turns on in the module. (I'm assuming that's bad)

We restarted the CyMiniProg3Service, and the same error occured. We even restarted the computer. We programmed the unit using the driver station and another computer (using the hex file provided), but the driver station still doesn't recognize it. We tried connecting it to another driver station from another team, and programming it using the .hex file on their driver station, and the same error occured. We tried using another team's brand new unopened cypress module and programmed it using the base code from our driver station but the same error occured. It's weird because we once got it to work perfectly, but it just stopped working.

Does anyone know a solution to this?

[Greg McKaskle]

Which LED lights up in response to the button? I believe that before the DS communicates to the device, but after you plug it into the PC, you should press the button and see LED 2 light up indicating version 2 of the hex file is on the device.

You may want to use the device manager ( Control Panel and search for it), to see if the USB device shows up when it is plugged in. Note whether you hear the da-ding sound once, twice, repeatedly, when the USB device is recognized. And record the vendor and produce IDs that it declares itself to be. Also, what OS are you using? What driver version do you have for PSOC, etc?

Also, try plugging it in first, then launching the DS, and the other order.

Post what you find and we'll help determine if it is a device failure or a configuration issue or a bug.

Greg McKaskle

[Alan Anderson]

What was the name of the .hex file you used?

When you press the button, the board displays its firmware revision number on the LEDs in binary. The red light on the board when you press the button is the second one from the end, right? It's telling you that the board is running firmware revision 2, and it only does that if it hasn't received any USB communication. Do what the error message says and "Make sure the CyMiniProg3Service has been started in the Service Manager."

[Joe Ross]

What operating system are you running, and are you running the 1/5/11 version of the driver station? I believe there were some improvements from last year.

[Jim.D]

There seems to be a problem getting the driver station installed correctly especially on systems with previous versions of FRC or Creator software installed on them. I would sugest uninstalling all of the Driver station and cypress software and starting with the First version of the Driver station and utilities from the FRC DVD. Then install the driver station updated and new cypress files. If you use Cypress Creator on the computer this will probably break the comumication to the PSOC boards from Creator. I havnt been able to get them to work together.

[mcbean]

we've also got this issue. we have the latest updated labview. the computer we are tryign to run it on did not have a previous version of labview.

the cypress board programs successfully with the v2 hex file. doing a read back appears to have the contents of the v2 hex file (i think it is being loaded properly).

the service is running on the computer, and the usb device is recognized in the device manager.

suggestions?

running winxp 32bit sp3

[Danny Diaz]

We are having this problem too. We successfully used the Cypress board last year, but this year we are having big problems getting the software installed "correctly" - I say this because the "CyMiniProg3Service" doesn't even appear in the Service Manager, so it looks like a software install problem. When we launch any of the PSOC utilities (programmer, creator) we get this same error. This is obviously not acceptable, because the control of our robot is very dependent upon analog input to the Cypress board.

We're actively working on this, and we have multiple approaches being worked on. We'll let you know if any of them pan out.

-Danny

[Danny Diaz]

Okay, we ended up just re-imaging the Classmate and DID NOT install anything that didn't need to be there - after installing all the provided LabVIEW software, and all the updates, we plugged in the Cypress Board, waited a few seconds for the firmware on the Cypress to update, and Presto! it works.

Lesson reiterated: Do not install anything onto the Classmate unless you're specifically told you must. If you're unsure, don't do it. Even if you are sure, don't do it unless you're prepared to reimage.

-Danny

[mcbean]

oh sorry i forgot to respond. we resolved this issue, it turns out it was a conflict of the cypress software with the labview/frc software. someone installed the cypress program, and it must have stolen the control, or replaced the driver with the wrong driver or something.

in any case, the uninstall / reinstall was messy, but if you never install the cypress software in the first place you wont have issues

[RyanN]

Ours doesn't work either... but then again... ours let out some smoke.

Glad you got yours working!