View Single Post
  #8   Spotlight this post!  
Unread 01-12-2004, 21:32
Ian W. Ian W. is offline
College? What?
no team (Gompei and the Herd)
Team Role: College Student
 
Join Date: Jan 2002
Rookie Year: 2002
Location: Worcester, MA | Smithtown, NY
Posts: 1,464
Ian W. is a name known to allIan W. is a name known to allIan W. is a name known to allIan W. is a name known to allIan W. is a name known to allIan W. is a name known to all
Send a message via AIM to Ian W.
Re: Recovering code from the RC

Quote:
Originally Posted by Rickertsen2
I don't think this will help you, but i'm posting it anyway. I know a way to do it, but it requires voiding your warranty as well as a PIC programmer and a bit of know how. If you are willing to be daring and have access to a PIC programmer, then crack open the RC and you will see some pinheaders. One will be labeled somethign like "user" (i don't remember the exact text). This is an ICSP port for the user processor. I'm not sure the order of the pins but it wouldn't be that hard to figure out with an ohmeter and the ICSP spec from the microchip website.
Before you go and crack it open, give IFI a call, perhaps there's a way to interface the PIC directly with something on the outside of the RC. Don't tell them you're cracking it open though, if they don't answer .

As for retrieving the code in general, you're probably better off just rewriting it, and using the experience two ways. One, teach new programmers how it all works (because it is quite a bit different from writing a generic win32 program), and two, figure out how to use some sort of more robust storage solution, be it backing up your code in several places or something like CVS.
__________________
AIM --> Woloi
Email --> ian@woloschin.com