Error Code

Hi,
Followed the procedure to download the latest master code (version 10) .BIN file into 2005 controller. Completed this successfully.
Downloaded the frc_default code (dated 1_7_2005) and loaded into RC. This produced a code error that read in Dashboard “Invalid Control or Current_Mode byte”.
NOTE: The 2004 frc_default loaded fine with no errors.

A MAP file was generated by IFI Loader as follows.

003A00 FD 0E DB 50 80 0B 2B 10 C0 6E FC 0E DB AE 03 D0
003A10 9E 9C 9D 8C F2 8C C2 80 E5 52 E5 CF DA FF E7 CF
003A20 D9 FF 12 00 50 6F 72 74 31 20 59 20 25 33 64 2C
003A30 20 58 20 25 33 64 2C 20 46 69 72 65 20 25 64 2C
003A40 20 54 6F 70 20 25 64 0A 00 25 73 0A 00 49 46 49
003A50 20 32 30 30 35 20 55 73 65 72 20 50 72 6F 63 65
003A60 73 73 6F 72 20 49 6E 69 74 69 61 6C 69 7A 65 64
003A70 20 2E 2E 2E 00 28 6E 75 6C 6C 29 00 FB 0E E3 CF
003A80 F6 FF FC 0E E3 CF F7 FF FD 0E E3 CF F8 FF FE 0E
003A90 E3 CF E9 FF FF 0E E3 CF EA FF E9 CF F3 FF EA CF
003AA0 F4 FF 09 00 F5 CF EF FF EE 66 FB D7 12 00 FE 0E
003AB0 E3 CF E9 FF FF 0E E3 CF EA FF F3 6A F4 6A EE 52
003AC0 03 E0 F3 4A F4 2A FB D7 12 00 D9 CF E6 FF DA CF
003AD0 E6 FF E1 CF D9 FF E2 CF DA FF E6 52 E6 52 C3 50
003AE0 DF 6E 01 0E C4 CF DB FF DE CF 2B F0 DD CF 2C F0
003AF0 2B C0 F3 FF 2C C0 F4 FF E5 52 E5 52 E5 52 E5 CF
003B00 DA FF E7 CF D9 FF 12 00 1A 6A 19 6A 10 0E E7 6E
003B10 D8 90 1D 36 1E 36 19 36 1A 36 22 50 19 5C 23 50
003B20 1A 58 05 E3 22 50 19 5E 23 50 1A 5A 1D 2A E7 2E
003B30 F0 D7 12 00 45 EC 10 F0 A4 EC 0C F0 01 01 98 91
003B40 01 01 98 A1 07 D0 17 EC 0D F0 01 01 79 AD 02 D0
003B50 9C EC 1B F0 F2 EC 1B F0 F3 D7 12 00 16 EE 00 F0
003B60 26 EE 00 F0 F8 6A 26 9C A6 8E A6 9C A1 EC 16 F0
003B70 FB EC 1B F0 9A EC 1D F0 F9 D7 12 00 FF 0E E3 50
003B80 37 6E 48 0E 01 D0 4C 0E E7 6E E7 2E FE D7 E7 6A
003B90 E7 2E FE D7 37 2E F7 D7 00 00 12 00 FF 0E E3 50
003BA0 E8 4E 12 00 00 00 00 D0 00 D0 00 D0 E8 2E FA D7
003BB0 12 00 C2 90 9D 9C 12 00 C2 82 12 00 00 00 00 00 

I even tried compiling the current source code with sucess using MPLAB 7.00 and compiler 2.40. This new .hex file also resulted in failure.

Although the exact problem was not found, the customer solved his problem with a “Newer PC”. He wrote back: “We repeated the entire process of loading master code, user code into the 2005 RC using a “newer” PC. Everything worked well. In fact, we even have the camera code working correctly…even the java GUI program. No code errors on the RC. Very nice.”
Unfortunately, there are always going to be PC issues that do not get resolved – once a new PC is tried and everything works ……case closed.

