cRIO doesn't reboot during imaging

[ubeatlenine]

When trying to reimage my team's cRIO with the latest java image (v52) using the 2014 Imaging Tool, the cRIO seems to get stuck on the rebooting step.

I have disabled all other NICs on my machine, disabled my firewall, and set my ip and subnet (10.15.12.5 and 255.255.255.0). The computer is connected to the cRIO through the DLink access point. I left the Imaging Tool running for an hour just in case it was actually that slow but it remains on the rebooting step. I also tried imaging the cRIO in safe mode but got the same results.

I am rapidly running out of ideas and any insight would be appreciated.

[Greg McKaskle]

Different laptops will have different behavior when an ethernet cable is disconnected -- or when the device directly connected reboots. One thing you may want to try is to plug the laptop and cRIO into a switch such as the DLink. The switch will not reboot and thus the laptop NIC will stay up.

Greg McKaskle

[rkoripalli]

I ran into this problem as well, I found that in order to fix this you should
1. Turn off the crio power
2. Turn the IP Reset switch ON
3. Turn the power on
4. After the crio turns on, turn it back off
5. While power is off, turn the IP Reset switch OFF
6. Turn the power back on and the process should work

[yash101]

I think we fixed it when we were imaging the cRIO today, by just switching to an older computer. I think some computers have been cursed by the computer gods, making it that they cannot image the cRIO .

yeah. that was kinda cheesy.

Anyways, to the point, just switch to a different computer and try again

[virtuald]

I also have had problems with the imaging tool this year, on both the cRio and the cRio-II. I was only able to format them after switching them to safe mode first.

[DjScribbles]

This issue would occur last year after your computer ran the Radio Configuration tool; the radio tool adds a bogus alternate IP address to your network adapter.

Go to your IP config screen, select advanced, and remove the 10.0.0.x IP address.

[otherguy]

Originally Posted by DjScribbles

Go to your IP config screen, select advanced, and remove the 10.0.0.x IP address.

There are more detailed instructions on how to do this here if required:
http://wpilib.screenstepslive.com/s/...-on-an-adapter

DjScribbles, thanks for posting info on why this is necessary to do, I didn't realize the configuration utility was the source of this problem.

[dmellich]

I posted this in another thread. This assumes other issues discussed i.e. IP address and network settings are good.

1. Put cRio in safe mode (hold reset button down for several seconds)
2. Launch NI imaging tool - select appropriate radio button in "Development Environment" and "Format Controller" checkbox and click apply.
3. A dialog box will pop up that says the cRio is in safe mode and cannot be imaged but gives the option to format. Click "format cRio"
4. The "Reconfiguring Device" dialog box comes up and first says it is formatting (maybe 30sec) then rebooting (another 30sec).
5. After the reboot completes, the same dialog box will indicate the format is complete.
6. Power down the cRio, turn safe mode off (dip switch on 8 slot - power cycle for 4 slot), turn on cRio. NOTE: when you turn on the cRio, the status light will flash 2 times (repeating). This indicates the chassis has detected an error in its software. Not to worry.
7. Click apply on the imaging tool - the "Reconfiguring Device" dialog box comes back up indicating it's formatting (maybe 20sec) then rebooting (maybe 30sec).
8. If all wen well it should then start re-imaging the cRio.

[BigDaddyKane527]

I had the same issue for the past few years. The rio would never reboot during re-imaging. A way that worked for me was to re-image it while the crio was plugged into the dlink and have the dlink connected to a wireless router. From there, the computer was plugged into the router and everything worked fine. Good luck with the rio!

[ubeatlenine]

I can confirm that switching computers resolved this issue for imaging both the cRIO and cRIO II. I guess some computers just aren't cut out for it. Thank you everyone for your suggestions!