| web | https://bradslab.com |
| pronouns | he/him/his |
| web | https://bradslab.com |
| pronouns | he/him/his |
Maybe a couple attainable goals will help:
That’s probably enough. No need to get overly-ambitious and feel worse for failing to complete the list.
It turns out reverse engineering something like this is tedious and boring: inspect the i2c packet, try to match up the hex values with anything in the plaintext data. Reboot. Repeat. I2C, plaintext data. Plaintext data?
Wait. Why don't I just *add* a microcontroller to listen to the bad chip's serial output in plaintext? It cycles off every 20 seconds, and might miss transmissions in the first 5 seconds of that, but so what? Worst case I miss the peak wind gust measurement for the day.
By connecting to the red module's serial output, I can see that it boots up, initializes the radio, tries to do something else, then crashes and reboots. This loops continuously for about 20 seconds.
My plan was to sniff the i2c communications and match the data up to the plaintext data coming off the serial port. I figured I could just pop the radio module off the board and use an ESP32 or something to talk to it directly.