Cypress Tutorial?

[Ray Gitchell]

Chris,

Make sure you are using a psoc 3. I am pretty sure we ordered one from Cypress, but were delivered a psoc 5. Apparently similar boards, but different processors. Thus, we are looking into the legality and compatibility of using the psoc 5, 'cause we see the psoc 3 is not unavailable. (at least the last time I checked)

Please post if you find out different, as we are getting a similar error when we try to download the latest code from FIRST for psoc 3.

Thanks, RayG

[Chris Hibner]

Originally Posted by Ray Gitchell

Chris,

Make sure you are using a psoc 3. I am pretty sure we ordered one from Cypress, but were delivered a psoc 5. Apparently similar boards, but different processors. Thus, we are looking into the legality and compatibility of using the psoc 5, 'cause we see the psoc 3 is not unavailable. (at least the last time I checked)

Please post if you find out different, as we are getting a similar error when we try to download the latest code from FIRST for psoc 3.

Thanks, RayG

The board we're using is the one that came in the kit from 2 years ago. Us being a veteran team, we have to reuse an old one. We haven't used any special inputs at the driver's station since FIRST switched to the NI system, so this thing has been packed away and I haven't really given it a second thought. But anyway, it is the one we got in the 2009 kit - it was just packed away and we dug it out a couple days ago.

I got the error just as we were being kicked out of the school, so I didn't have time to write it down, but it was something along the lines of this (heavily paraphrased):

"Programming failed: the XXXX.xxx was created for (something I can't remember) v32, and the (something I can't remember) you are trying to program is v31."

It seems like our board is so old that the new firmware isn't suited for it. Of course, I could be wrong. As I said, we were getting the boot as this was happening and all of that stuff is still at the school so I can't do any real testing. I'm thinking that if I recompile the open-source code with the software that I installed from the CD we had, it will solve the problem. I was hoping that someone else saw this problem and had a solution so I didn't have to spend a lot of time (which I don't really have right now) tracking this down.

[Ray Gitchell]

No, sorry, not the same issue, although our solutions may be similar (rebuild with appropriate toolset).
Perhaps you can install the old CD on a separate computer and load the previous year's .hex file to the board.

I am afraid we may have to port the code to a variant processor, as the psoc5 uses a different compiler and probably different header files. We don't want to tear up previous driver stations, as we use them for promotions and recruiting. ;-(

Thanks for the response, RayG

[jhersh]

Originally Posted by Ray Gitchell

No, sorry, not the same issue, although our solutions may be similar (rebuild with appropriate toolset).
Perhaps you can install the old CD on a separate computer and load the previous year's .hex file to the board.

I am afraid we may have to port the code to a variant processor, as the psoc5 uses a different compiler and probably different header files. We don't want to tear up previous driver stations, as we use them for promotions and recruiting. ;-(

Thanks for the response, RayG

As long as you are using the board that shipped in the kit a year ago, then the firmware should work for you. It has not been recompiled since then (no bugs reported since beta last year). If you can provide the exact error, I may be able to help you figure our what's going wrong. If I had to guess based on what you've told us so far, it would be that you downloaded a newer version of the programmer than the board supports, though I've never actually seen a complaint like that from the programmer software.

-Joe