01-11-2019 12:34 AM
I tried to update the firmware on one of our RoboRIOs tonight, but the FRC roboRIO Imaging Tool crashed partway through the Update Firmware process. (See attachment showing the information from the Windows Error Reporting entry in the Windows Event Log.)
The RoboRIO shows up still in the tool, but it shows a current firmware version of "unknown". Subsequent attempts to flash firmware fail.
I've tried:
I've tried flashing the v6 firmware using 2 different computers. They were plugged into the RoboRIO using the USB cable, running with other network adapters disabled, were running the tools as Admin, and had the Firewall and antivirus disabled. The roboRIO doesn't have any error conditions indicated by the LEDs or shown in the Web Dashboard.
The typical error message is below:
Any ideas? I was able to flash firmware on a different RoboRIO without any issue. Does this RoboRIO need to be replaced?
Thanks,
Will Rall
FRC Team 1318 - Issaquah Robotics Society
Solved! Go to Solution.
01-11-2019 10:29 AM - edited 01-11-2019 10:29 AM
Hello wrall,
From what I see in the Imaging Tool, it is possible that the crash had corrupted the installation of the firmware in the roboRIO. I recommend the following:
Thanks,
01-12-2019 09:08 PM
Hi Oscar,
I have tried going through those steps, as well as the suggestions posted here as of Thursday evening: https://www.chiefdelphi.com/t/2019-firmware-update-failing/337242
Unfortunately I don't have access to the RoboRIO during those hours on weekdays. I could still call to arrange a return/replacement if that is needed, or take the retry that evening and call back the next day approach.
Thanks
-Will
01-13-2019 02:13 PM
Hello Will,
I recommend we try getting in contact by phone with the support team, so they can understand better the behavior you are seeing in the different components (thanks for the super detailed first post you made), and can send more steps and resources to try.
If the device is indeed "bricked", we would process the repair by phone, too. I recommend you get the Serial Number of the device (located in the bottom side of the roboRIO in a white label) in case we need to follow that route.
Thanks,
01-14-2019 08:50 PM
On further inspection, if I try to switch the roboRIO into Safe Mode (by holding the "Reset" button for ~5 seconds after the RoboRIO has booted), the Status light flashes incessantly. I assume that this is an indication that the RoboRIO needs to be returned. I'll have someone call NI in the next couple days to set up a return.
Thanks
-Will Rall
01-14-2019 09:25 PM
Hello Will,
It does not necessarily mean that the roboRIO has to be returned, but that its software got corrupted. Please mention this when you get in contact with us by phone, so we can try recovering the software in your roboRIO before you have to ship it.
Thank you!
01-18-2019 06:22 PM
To update the thread: I called support and was able to resolve the issue with their help. They provided a special version of the firmware that I put onto a USB stick, and then I restarted the RoboRIO with the USB stick plugged in while holding the RESET button. This triggered it to flash the firmware on the USB stick. I was then able to flash the newest version of the Firmware, and the RoboRIO is now working perfectly.
02-20-2020 02:21 PM
Hello, I have the same issue trying to flash a roborio to setup a bench top robot for our FRC team. Tried different computers, safemode, etc, as suggested in this thread. Ready to try the USB boot. How can I get hold of this special image? (I could not locate NI support phone number). Thank you for your help.
02-20-2020 04:03 PM
Please find the NI support number for FIRST here:Connect with NI FRC Technical Support.
If you're outside the United States, you can call into the NI's local line for your location and ask to be transferred to the FIRST Support queue.
Thanks,
02-21-2020 11:31 AM
Thank you for the reply. Also noticed the phone number on the bottom of the the page (and every page on NI web site ... ). Update: Contacted support and received a link to the recovery image. Tks again