Andymark has a tutorial for flashing OpenWRT on the OM5P-AN and we tried it on both the AN and the AC and it just sits and waits for the interface the entire time. The FRC Configurator works fine on both of them, as well as the CloudTrax image flashing tool for their factory image. Any ideas?
Can’t say I’ve ever tried this. I’m not seeing anything on the openWRT webpages specific to the radio either… I’m sorry I can’t help more! If you do happen to find root cause and an answer, please post again so others may learn!
If I am not mistaken, the OM5P-AC is heavily locked down out of the box and the AN had it released for this season to lock it down. By locked down I mean that custom firmwares cannot be run on these radios as it was found that you can operate them outside of their licensed spectrum on custom firmware. This means that the OM5P Series Radios used for FRC **CANNOT HAVE CUSTOM FIRMWARES DEPLOYED TO THEM!**It is also against the rules to do this I think because you must run the FRC based firmware because it locks down the radio so you cant extract the key from the radio.
1 Like
More on why the OM5P-AN was discontinued: https://www.firstinspires.org/robotics/frc/blog/radio-silence
I’m not sure what rules apply to custom firmware, but the radio configuration tool can also flash the FRC firmware (and refuses to configure a radio that doesn’t have current FRC firmware), so you’d have a hard time using any sort of custom firmware at a competition.
This will point you in the right direction:
This is not a procedure for most people.
This thread is hilarious.
Related to the 2016 lockdown, huh. Nifty!
“If you have full access to the system then you have full access to the system. I don’t understand why having full access to the system should mean that you don’t have full access to the system.”
lolz.
OpenMesh is clearly trying to walk a line between what the customer wants and the heavy-handed edict from the FCC designed to protect the Wi-Fi airwaves from people who use custom firmware to use power levels in excess of what the device was FCC-certified to allow.
ASUS took an interesting tack of closing off the radio part of their firmware while leaving the rest of it open. So custom firmware providers can get the binary of the radio code and include it with their custom firmware, but it makes playing with the radio power much more difficult.