We are seeing the same problem as:
http://www.ifirobotics.com/forum/viewtopic.php?t=128
We tried using IFI Loader 1.0.10 to load the new main code, no problems. We downloaded the 2004 FRC_default code, after downloading the program state LED shows that there is an error. We continue to see this problem. We decided to try the old version 1.0.2 and that downloads the new 2005 FRC default code fine. We are running Windows XP.

The customer states: Last night we tried the newly released 2005 default code and it loaded correctly the first time with IFI Loader 1.0.10. We tried several times and it did not fail. One difference is that we tried plugging into a different USB port which resulted in us needing to use COM1 instead of COM5 or COM2 as previously used.

We used the default accelerometer code from frc_accelometer.zip (Kevin Watson’s code), and did the recommended checks at the end of the read me file. The program compiled with no errors, but when it downloaded to the RC, the program state led blinked red and the operator interface showed solid red code error. We are using the Texas Instrument EX3LG20-15A accelerometer. Immediately after the download we get a notepad pop up named error.mcp (see below for a sample)

003A00 64 F1 8C 92 8D 92 8C 90 8D 90 8C 96 8D 96 8C 94
003A10 8D 94 8C 9A 8D 9A 8C 98 8D 98 8C 9E 91 90 8C 9C
003A20 8D 9C 01 01 79 AD 22 D0 01 01 98 A1 1E D0 78 0E
003A30 E6 6E 01 0E E6 6E FD EC 10 F0 E5 52 E5 52 6B C1
003A40 E6 FF 6A C1 E6 FF 69 C1 E6 FF 68 C1 E6 FF CD EC
003A50 19 F0 E5 52 E5 52 E5 52 E5 52 58 0E E6 6E 01 0E
003A60 E6 6E 16 EC 11 F0 E5 52 E5 52 DB D7 12 00 12 00
003A70 D9 CF E6 FF E1 CF D9 FF E5 52 E7 CF D9 FF 12 00
003A80 1E 0E F6 6E 08 0E F7 6E 00 0E F8 6E 01 01 09 00
003A90 F5 50 B6 6F 09 00 F5 50 B7 6F 03 E1 B6 67 01 D0

The termimal window doesn’t even pop up. We are using a fairly new computer running Windows XP Pro and an actual serial port not a usb converter.

The customer was able to fix this problem by completing un-installing / deleting all associated files / programs; MPLAB, IFI Loader, and Default Code. They started from scratch and re-loaded everything, problem solved.

We’ve been hitting consistent ERROR.MCP dumps at the end of the IFI loader download for our 2006 RC. They appear with one to ten lines of a hex dump, see example below.

We seem to have hit a code-size threshold. Adding a few lines to a working routine caused this problem and we can
reliably reproduce the error with these additional lines, and prevent it by commenting-out the lines. If it’s a
hardware failure in our RC it’s a subtle one, as it works fine otherwise.

Per the IFI forum suggestions, we’ve uninstalled and reinstalled the SDK, done a cold install on another
PC, moved code around within various files, and the problem persists. We’re running IDE v. 7.20, have tried both v3.92 and v3.94 linkers, likewise.

We’ve found a workaround by switching from Kevin@JPL’s “bells and whistles” base code to the “streamlined” version, freeing up some code space; however we’re adding code and may hit the threshold again. I have a fileset that reproduces this problem at will and can set it up for anon FTP if you want to try to reproduce it.

One of several variants of the ERROR.MCP hex dump:

008010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01
008020 00 00 00 00 FE FF 00 00 01 00 00 00 00 00 00 01
008030 00 00 00 00 01 00 00 00 00 00 00 01 00 00 00 00
008040 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00
008050 00 01 01 01 00 00 00 00 00 00 FF FF FF FF FF FF

**
There is a problem with the IFI Loader if your code is too large. We will be posting a new IFI Loader to correct the problem.**