A Problem with Java Deployment

I am trying to deploy the default Java program to our cRIO.

Some details:

  • Our cRIO has the latest image (2012 v43), and it is configured to accept Java programs.
  • I tether my laptop directly to the cRIO via the provided Ethernet crossover cable.
  • I have a fresh install of Netbeans, and the FRC plugins are fully configured.
  • My main project is the unmodified BuiltInDefaultCode, and I deploy via “Run Main Project.”

The problem is that the deployment simply hangs, with the following output:


init:
init:
clean:
Created dir: C:\Users\liujc\Documents\NetBeansProjects\DefaultCode\build
Compiling 1 source file to C:\Users\liujc\Documents\NetBeansProjects\DefaultCode\build
Note: C:\Users\liujc\Documents\NetBeansProjects\DefaultCode\src\edu\wpi\first\wpilibj\defaultCode\DefaultRobot.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
compile:
Created dir: C:\Users\liujc\Documents\NetBeansProjects\DefaultCode\j2meclasses
preverify:
Created dir: C:\Users\liujc\Documents\NetBeansProjects\DefaultCode\suite
Building jar: C:\Users\liujc\Documents\NetBeansProjects\DefaultCode\suite\BuiltInDefaultCode_1.0.0.jar
jar-app:
CompilerOracle: exclude com/sun/squawk/Method.getParameterTypes
CompilerOracle: exclude com/sun/squawk/SymbolParser.getSignatureTypeAt
CompilerOracle: exclude com/sun/squawk/SymbolParser.stripMethods
[translating suite image [closed: false, parent: squawk] ...]
### Excluding compile: com.sun.squawk.Method::getParameterTypes
### Excluding compile: com.sun.squawk.SymbolParser::getSignatureTypeAt
[Including resource: META-INF/MANIFEST.MF]
Romizer processed 100 classes and generated 4 files.
Expanding: C:\Users\liujc\Documents\NetBeansProjects\DefaultCode\suite\BuiltInDefaultCode_1.0.0.jar into C:\Users\liujc\Documents\NetBeansProjects\DefaultCode\suite
Moving 1 file to C:\Users\liujc\Documents\NetBeansProjects\DefaultCode\suite
Moving 1 file to C:\Users\liujc\Documents\NetBeansProjects\DefaultCode\suite
Moving 1 file to C:\Users\liujc\Documents\NetBeansProjects\DefaultCode\suite
Deleting: C:\Users\liujc\Documents\NetBeansProjects\DefaultCode\image.suite.api
Host OS: Windows 7 6.1, 6.1
Host JVM: Java HotSpot(TM) Client VM 22.0-b10
Target IP: 10.32.74.2
Network interfaces on host:
    Marvell Yukon 88E8058 PCI-E Gigabit Ethernet Controller:  address: 10.32.74.6 netmask: 255.0.0.0 <--- on robot's subnet
Connecting FTP @10.32.74.2
upgrade:
Sending local file image.suite
flashapp:
deploy:
init:
[cRIO] [OTA Server] ********* REBOOTING cRIO *********
[cRIO] 
   Waiting for cRIO to reboot (1s)
   Waiting for cRIO to reboot (2s)
   Waiting for cRIO to reboot (3s)
   Waiting for cRIO to reboot (4s)
   Waiting for cRIO to reboot (5s)
   Waiting for cRIO to reboot (6s)
   Waiting for cRIO to reboot (7s)
   Waiting for cRIO to reboot (8s)
   Waiting for cRIO to reboot (9s)
   Waiting for cRIO to reboot (10s)
