IO Board is not recognized

[2010FRC0362]

When we plug in the IO board as instructed, it is not recognized. The message says to check connectivity and battery. Has anyone seen this happen? Any ideas on what else we could do?

[heydowns]

Have you updated the Classmate (or whatever PC you are doing using it with) with the Driver's Station update?

Have you followed the instructions in the Control System manual to load the I/O board with the FIRST-provided firmware image?

Both the manual and the update are linked from http://www.usfirst.org/frccontrolsystem

[walterev]

Our Classmate did not recognize the First Touch board. The device family CY8C38xx was not even available in the list in PSOC Programmer. I loaded FRC-IO.v2.hex onto the First Touch board from my laptop, on which the software had been loaded from the vendor's CD. But neither the Driver's Station nor the PSOC Programmer would connect to the board.

So I installed the upgrade (v 3.10.1.616) from Cypress even though the documentation says to skip it. PSOC programmer now connects using CY8C38xx and all is well.

[walterev]

Sorry, I spoke too soon. We still have an issue with the I/O unit.

error:

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

I have tried a different cable and a different First Touch unit, with the same results.

Will keep trying...

[Joe Hershberger]

If you upgrade the PSoC Programmer software after installing the Driver Station update, the Driver Station will not be able to talk to the First Touch module.

[Robot2377]

We purchased a new PSoC 3 for this year. The programmer complains that the FIRST image was built for a different silicon revision. What's up with that? I have uninstalled and reinstalled all software. The programmer transcript follows:

Program Finished at 9:55:40 AM |
| Programming Terminated
WARNING!---> | Debug mode enabled, this should be turned off from PSoC Creator before production.
ERROR!---> | The hex file was built for silicon revision ES3, but the acquired device is revision **.
| Use PSoC Creator to generate a hex file for the proper device.
Device set to CY8C3866AXI-040 at 9:55:40 AM | 65536 FLASH bytes
Device Family set to CY8C38xx at 9:55:39 AM |
| Automatically Detected Device: CY8C3866AXI-040
Program Requested at 9:55:38 AM |
Successfully Connected to FirstTouch3/000000001A02 at 9:55:26 AM | FirstTouch3 version 1.14
Device set to CY8C3865AXI-056 at 9:55:26 AM | 32768 FLASH bytes
Device Family set to CY8C38xx at 9:55:26 AM |
Opening Port at 9:55:24 AM |
Active HEX file set at 9:55:18 AM | C:\Documents and Settings\All Users\Documents\FRC\FRC_IO.2012.v3.hex
Device set to CY7C60113-PVXC at 9:54:26 AM | 8192 FLASH bytes
Device Family set to 60100 at 9:54:26 AM |
Session Started at 9:54:25 AM | PPCOM Version 7.0

[team4279_IT]

The hex file was built for silicon revision ES3, but the acquired device is revision **.

Anyone find a fix for this yet? I've spent my entire Saturday trying to get this ridiculous board to take and install the file from FRC. Is the board really even necessary? I've seen some posts where people say that they never used theirs.

I've followed all the instructions and installed all the software everything should be 'talking' -- but, no. I have the hex file FRC_IO.2012.v3.hex and the psoc programmer version 3.12.0.827 - after installing the drive station update from the update zip file. I've rebooted, plugged, unplugged, prayed, burned incense, waved chickens, banged bongos, trolled through about six million postings and forums, and anything else I can think of .... to no avail. Is there a secret handshake or password? or will FRC come out with an updated hex file soon?

Please help I lose my mind! oops, too late

[Joe Hershberger]

Can you either transcribe or take a close-up photo of the PSoC on your board?

Did this come in your kit or did you buy it separately? Did you try both the 2012 file and the 2009 file?

Cypress released several incompatible versions of the silcon. It needs to be built for the silicon you have.

The "2012" file is for production silicon. The "2009" file is for ES2 silicon.

[Robot2377]

Joe,

We have two PSoC boards, one was purchased from AndyMark, the other from DigiKey.
We tried both the 2012 and 2009 files. Same error both times.
The chip part number is CY8C3866AXI-040ES2 date code 0949 on the AndyMark board.
The one that came from DigiKey has production silicon CY8C3866AXI-040 date code 1125 (no ES suffix) and the PSoC Programmer reports the same error.
See the PSoC Programmer transcript below.

Robot2377

[Joe Hershberger]

We have two PSoC boards, one was purchased from AndyMark, the other from DigiKey.
We tried both the 2012 and 2009 files. Same error both times.

Are you able to program the old board with the "2009" file? Is this just a problem with the production silicon?

The chip part number is CY8C3866AXI-040ES2 date code 0949 on the AndyMark board.
The one that came from DigiKey has production silicon CY8C3866AXI-040 date code 1125 (no ES suffix) and the PSoC Programmer reports the same error.
See the PSoC Programmer transcript below.

Those look like the part numbers I would expect. The ES2 should work with the "2009" firmware file. The production should work with the "2012" firmware.

Has anyone (other than me) successfully programmed a board with production silicon?

-Joe