AAAUUUGGGHHH!!! RC NOT RUNNING!!!

[Astronouth7303]

What does orange-green-orange-green mean for the program state LED?
When I download my competition code with printf, I get that. When I download without, I get an infinate loop error.
HELP?!?!?

And the default code works

[edit]I'm hitting refresh till i get a response! im frantic! i pnaicing! im not spellchacking! HELP!!!!!!! [/edit]

[Anthony Kesich]

I'm getting the same problem too, only for me, it runs without the autonomous code, it gives the code error thing when i load the default IR code, and does the flashy thingie when i put my autonomous code into it (even if i dont ever call it). So dont think you're the only one.

-Kesich

I'm gonna kill my engineers; lets see if they take 6 weeks to build it next year....

[Tom Bottiglieri]

try updating the firmware.. or if you already did try hitting it with a hammer until it works

[Astronouth7303]

Already updated firmware. And i don't use hammers on electronics

[Astronouth7303]

Say, There is a compile option for large/small space. Would that have to do with this?

[Ryan M.]

Never heard of the error before, but you might want to try the hard reset as detailed in Team Update #7. G2G

[Anthony Kesich]

I've done the hard reset, updated the firmware, everything. This sort of error is just not listed. And i also do not get a RAM dump before you ask.

[Ryan M.]

Originally Posted by Astronouth7303

Say, There is a compile option for large/small space. Would that have to do with this?

If your code (not data, meaning variables) is over 32k (I think. It might be 64k) in compiled size, you have to use the large memory model. Check the size of the .HEX file. If it is greater than 32k or 64k and you don't have any large arrays or stuff like that, try the large model.

Try downloading the default code (sorry if you already tried this). It might be that somehow your code is entering an infinite loop/it takes too long to process something and the master processor shuts it down. We had this happen to us do to a hardware component malfunstioning and our code wasn't built to handle the values it was recieving.

--EDIT--
That second error would be indicated by a flashing orange LED, so I don't think that is it.

[Astronouth7303]

After e-mailing IFI about it, it turns out in Kevin's interupt code, I accidently set timer1 to High Priority . I would post it here, but I'd rather save it until after regional (maybe just Buck-eye, not West MI). I'll test it tonight and tell you about it.

What about the other Problem? If I don't include a #define, printf_lib doesn't get compiled (My design), and I get a green-orange-green-orange I described in the first post. IFI says they can't recreate it. Help?

[HuskieRobotics]

I got the same error and fixed it by following these steps:
1)Press and hold the RESET and PROG buttons at the same time.
2)Release RESET; continue to hold PROG until the "Battery Power" light becomes a solid green
3)Release PROG
4)Hit Reset

I don't know if this will help but it fixed the problem for me so i hope that it does for u too.

[Anthony Kesich]

tried and tried again. still nothing. and i never changed kevin's timer interupt code, but ill check anyways.

[Astronouth7303]

I believe the timer initialization needs to be changed to enable them.

Aparently, that bug fixed both problems (Sort of, with printf() I get garbage)

[InnovationFirst]

Since nobody else has mentioned it on this thread, we would like to remind you that whenever you get a flashing red Program State LED indicating a code error, you can find out more information by using the Dashboard Viewer.

Make sure your OI and RC are linked via tether or radio, connect your PC's serial port to the DASHBOARD port on your OI, make sure the OI/RC jumper is set to "RC", and you will see details about the type of error which caused the flashing red LED at the bottom of the Dashboard Viewer window.

This is how we diagnosed Astronouth's problem, and it may also help you, Kesich.

Regards,
The Firmware Team
Innovation First, Inc.

[Daniel]

Someone mentioned printf working strangely...

I put printf statements through out my program to trace and debug it.

But the program's output has been appearing erratically all of a sudden! That is sometime it just doesn't perform the printf or skips a function call. Has anyone heard of this before? Any solutions?

So much great code, and so little time to debug it!

[bigqueue]

Originally Posted by ToMMan b182

try updating the firmware.. or if you already did try hitting it with a hammer until it works

We tried covering ours with Loctite, and it made all our code problems go away. (Actually, it made all the plastic sides of the robot controller go away, and the code would no longer run.....)

VIOLA...no more nasty code bugs!

-Quentin