[cRIO] 
[cRIO] -> * Loading debug.o: debug
[cRIO] Debugging is up, target server mounted at /tsfs
[cRIO] 
[cRIO] 
[cRIO]                 VxWorks
[cRIO] 
[cRIO] Copyright 1984-2006  Wind River Systems, Inc.
[cRIO] 
[cRIO]              CPU: MPC5200 -- Wind River Lite5200 BSP.
[cRIO]     Runtime Name: VxWorks
[cRIO]  Runtime Version: 6.3
[cRIO]      BSP version: 2.0/10
[cRIO]          Created: May 27 2011, 11:02:24
[cRIO] ED&R Policy Mode: Deployed
[cRIO]    WDB Comm Type: WDB_COMM_END
[cRIO]              WDB: Ready.
[cRIO] 
[cRIO] * Loading nisysrpc.out: nisysrpc
[cRIO] * Loading NiRioRpc.out: NiRioRpc
[cRIO] * Loading nivissvc.out: nivissvc
[cRIO] * Loading nivision.out: nivision
[cRIO] NI-RIO Server 4.0.0b8 started successfully.
[cRIO] task 0xe2f9d8 (NiRioRpc) deleted: errno=0 (0) status=0 (0)
[cRIO] * Loading visa32.out: visa32
[cRIO] * Loading niserial.out: niserial
[cRIO] * Loading NiFpgaLv.out: NiFpgaLv
[cRIO] * Loading FRC_FPGA.out: FRC_FPGA
[cRIO] * Loading FRC_NetworkCommunication.out: FRC_NetworkCommunication
[cRIO] FRC_NetworkCommunication was compiled from SVN revision 2923
[cRIO] FPGA Hardware GUID: 0xA14C11BDE4BB64AEF6A86FC52A294CD9
[cRIO] FPGA Software GUID: 0xA14C11BDE4BB64AEF6A86FC52A294CD9
[cRIO] FPGA Hardware Version: 2012
[cRIO] FPGA Software Version: 2012
[cRIO] FPGA Hardware Revision: 1.6.4
[cRIO] FPGA Software Revision: 1.6.4
[cRIO] * Loading FRC_JavaVM.out: FRC_JavaVM
[cRIO] 
[cRIO] 
[cRIO] [OTA Server] Version: 2012 FRC, Jan  5 2012, 17:20:48
[cRIO] 
[cRIO] 
[cRIO] Welcome to LabVIEW Real-Time 11.0rc14
[cRIO] task 0xddbe60 (sysapi-rpc) deleted: errno=0 (0) status=0 (0)
[cRIO] 
[cRIO] [Squawk VM] Version: 2011 FRC, Nov  5 2011, 14:34:13
[cRIO] FPGA Hardware GUID: 0xa14c11bde4bb64aef6a86fc52a294cd9
[cRIO] FPGA Software GUID: 0xa14c11bde4bb64aef6a86fc52a294cd9
[cRIO] BuiltinDefaultCode Constructor Started
[cRIO] 
[cRIO] DIO LoopTiming: 260, expecting: 261
[cRIO] BuiltinDefaultCode Constructor Completed
[cRIO] 
[cRIO] RobotInit() completed.
[cRIO] 
[cRIO] Default IterativeRobot.disabledContinuous() method... Overload me!

Specifically, after this particular line:


[cRIO] Default IterativeRobot.disabledContinuous() method... Overload me!

After doing some googling, I found that a similar issue was resolved here. In that case, the issue was resolved by “enabling the robot.”

So I have two questions. First, how would I go about “enabling the robot”? And second, what are other possible solutions to this problem (as the root cause of their problem isn’t necessarily the same as mine)?

I really want to use the new infrastructure in wpilibj, so thanks a lot!


[cRIO] Default IterativeRobot.disabledContinuous() method... Overload me!

The disabledContinuous() line is just saying that it’s running the default method. Write your own to do whatever you want. But not required at this time.

To enable your robot, you click enable in the Driver Station, and that should run tele-opContinous() or however that is spelled.

Yeah, I understood that that’s what the line meant; I was merely using it as a reference point to pose my question.

And oh ok, I thought the “enable” they referred to was more complicated than simply that. So I guess there was no problem with deployment after all? It’s just waiting for the driver station to send commands?

Thanks!

That is correct
One thing I may suggest is to locate the driver station executable in Program Files and make a shortcut to it on the desktop of you developer account. Prevents having to constantly switch between accounts