http://www.ifirobotics.com/docs/lega..._2004-1-14.pdf
http://www.ifirobotics.com/docs/rc-r...-6-13-2006.pdf
When we have difficulties, we start at the beginning. Might seem silly, but it helps tell us what is working and what isn't.
1. Using the ifi loader 1.1.0 (
http://www.ifirobotics.com/docs/ifi-loader-v1-1-0.zip) reload the master code and default hex code. Instructions can be found in a pdf file within
master-software-ver11.zip/. Only use the pdf file in this zip file - use the V13 master code as outlined below. This should be done on the 2006/2007 controllers only as I am not sure what will happen - if anything - if this is tried on a 8520 processor in the 2005 controller.
. V13 master code is available in 2007 default code (
http://www.ifirobotics.com/docs/frc-code-2007-8722.zip, the filename is FRC_MASTER_V13.BIN
. FRC_Default.hex is in the same zip file and is the default hex file to use
. Make sure you select the correct COM port via "PortSettings" menu in ifi loader.
. Follow ALL directions in the pdf instructions, including re-verifying the controller type. If the ifi loader already shows "FRC" where expected, do another verification to start anyway. If we can't get controller verification then we know we have either a communication setup issue with our COM port or a bad controller. Its always been a COM port setup issue if we cannot get through controller verification.
** If we get through this cleanly, then we know it isn't a problem with the COM port or controller **
2. Using MPLAB, compile and download unmodified default code [which we keep in a separate directory]. The default code is in the aforementioned zip. Make sure that you select the "Configure -> Select Device" appropriately. For 2006/2007 this is PIC18F8722. For 2005 controller's (that haven't been sent back to be upgraded) this is PIC18F8520.
. build all ("Project->Build All") so that a new .hex file is created without errors
. startup ifi downloader V1.1.0, select the hex file just created and download.
** If there is a problem at this point, it is somewhere in the configuration setup of the MPLAB environment. Typical problem has not been selecting the correct PIC chip device as the target for the build or not having MPLAB properly configured. MPLAB and C18 Microchip suite was provided in KOPs. **
3. Now on to EasyC. Using provided .bin and .hex files in step 1 we've proved that the COM and controller are setup properly and can be communicated to ok. This means there is an EasyC setup issue if we still cannot download from here. Try the above steps and report explicit good/bad results. By then I'll be home and have access to EasyC and will update the steps for EasyC in this post. ;-)
Please be explicit as there has been a lot of advise in this thread.
Q. Were you able to verify the controller under the IFI loader?
Q. Were you able to download the master (bin) code without error?
Q. Were you able to download the default (hex) code without error?
Q. Were you able to build this year's MPLAB default code without error?
Q. Were you able to download this year's MPLAB default code without error?