24-01-2006, 23:27
|
 |
 |
Electrical Engineer / Computer Geek
AKA: Eldarion Telcontar
no team (Teamless Orphan)
Team Role: Alumni
|
|
Join Date: Nov 2005
Rookie Year: 2005
Location: Númenor
Posts: 558
|
|
|
Re: The chasing-lights RC error
Quote:
|
Originally Posted by steven114
We had this trouble occasionally when we had a flaky serial cable. The solution we used is twofold:
First, you have to instruct the master microprocessor not to boot the user one. Hold both the RESET and PROG buttons on the RC for about five seconds. Release the RESET button, wait another five seconds, and then release the PROG button. The Battery light should go green, the Program light should go orange, and the rest should stay unlit.
Then, use a known good serial cable (make sure it doesn't have excessive length! Use only one 6' cable if possible) to download your code. Should fix it right away.
|
So the error is caused by random garbage going into the program port?
I was able to fix it by just pressing Reset on the RC; I was more curious what the actual error meant. 
__________________
CMUCam not working? Tracks sporadically? Try this instead: http://www.falconir.com!
PM me for more information if you are interested (it's open source!).
Want the FIRST Email blasts? See here: http://www.chiefdelphi.com/forums/sh...ad.php?t=50809
"The harder the conflict, the more glorious the triumph. What we obtain too cheaply, we esteem too lightly; it is dearness only that gives everything its value."
-- Thomas Paine
If it's falling apart it's a mechanical problem. If it's spewing smoke it's a electrical problem.
If it's rampaging around destroying things it's a programming problem.
"All technology is run on 'Magic Smoke' contained within the device. As everyone knows, whenever the magic smoke is released, the device ceases to function."
-- Anonymous
I currently speak: English, some German, Verilog, x86 and 8051 Assembler, C, C++, VB, VB.NET, ASP, PHP, HTML, UNIX and SQL 
|