cRio Kernel Error/Reboots

[Marc P.]

Hello all!

I'm here asking for advice on behalf of Team Beta's programmers. The other night they were attempting to write some simple code to experiment with an encoder, with some success. Things seemed to be going well until the cRio inexplicably started rebooting itself.

The cRio powers on, boots up, runs the deployed code for just long enough for the classmate/driver station status to show "Teleoperated Disabled" for a split second before showing "No Robot Communication" as the cRio status light blinks on for a second, indicating it restarted.

The programmers are using C++/Wind River, the cRio is running image version 25, WPIlib and the build environments are all updated to the most recent downloadable versions.

My first thought was to format/re-image the cRio. While in the "not functioning properly" state, the cRio imaging tool can not find the cRio for re-imaging. After powering off the main breaker, I flipped the Safe Mode DIP to "on" and turned the breaker back on. The cRio then booted up, and was detected by the imaging tool. From there we were able to successfully format the cRio, and the imaging tool then said to power down, turn off the safe mode switch, and power back on. After doing so, the imaging tool was again able to detect the cRio, and successfully set the IP address and applied the v25 image. The cRio will then boot up fine, the classmate/driver station is able to connect, and the status shows "No Robot Code." It will sit like that for extended periods of time without issue.

The programmers then proceeded to compile and deploy basic sample code with seemingly no issue. Once the deployment finishes, the cRio is rebooted via the "Robot Reboot" button on the classmate/driver station. It again reconnects to the classmate/driver station just long enough for the status to show "Teleoperated Disabled" for a split second before changing back to "No Robot Communication."

With Wind River still open after deploying code, the following error pops up:

Target Exception

VxWorks6x_10.28.36.2: Exception in Kernel Task FRC-RobotTask:0x12816e0 at pc=0x218682C

Vector 0x300 : Data Access addr=0x992611E8 status=0x21867C0

The System has stopped.  Do you want to attach the debugger now?

(yes)   (no)

Clicking yes opens a tab with scrolling lines saying:

deadbeef:  Read access not allowed
deadbef0:  Read access not allowed
deadbef1:  Read access not allowed
deadbef2:  Read access not allowed
deadbef3:  Read access not allowed
deadbef4:  Read access not allowed
deadbef5:  Read access not allowed
...and so on

The cRio then continues in it's rebooting loop, after multiple cold boots/power cycles, and the only thing that seems to stop it is booting in Safe Mode, formatting, rebooting in normal mode, and re-imaging. But even that only works until any code is deployed, after which the cycle begins again.

Steps we have tried:

Full power cycles (turning off breaker, unplugging battery, reconnecting, turning breaker back on)
Removing all cRio modules
Formatting the cRio in safe mode
Re-imaging the cRio in normal mode
Blowing out the cRio with compressed air
Deploying default/sample code
Fresh battery

All to no avail. Is there anything else we can try before contacting NI?

Thank you all for any advice or assistance!