URGENT - Code Violation

[CPress]

Hello,

I was trying to program some things for this years robot with 2005 RC. We first originally loaded the default 2007 code onto it and it worked fine. Then we tinkered with that code and it worked after recompiling it and put it on the RC. Now, I am on a different computer using the orange VEX USB->Serial converter cable (my laptop doesn't have a serial port) and I tried to load some code I was working on and the build worked, no errors in mplab, but when I put it on the RC it says "Code Error" on the Operators interface and "Code Violation" on the RC itself. I tried to load the Default 2007 code back on to it and got the same thing. Ive been looking for about 2 hrs now and still haven't found anything at all. I'm hoping you guys can help me out.

- Matt (Team 754)

[Mike Betts]

Remember that the 2005 RC had a different processor than the 2006/2007 RCs.

[Jeff 801]

also the numbers after like the pwm are in a different order

[Alan Anderson]

Mike is right. You can't run a program compiled for the 2006 or 2007 RC on a 2004 or 2005 RC. See the "Using_a_2005_FRC.txt" file that is included with the 2007 default code for instructions on recompiling it to work.

[kitscuzz]

And beyond the different proccesor, there's also less memory. There is an option in all the 2006-2007 code that enables the full usage of the memory which will quickly cause errors if not disabled in the project options.

[taberski]

I ran into the same problem today!

We're using a 2005 RC controller for some testing in an attempt to divide and conquer. I modified Kevin Watson's (frc_camera_21) to run on the 2005 RC to do some testing (following the supplied instructions for the device, linker and library) and has a successful day (this session was at home using a desktop computer with a real serial port). I demonstrated my progress to the team utilizing a laptop with a serial port.

Another member of the software team need to use this controller to test a separate piece of the software and started with the same code base. He kept getting the same errors as described above. In his case, he was using a laptop with a USB-to-Serial adapter (which he's been using for a while).

Anyway, I backed the debug process all the way down to downloading the hex file that I had successfully run earlier in the day with the same errors! By this point our work session was over until morning, so I have no platform to work with until the morning :-(

Any insight into what might be happening or what I should look for is greatly appreciated. It's as if we broke something!

Thank you,

Kevin Taberski