Code not loading properly

[Al3+]

I'm trying to load the built-in default code provided in the WindRiver examples. However, when I deploy it, reboot the cRIO, and try to run it, the Classmate says there's no code. It does detect the stop button and joysticks, so the Classmate doesn't seem to be the problem. I think that the code might not be deploying correctly, although there are no errors when I hit download.

I've installed all the software updates, and set the computer's IP to 10.8.40.6 (team 840), so I don't know what is going wrong...

A few things of note
- the 5V LED on the power distribution block isn't lit. Could this be the problem?
- if I try to connect from the "Remote Systems" tab, I get the following error:

Wed Jan 13 18:47:52 2010
Target name is 10.8.40.2
tgtsvr (VxWorks6x_10.8.40.2@AragonRobotics): Wed Jan 13 18:47:52 2010
WTX Library version: 4.1.1.22
Tgtsvr core version: 4.1.1.17
Wind River Target Server: Win32 version
Connecting to the target agent ...
... switching to WDB4 mode ... ... succeeded !
Loading plug-in for VxWorks... succeeded.
Checking License... OK
VxWorks plugin version: 4.1.1.11
Attaching elf OMF reader for PPC CPU family... succeeded.

Differences for module "vxWorks" segment's address 0x100000:
Offset Target Value Host Value
0x152 0x9c 0x9d
0x153 0x84 0xd0
0x49d 0x0d 0x09
0x49e 0x03 0xaf
Stopping dump. Other errors might exist.

Error: The systems running on the target and loaded into the target server memory are different.
Either wrong core file is selected on the host or text section is corrupted on target side.
Error during target server core initialization
Target Server will exit

[Joe Ross]

Did you re-image the cRiO after installing the LabVIEW update?

[nighterfighter]

Ya know, we had the EXACT same problem with our cRIO....


What fixed it for us was installing all the updates...but...my idea here is your IP Address/Team Number...


Because ours is 1771, it was 10.17.71.2 (for the cRIO)

I thought if you only had a 3 digit number, you put a 0 in first?

So, 10.08.40.6?

That may work, I don't know. :/

PS- Does the classmate show robot connectivity, just not code?

[Al3+]

Yeah, I did re-image the cRIO, but I'll try doing it again tomorrow if I can't think of anything else. And yes, there is robot communication, just no code.

I guess I'll double check the updates. Does the Driver Station update ( http://joule.ni.com/nidu/cds/view/p/lang/en/id/1535 ) need to be installed on the computer with Workbench?

(By the way, the Classmate has LabVIEW and Java preloaded but not Workbench. Is that how it's supposed to be?)

[Bongle]

After we re-imaged our classmate, we had to do a reboot of both classmate and cRio. Make sure that the version string is like c-2010-v19 on your classmate.

Don't forget to recompile your code after updating WindRiver. We struggled for half an hour or so because we forgot to recompile our code to use the LabView mandatory update, so we were uploading v5 code to our v19 cRio.

Another useful thing is to plug a serial cable into the cRio to get its text output. Oftentimes you can take the error text it spits out and search for it on CD to get the solution.

[byteit101]

How are you "deploying"? First>Download? if so, make sure the settings are correct. Go to Window>Preferences and make sure you set the team # and build file in the First Downloader section
If you are using the remote system, you don't need to reboot.

EDIT: make sure you select the OS image when remote system connecting

[Al3+]

So it turns out that the cRIO wasn't up to date after all. Re-imaging from v5 to v19 fixed the problems.

[woodk]

I also had to re-image the cRIO a couple of times before it worked. In the end it was because I had a virus checker running and it caused the re-imaging to timeout.

- Kevin

[RKElectricalman]

I was actually having the same issue, but even after doing all the updates I'm still having this issue!

I'm using Windriver to upload code, and everything seems to deploy properly but doesn't work... Any suggestions?

Any help would be appreciated,.. I always have to spend 3 weeks fixing programming issues for my kids, and I just want them to have the maximum time developing software for once.

-Meezy

[Boydean]

I was actually having the same issue, but even after doing all the updates I'm still having this issue!

I'm using Windriver to upload code, and everything seems to deploy properly but doesn't work... Any suggestions?

Any help would be appreciated,.. I always have to spend 3 weeks fixing programming issues for my kids, and I just want them to have the maximum time developing software for once.

-Meezy

We are also having this same problem, but with labview. I have been working on it for the past two days and I got nothing. Any suggestions would be greatly appreciated.

(the chassis team keeps coming to me saying "well...we want to drive it over the bump some time.")

[ranc]

After updating, did you reimage the CRio to v19 over a wired connection?
I had the same issue, but reimaging did the trick.
Apparently, the error code comes from Windriver and the CRio having different versions.

[BradAMiller]

Originally Posted by RKElectricalman

I was actually having the same issue, but even after doing all the updates I'm still having this issue!

I'm using Windriver to upload code, and everything seems to deploy properly but doesn't work... Any suggestions?

-Meezy

Are you using the FIRST/Downloader or the run/debug options to load code into the robot?

[RKElectricalman]

Yes, we're using the First/Download option in Windriver, and it's not giving me any errors at all... We've done all the updates, and it says it's going through properly, but everytime we hook up the robot to the driver station (last years, and this years) we get a "no code" displayed.

We're using our own development laptop to load the code onto the robot, and we're hooking the ethernet cable straight to the cRIO port one. Is this correct?

Currently, we're installing a fresh copy of all the programs onto another laptop to see if that would help, since the current computer had last years software on it too. It's worth a shot I guess... any suggestions?

-Meezy

*edit* A fresh install did the trick. If you installed the software on a computer that you used last year, completely uninstall it first and then do all the updates + reimaging... works like a charm. Thanks everyone!

[BigJ]

Team 1675 is currently having this same problem (error on trying to connect remote system and "No Robot Code" shown on driver station). We have been trying from a laptop we got this year, so all the installs are fresh.

We have used FTP to confirm that our code is actually getting into the cRIO when we deploy, so that is good.

We have tried deploying/remote system from multiple laptops so it wasn't a problem with our laptop.

We have reimaged using v19 probably 5 or 6 times.

I will try completely uninstalling and reinstalling all the development software tonight. Hopefully it will work then.

2 weeks of cRIO problems makes me a sad panda.

[byteit101]

Are you sure you have all updates?
and more importantly
Are you sure the WR update is installing successfully?

http://first.wpi.edu/FRC/frccupdates.html