Roborio 1 not retaining memory

[KEVIN5610]

I have a robotic 1 we use for our FRC robot.  We can download our code and everything works fine.  if we power cycle we get no robot code(Red bar) on the driver station and the robot will not function which is leading me to believe there is a memory retention issue.  The robotic appears to have the correct image and firmware.   once we power cycle and get "no robot code", if we deploy our code again, everything works as planned.  Any suggestions???

[ThaysMolina]

Hi,

I'm Thays from NI. 

Could you try a factory reset of the device using the recovery file provided in this document FRC roboRIO STATUS LED Constantly Flashing - NI?

1. Download the recovery.cfg file.
2. Find a flash drive, remove everything from it, and reformat it as a FAT32 drive by right-clicking on the flash drive and selecting Format.. from the list.
3. Place only the recovery.cfg file on the flash drive.
4. Turn off your roboRIO.
5. Plug in the FAT32 formatted flash drive (with only the CFG file on it) into one of the two USB ports on the roboRIO.
6. While holding down the Reset button, turn on the roboRIO.
7. Let go of the Reset button after the STATUS LED has turned on and remains solid.
8. Watch the STATUS LED. It should stay on for about 60 seconds and not continuously blink the STATUS LED anymore without a pattern. Try the following recommendations if the device does not recognize the USB after a couple of attempts:
   1. Use a different flash drive. Smaller capacities work better.
   2. Use an externally powered USB hub between the roboRIO and the flash drive.
   3. Use an SD card to USB adapter, following the steps using the SD card instead of a USB flash drive. 
9. Turn off the roboRIO, remove the flash drive, and turn on the roboRIO.
10. Reimage the roboRIO through its USB or Ethernet port using the roboRIO Imaging Tool.

[KEVIN5610]

This issue appeared to be related to our Java code.  We don't completely understand the issue.  The code would compile and deploy but never show "robot code" on the driver station.  Reverting to an older version of the code made the issue go away.   We completed a line by line comparison and removed an unused variable and all is well now.

Thanks for your help