Discovering and Imaging the Device

cancel
Showing results for 
Search instead for 
Did you mean: 

RoboRIO 2 Imaging Issue

Solved!
Go to solution

We're working with imaging the SD card for the roboRIO and we're running into some issues with connecting to it over ethernet. It works fine over USB. The SD Card is a PNY Elite micro 32GB microSD card.

 

For setup, we used Balena Etcher to image it with FRC_roboRIO2_2025_v2.0.img.zip from FRC Game Tools 2025 Patch 1. This was done on a Framework 13 laptop with the SD expansion card slot.

 

We've attempted to image it with the roboRIO imaging tool and roboRIO Team Number Setter and have gotten nothing. The interesting thing is that there is no Current Image or Firmware version when we look at it in the imaging tool. I've attempted to ping the IP from a previous post here and the one shown in the Team Number Setter and got no response.

Screenshot 2025-02-15 214840.pngScreenshot 2025-02-15 214708.pngScreenshot 2025-02-15 220142.png

Screenshot 2025-02-15 220121.png

We've tried reimaging the card 3 times and have gotten the same results. We've tried cleaning out the slot to see if debris was in the way. We've tried resetting the roboRIO. None of these have solved our problems. Any help here would be appreciated.

0 Kudos
Message 1 of 2
(54 Views)
Solution
Accepted by topic author JamesTaylor9109

We solved our problem.

 

The steps taken were the following:

  1. Connect to roboRIO over USB
  2. Set the team number with the 2025 version of the roboRIO team number setter
  3. Set static IP on the roboRIO webserver as follows by connecting to the IP shown in the team number setter: https://docs.wpilib.org/en/latest/docs/networking/networking-introduction/ip-configurations.html
  4. Then configured radio with team number and passwords for wireless as follows: https://frc-radio.vivid-hosting.net/overview/programming-your-radio-at-home

 

The key problem was that while the roboRIO was recognized by the team number setter over ethernet, it was unable to update those settings. Connecting over USB was the reliable way to resolve our issue. And then fully configuring the IP of the roboRIO by con

0 Kudos
Message 2 of 2
(30 Views)