Locating Older Cypress FirstTouch hex files

[Phalanx]

I performed a FULL uninstall of ALL of last seasons software. It also uninstalled/removed all the .hex files from my C:\Users\Public\Documents\FRC.

We so happen to have one of the older PSOC-3's and I no longer have the correct .hex file for it.

1) Does anyone know where it can be found or would be willing to email me the older versions if they have them?

2) Shouldn't ALL of the necessary versions been packaged and installed with this years software? Perhaps an update to add them?

[Mark McLeod]

Here are some, but I'm pretty sure I have others floating around in my archives.

[Joe Ross]

You can file a bug about the missing files here: http://firstforge.wpi.edu/sf/tracker/do/listTrackers/projects.wpilib/tracker

[Phalanx]

Here are some, but I'm pretty sure I have others floating around in my archives.

Thanks Mark. It's any/all .V3 files I'm looking for.

IIRC there was a version specific to the original PSOC-3 that was provided when it was initially given to team either in 2009 or pre 2009 I can't remember. There was a slightly different version for the newer PSOC-3 because the hardware changed or something. As I recall.


You can file a bug about the missing files here: http://firstforge.wpi.edu/sf/tracker...wpilib/tracker

As soon as I'm sure I have my information correct, I'll open a tracker.

[Phalanx]

Sorry to bump my old post, but.....

I'm looking for from last season FRC_IO.v3.hex.

According to last seasons "Getting Started with 2012 FRC Control System" on page 39 it states..


In the top left of the tool bar, you’ll see a blue folder icon. Click the folder, browse to Shared or Public Documents/FRC, and select the FRC_IO.v3.hex or FRC_IO.v3.2010.hex (or latest version) file. You must select the correct firmware for the version of the module that you have. The location on the Classmate is Computer»Windows (C:) »Users»Public»Documents»FRC. If you are a rookie, you have a 2012 module. If you are a veteran teams and got your First Touch module in the 2010 or 2011 kit, use that firmware. Selecting the wrong firmware image will result in an error message and will not damage your First Touch module.

So since we certainly weren't a rookie team in 2012, I need the FRC_IO.v3.hex from last year.

@Mark McLeod Do you happen to have that one in your archives?

@Joe Ross, I'll now open a tracker as I have my facts straight.

[Mark McLeod]

Sorry Michael, I haven't been home most of this week because of robotics & work.
I suspect some of the KOP Cypress documentation though. For instance, the first couple of years referenced a firmware version that was never released to the public.

I won't be able to go through my archives until Sunday - today I'm leaving in a few minutes to pick up an aluminum donation, recycling scrap metal, holding an SBPLI workshop, followed by a LI-team idea exchange, finishing with a brainstorming/prototyping session with my own team.

[Phalanx]

Sorry Michael, I haven't been home most of this week because of robotics & work.
I suspect some of the KOP Cypress documentation though. For instance, the first couple of years referenced a firmware version that was never released to the public.

I won't be able to go through my archives until Sunday - today I'm leaving in a few minutes to pick up an aluminum donation, recycling scrap metal, holding an SBPLI workshop, followed by a LI-team idea exchange, finishing with a brainstorming/prototyping session with my own team.

Thanks Mark, No worries. I'm in a similar situation.

[Mark McLeod]

I went back and checked. The yearly documentation has generally incorrectly referenced the firmware files.
These are the Cypress firmware files we received in the Driver Station installations each year:

2010: FRC_IO.v2.hex
2011: FRC_IO.v2.hex
2012: FRC_IO.2009.v3.hex & FRC_IO.2012.v3.hex
2013: FRC_IO.2012.v3.hex

[Phalanx]

Thanks Mark.

I now have the FRC_IO.2009.v3.hex & FRC_IO.2012.v3.hex files.
Which is all I should need.

There's a tracker open for the missing FRC_IO.2009.V3.hex file from this years installer. I suspect an update to the driver station package to include it.