View Single Post
  #11   Spotlight this post!  
Unread 28-11-2006, 23:30
Shinigami2057 Shinigami2057 is offline
Slackware Is Your New God (Mentor)
AKA: Harry Bock
FRC #1350 (Rambots)
Team Role: Programmer
 
Join Date: Oct 2006
Rookie Year: 2006
Location: Johnston, RI
Posts: 106
Shinigami2057 is just really niceShinigami2057 is just really niceShinigami2057 is just really niceShinigami2057 is just really niceShinigami2057 is just really nice
Re: IFI_Loader protocol?

Hey all, I'm back

I've finished the entire backend interface and have been working on the terminal version on and off for a week or so. So far, everything works just fine - erasing the device, loading programs, dumping user memory, reading configuration memory, etc. all have been tested on the PIC18F8520 controller (2005).

I need some brave souls with access to the 2004 and 2006 controllers to help me out by figuring out the device ID for them using my program, since the program's configuration file relies on device IDs and I only have the 2005 ID (0x0B01). The program will run fine without the correct IDs, it just will assume the memory bounds of the PIC18F8520 which may prevent some programs from loading completely.

Here is the current source tarball: http://lights2dx.net/source/other/frcprog.tar.bz2
Compile it using the make.sh script (I'll get around to a Makefile later). To get the information needed, run it like so:
./frc -i -c --device /dev/ttyS0 (replace ttyS0 with whichever port you actually use)

I've also started building the GUI using glade. Based on this screenshot of the windows the program will use, what do you think so far? http://lights2dx.net/source/other/fr...de_prelim2.png

Thanks everyone again for your help
__________________
One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs.