cRIO Startup code corrupts on boot, reformatting doesn't help.

[WarrenPW]

Hello,
This week we have been having trouble with the cRIO in two different ways. First of all, the cRIO somehow managed to set itself to get an address via DHCP, and though multiple reformats didn't help, we were able to fix this with the MAX Measurement and Automation Explorer, but now when we try to boot the cRIO with deployed code, the robot reboots a couple of times, and then the status light blinks four times every second. MAX says that the error is that the cRIO had rebooted to many times and had been put into safe mode because of a corrupt startup program, but the code looks fine in Labview, and when we load the default code from a new project, the same thing happens. Is it possible that more than the TCP/IP settings got changed in the cRIO? If so, what setting would I need to change?Team 2085 Robodogs

[Ben_S]

WarrenPW,

That is strange!

A few questions:

1. Do you have the latest LabVIEW and DriverStation updates installed?
2. Did you re-image your cRIO with image v19 after installing the updates in step 1?
3. Can you post a screenshot of the error message MAX is giving you that indicates that "the cRIO had rebooted to many times and had been put into safe mode because of a corrupt startup program"?
4. Does this behavior happen when you build the default "FRC cRIO Robot Project" as a startup executable?
5. (See Information below) You can monitor the cRIO's memory and processor by opening the Distributed System Manager at Start»Programs»National Instruments»Distributed System Manager.

When the cRIO's status light blinks 4 times, that usually means:

"The software has crashed twice without rebooting or cycling power between crashes. This usually occurs when the chassis runs out of memory. Review your RT VI and check the memory usage. Modify the VI as necessary to solve the memory usage issue."