cRIO updates

Technical Java
1

Yesterday we updated our cRIO to the newest version, v28. NetBeans, however, did not find any Java updates. I looked on the FIRST Forge website http://firstforge.wpi.edu/sf/frs/do/viewSummary/projects.wpilib/frs], but the latest Java update is still v27, and to make things worse FIRST actually took off the previous cRIO versions (and we didn’t save any copies), so we’re stuck with different versions on my computer and the cRIO. Re-imaging the cRIO [obviously] took off the old code, and now I can’t download any new code.

I looked around and some other threads mentioned v28 for the cRIO, but I couldn’t find any that addressed Java updates. Anywhere I’m not looking? Or maybe there’s a way to tell NetBeans to ignore the fact that I’m working with different versions?

Just in case here’s the error I’m getting when NetBeans tries to deploy code:


...
Network interfaces on host:
    eth1:  address: 167.128.72.32 netmask: 255.255.255.0
    eth0:  address: 10.9.55.100 netmask: 255.255.255.0 <--- on robot's subnet
Connecting FTP @10.9.55.2
~/sunspotfrcsdk/build.xml:95: The following error occurred while executing this line:
~/sunspotfrcsdk/ant/upgrade.xml:40: Expected version FRC_2011_v27.zip; for Name but got FRC_2011_v28.zip;. Go to http://first.wpi.edu/FRC/frcjava.html to get latest software update
BUILD FAILED (total time: 7 seconds)
2

Click the link to upgrade.xml and change v27 to v28 in the Name section.

I just did this this morning :stuck_out_tongue:

3

Well we tried it, and now we get a different error message:


Target IP: 10.9.55.2
Network interfaces on host:
    eth1:  address: 167.128.72.32 netmask: 255.255.255.0
    eth0:  address: 10.9.55.100 netmask: 255.255.255.0 <--- on robot's subnet
Connecting FTP @10.9.55.2
upgrade:
Sending local file image.suite
flashapp:
deploy:
init:
   Waiting for cRIO to reboot (1s)
   Waiting for cRIO to reboot (2s)
   Waiting for cRIO to reboot (3s)
... (it doesn't stop counting)

Eventually the cRio reboots, of course, as our driver station tells us, but it has no code on it.

Also, I know this usually happens if you have your IP configurations wrong somewhere, but I’ve checked all of those many times.

Any other solutions (or anything I’m missing about this one)?

4

That’s a better result than I got after doing it. If you just wait a while then it should reboot and go through a whole bunch of other things. How long did you let it count?

5

I let it count well past 100. The driver station sees it reboot, but it says there is no code on the robot.

6

Huh, that’s odd. So the driver station says there is communication but no robot code?

7

Yes. Driver station has communication with robot, sees it reboot, but sees no code on it. The computer sees the robot and tries to deploy, but never sees the robot reboot.

UPDATE:
I restarted the cRio manually. Now the computer sees it restart, but there’s still no code. Here’s the output:


... (the normal stuff)
[cRIO] 
[cRIO] Welcome to LabVIEW Real-Time 8.6.1f3
[cRIO] 
[cRIO] [Squawk VM] Version: 2011 FRC, Feb  2 2011, 13:26:47
[cRIO] Uncaught exception in Thread.run():
[cRIO]     on thread edu.wpi.first.wpilibj.templates.RobotTemplate - main
[cRIO] java.lang.IllegalArgumentException: MIDlet class specified, edu.wpi.first.wpilibj.templates.RobotTemplate, was not found
[cRIO]     at com.sun.squawk.imp.MIDletMainWrapper.main(94)
[cRIO]     in virtual method #95 of com.sun.squawk.Klass(bci=25)
[cRIO]     at com.sun.squawk.Isolate.run(1506)
[cRIO]     at java.lang.Thread.run(231)
[cRIO]     in virtual method #47 of com.sun.squawk.VMThread(bci=42)
[cRIO]     in static method #3 of com.sun.squawk.VM(bci=6)
[cRIO] 
[cRIO] 
[cRIO] --------------------------------------------------------------------
[cRIO] GCs: 1 full, 0 partial
[cRIO] ** VM stopped: exit code = 1 ** 
[cRIO] task 0x21dda18 (SquawkRobotTask) deleted: errno=0 (0) status=1 (0x1)

This is with v27 on my computer, v28 on the cRio, telling upgrade.xml to look for 28 instead of 27.

8

Reflash the crio with v27, and it should work until you can update your computer to v28

9

Okay we got it figured out. We did change upgrade.xml to look for v28 instead of v27. The problem after that was just something wrong with the project. Making a new project fixed it. (I remember this happened a lot when we used WindRiver, but this is the first time it happened with NetBeans, so the thought never occurred to me.)