Today we’ve released firmware v1.2.5. We recommend that everyone update their radios to this version ASAP to avoid potential issues in the future.
Why is this a critical update?
We’ve received some units from the field where the flash memory that stores some of the radio’s calibration is corrupted. This causes the radio to go into a bootloop.
Here’s an example:
The 1.2.5 release has a mitigation to address this potential corruption. We recommend that all VH-109s and VH-113 be updated to this ASAP.
What to do if your radio is affected by this?
If this happens to your radio, we do have a way of recovering the radio remotely. Contact WCP Support, and they’ll coordinate the remote support with Vivid-Hosting.
There’s a macOS and Linux client. I’ll be publishing those today.
I’ve remotely supported teams who couldn’t figure out how to un-AP their radios in the past when their school firewalls blocked the connection. We just had them hotspot off their phone.
Unfortunately the only way to recover this requires restricted access to the device as the partition we’re accessing was explicitly called out as a protected region during the regulatory approvals.
Unfortunately not. However, we have so far only observed this behavior on earlier firmware releases from the factory at v1.0.
The KoP and FC radios were shipped with v1.1.2 installed.
Just my opinion, but something of this nature should be in a FRC blog post or some other official communication once everyone is happy with the procedure…
There are potentially a LOT of teams impacted. While CD has good reach, it’s not quite far enough to be a proper backstop solution.
I don’t know how far in advance KoP things are done or if this would be feasible, but maybe putting some kind of scary “UPDATE REQUIRED BEFORE USE” sticker on the radio box that you have to cut through to open would be a good way to prevent teams from missing it?
Are there any plans to add text specifying the installed firmware version to the configuration webpage? imo this was a huge oversight and made troubleshooting and upgrading firmware a pain. Other debugging info would be great too.
Open http://192.168.69.1/status (write “status” instead “configuration” in the URL of the Configuration Page) for detailed information about your radio.
After upgrading our radio to v1.2.5 it will no longer connect to our Rio. The radio was one of the ones given out at worlds this year, running 1.0.0 prior to upgrade. It was working prior to applying the firmware update. Any suggestions?
I’ve confirmed it’s not an issue with the ethernet cable or the rio ethernet port.
After the firmware upgrade I set the team number, SSID and WPA keys. I can connect to the wifi network and access other devices, such as photonvision on our coprocessors connected to the switch. The rio cannot be accessed using the static 10. IP address or the mDNS name.
Yes, I’ve confirmed that the IP is set correctly when connected via USB. This is the 10.TE.AM.2 IP I’m referring to. If we swap out the vivid hosting radio with one of the old FRC radios we’re able to connect to the Rio fine. I’m going to try applying the latest Rio firmware update from NI game tools this weekend to see if that has any effect.
