can't Download code to cRIO
 

We can Debug our code, it runs and there are no error messages in the Task console window. Now when we start FIRST...Download the status window opens and it is static, saying "Downloading to robot..." with a red dot on the right side. No progress bar or anything, just stuck. The ethernet lights show no activity. The downloading PC has IP 10.xx.yy.6.

The FIRST Downloader Preferences have been set to our team number and the .out file is the correct one. Windriver has the update, Labview has it's update although possibly those have nothing to do with this problem. The cRIO has C++ image V19 and that is confirmed by Driver Station ... Diagnostic.

Any ideas?

Re: can't Download code to cRIO
 

The FIRST downloader in Windriver is specifically for downloading the code permanently to the cRIO. The run dialog however, will allow you to send code to the cRIO temporarily which will allow you to debug and test while developing.

Assuming you have set the IPs of the cRIO and the Gaming Adapter correctly, you need to setup a Kernel Task in the Run Dialog. You can do this by clicking on the arrow next to the green button with a triangle on it, and then click 'open run dialog'.

To the left, you should see a tree diagram with the 'kernel task' option in it. Right click on this and make a new kernel task. In the main tab in the box next to 'entry point' you need to put 'FRC_UserProgram_StartupLibraryInit'. Next, switch to the projects to build tab and then add your current C++ project to this box. Switch to the downloads tab and make sure the same project is selected.

Once you have done this, you can click 'apply' which will save the settings and close the dialog.

Now, in the bottom left corner of the Windriver program, you will see the 'remote systems' tab, right click in there and click on 'new' and the 'connection'. In the dialog that pops up, go into the VxWorks 6.x tree and use the Wind River VxWorks 6.x Target Server Configuration that is available there.

Click next. Make sure the target name/ip address is set to your cRIO's address. The input box next to 'File' needs to be set to the VxWorks file located in C:\windriver\WPILib\ Once you have done that, click finish. You can then right click on that connection and assuming your robot is all connected and you can ping it, you can right click the connect button.

After it connects, you will see the tasks running on your cRIO. To upload code to the robot, all you need to do is go up to the green button that you went to before and select the run configuration you setup before and it should send the code to the robot.

You can reset the code by resetting (the power) or rebooting the robot remotely.

Hope this helped.

Regards, team 3257. :)

Re: can't Download code to cRIO
 

And it works?

can you open a browser and go to ftp://10.xx.yy.2/ and see the cRIO
if not, make sure you are wired up to the cRIO correctly (and try direct crossover)
is the project Built

Re: can't Download code to cRIO
 

Yes. We've loaded code with the Windriver Run button and driven our mecanum chassis robot over field humps. Today we got the camera sending images to the dashboard after formatting and reimaging the cRIO. Still won't Download though. The Download window just sits there, no progress. The Undeploy option says there is no user code loaded, like we didn't know that :)

Re: can't Download code to cRIO
 

Make sure the networking is set up correctly.
however, you can always get the built file, and FTP it to the crio manually, 10.xx.yy.2/system/startup/FRC_UserProgram.out (or something like it)
EDIT: (hopefully stupid question) you are attempting downloading when the cRIO is plugged in, turned on, and the DS (which is connected to the programming laptop) says communication, no code, Correct?

Re: can't Download code to cRIO
 

That's a good idea to try FTP. If the FIRST Downloader uses FTP to transfer data, maybe the root cause of the problem is with FTP. We'll try it and report back.

Re: can't Download code to cRIO
 

Our control system is in pieces, getting installed on the chassis. We did ftp into the cRIO and were able to copy over our .out file and rename it, power cycled the cRIO, it didn't run our code and the RSL had a somewhat random blinking pattern. Further debugging will have to wait until probably Saturday.

Re: can't Download code to cRIO
 

are you positive you have v19 and Windriver/WPILib update 4?
also, Right click the project, and rebuild

Re: can't Download code to cRIO
 

We are seeing this same random blinking pattern on the DS. Does this indicate anything specifically is wrong?

Re: can't Download code to cRIO
 

We haven't run any code for a week or so while the hardware is getting assembled.

Last night I reformatted the cRIO and installed v19 image for C++ for maybe the 6th time. Started Windriver, checked the FIRST preferences for the correct .out file and team number, Undeployed the code and it gave a warning that there was no code to undeploy, then rebuilt and Downloaded our code. The Download window opens, red dot on the right side, no progress bar, nothing downloads. Ftp into the cRIO and the Startup directory, no code got copied over. Exit Windriver. Rename and copy over the .out file to the cRIO using ftp. Power cycle the cRIO and the Driver Station says there is no robot code. Ugh. I'm ready to throw the cRIO into the river.

Re: can't Download code to cRIO
 

We had a similar experience last night after I added the 2/8/2010 c++ update to our 2 PC's. "no code to undeploy" messages and "no robot code" upon cRio power reset and what was a ""too fast" progress bar on the download. After doing the insanity thing and repeating over and over, my cohort, Bryce re-installed the update on one of our HP's. He pulled a new "2010 vision code " example project...then closed and re-started WindRiver. Built, set the correct .out, and downloaded. That finally worked.... I don't blame the cRio. There is something very funky about WindRiver/Eclipse this year. We keep getting Windows "out-of-memory" errors and need to close and re-start at least once a meeting.......go figure.

Eric

Re: can't Download code to cRIO
 

Try to take one of the example projects and download it. Sometimes there will be a bug in the code that may prevent it from downloading/running correctly. If you can't deploy a default project, then you know for sure that it's not a problem with the code and that it is a problem with something in the downloading process.
Also, make sure you have the latest updates for everything you're using. Apparently there was an update recently (I think for the DS) that you had to install twice, because it didn't work the first time. Make sure everything is installed and updated.
Good luck!

Re: can't Download code to cRIO
 

We finally deployed code yesterday for the first time in 2010!

It was an epic. We tried to reimage the cRIO from our programming laptop and it would fail every time. Sometimes the Imaging app couldn't locate a cRIO, other times it would error out during formatting, sometimes it would error out later in the imaging process. For laughs we booted up our 2009 laptop and loaded the 2009 v7 image, and that worked! Then went back to the 2010 laptop and started the DriverStation, it said there was robot code. Strange stuff. Tried to Image to 2010 v19, same errors as before. Hmmm.

We loaded all the 2010 code onto the Classmate and tried to Image from that. It looked promising but stopped short again. Then we set the cRIO to Safe mode and reformatted, then went out of Safe mode and the Image finally loaded. Then we ran Windriver on the Classmate and the code Downloaded and the robot at last can be power cycled and run the code.

The other laptop with 2010 code still can't Download robot code, so that will have to have all it's 2010 code uninstalled and reinstalled. What a mess, but at least we can compete now.

Re: can't Download code to cRIO
 

I helped a team yesterday having problems getting their "Robot Code" light to turn green. The FRC cRIO Imaging Tool on their laptop wouldn't find the cRIO. After trying everything I could think of, I used our team's laptop instead, and things started working.

I think it turned out at the end of the day that there was a 1394 network defined on their laptop, and disabling that in addition to the wireless network fixed the problem.