Quote:
Originally Posted by Alan Anderson
If last year's code executes properly, that's a pretty good indication that you probably have last year's image in the cRIO. What does the Driver Station tell you the cRIO image version is? It had better end in v20, or you'll get "no code" indications when you try to run a program compiled against the most recent WPI library.
|
It's v20 on both the robot's cRIO and our demo board cRIO. Same effect on both. Latest DS software too, as well as latest WindRiver update.
I can run both last year's code (recompiled with this year's WPILib, without many changes) and also this year's 2010 camera demo code.
I copied in modified code from this year's project into the previously working .cpp and .h files from last year - no robot code resulted. I'm going to have to narrow it down slowly.
Quote:
Originally Posted by Abrakadabra
Travis and others -
The best thing you can do is download the NetConsole plugin and install it. (See link under "C/C++ Team Update 4.0" on this page). Watch the console when the cRio reboots. The messages are still a bit cryptic, but you should be able to glean hints about which pieces of code are complaining. You can then either change that code or just comment it out until you can get the rest of your code booting cleanly.
I too have seen a much greater sensitivity to little code issues that didn't seem to matter last year. Not sure exactly what the difference is this year. But I have found that using the NetConsole and the iterative process described above has helped get us through it.
Also, make absolutely sure that you have the latest cRIO firmware image and the latest WPILib update - the latest updates seems to have fixed a lot of the little stuff as well.
HTH. |
Thanks for the suggestions - I'll try to lock this down at the school tomorrow.