![]() |
No Robot Code error
For the upcoming fall classic FRC competition, our team did our first power-up check today. The test ran smoothly and everything worked fine. After turning off the robot and then turning it back on, without re-downloading code or changing anything on the robot, the driver station displayed "No Robot Code" and would not run. This program is the exact code that we used last FRC season, and was confirmed to be operational. Because it worked today and then suddenly stopped working without any apparent cause, this is a list of troubleshooting solutions we have tried so far:
Software Tests: -Run full program (which was just working a moment ago) -Run program with complex/potentially breakable functions commented out -Run empty workspace (hello world) -Run code from previous years (2012, 2013) -Check Driver Station Launch Viewer -Re-Install latest FRC WindRiver C++ update -Re-Install latest WPILib update -Re-Install latest National Instruments update Firmware Tests: -Run code on new cRIO -Re-image cRIO with latest image (2014) Hardware Tests: -Unplug/replug ethernet cable -Use new ethernet cable -Run code using wireless connection -Turn robot off then on -Ensure battery is fully charged -Check wiring system for breakages/disconnections -Redo wiring system (just to be sure) ... Any suggestions on what else we can try or what the problem may be? |
Re: No Robot Code error
Quote:
Quote:
|
Re: No Robot Code error
It is probably something silly. These things usually are.
On the DS setup tab do you have the right language selected? (not sure if this really matters) On the DS diagnostic tab, Do you have robot coms? Does it have the Crio version? right side of page. If it has these things then your com path to the crio is probably good. I would start looking for odd settings in your compiler tool chain. |
Re: No Robot Code error
Quote:
|
Re: No Robot Code error
Quote:
|
Re: No Robot Code error
What does netconsole report, both in the working cases and the failed cases?
|
Re: No Robot Code error
Quote:
Warning <Code> 44002 occurred at Ping Results: link-bad, DS radio(.4)-bad, robot radio(.1)-GOOD, cRIO(.2)-GOOD, FMS-bad Driver Station <time>9/20/2014 1:07:03 PM<unique#>9 |
Re: No Robot Code error
Netconsole: http://wpilib.screenstepslive.com/s/3120/m/8851
|
Re: No Robot Code error
Quote:
http://imgur.com/DN9sAGG UPDATE-1: We discovered that WPILib was the problem, and that it was not installed correctly. On a different laptop that WPILib was not installed on yet we correctly installed it. Now the NetConsole is giving us the same errors plus more. From the look of it, it is possible that we are either including our WPILib incorrectly in code or that we are defining our variables wrong. Here is the NetConsole report: http://imgur.com/CcOtNfl UPDATE-2: We fixed the "Relocation does not fit in 24-bit" problem through a different thread by adding in -mlongcall into our build options. Now the only remaining issue is the WPILib. Here is the new NetConsole report: http://imgur.com/w1gRPUs |
Re: No Robot Code error
Here is a link to our code in case there is something we are doing anything incorrectly:
GitHub Main Page Issue on Github |
Re: No Robot Code error
Does it work if you create a brand new project and don't add any extra code?
Commit 08a2bdb seems to have messed with a lot of project settings (along with lots of other things). |
Re: No Robot Code error
Quote:
|
Re: No Robot Code error
Quote:
Reading the autogenerated Makefile, it looks like WPILib isn't being linked in. WPILib is a static library. |
Re: No Robot Code error
Quote:
|
Re: No Robot Code error
Quote:
Conceptually, you want to add WPILib.a to the link command. Not sure the magic key strokes to do that. My guess is that the following diff to your .wrproject did it. Code:
- <listAttribute key="BLD::Info|Libs|PPC32diab"> |
Re: No Robot Code error
Quote:
Also nowadays is there an easy way to compile directly with Linux(specifically Debian or Arch Linux)? Or would I have to go ahead and write up a custom environment too? |
Re: No Robot Code error
Quote:
I'd recommend waiting until the roboRIO arrives to mess with a new environment. The new tools should work from Linux a lot smoother. |
Re: No Robot Code error
Quote:
http://firstforge.wpi.edu/sf/projects/c--11_toochain |
| All times are GMT -5. The time now is 22:40. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi