Hi, I keep getting an error on my SOM where after some period of time (sometimes several minutes after boot to hours) it can’t find i2c addresses of the Rugged Switchblox it is connected to. I’ve seen this behavior on multiple units. The only real fix is a full power down, and power up. Another weird thing is the UART serial interface only works on the SOM UART connection but not the Switchblox. Maybe this can clue you in on an answer? Thanks.
Hi there,
If you’re using a SwitchBlox Rugged that was shipped before May 2026, it will be running a firmware that sometimes interacts with the software running on Rugged SOM, via the shared I2C bus between the two boards.
To fix this, the SwitchBlox Rugged needs to be flashed with the latest version of the firmware.
Instructions on how to flash our boards can be found at the link below.
Meanwhile, we will email you with the latest firmware to flash.
Thanks Josh. I will give this a go. We received these units in June/July so not sure why it’s still happening but hopefully this is the problem.
Sadly the May 2026 date is more of a blurry date rather than a hard guide, and those boards aren’t serialized. It is reasonable to expect that it could still be running out of date firmware.
Hi Josh,
I flashed with the new firmware but still seems to do the same thing. When I give it anything more than a minimal level of throughput it enters the same “can’t write to register” state.
I saw another post that mentions flashing with “empty” firmware. Can I just erase what’s there and call it empty? Or is the new firmware you sent me “empty”
Empty firmware and the new firmware should behave the same, both will release the I2C lines, it’s just that the new firmware only releases the I2C after a few milliseconds.
Just to confirm, you are flash the SwitchBlox Rugged with it unconnected to Rugged SOM right?
Can you share more about the hardware setup? The power supply, what’s connected, and a screenshot of the GUI. That’d be helpful for debugging.
