I have an RFM2Pi module with an RF69 module (unmodified, as purchased around November last year). I believe it is the RFM69PI V3 but has a blue PCB not red.
It’s been working great, but I wanted to experiment with my own firmware on it. I figured before I did that, I should make sure that I can compile and get the stock firmware working.
If I upload the compiled firmware from the RFM2Pi repository (using the
update-RFM69.sh script) then everything works fine. Now, I want to compile it myself. I have checked out jeelib at revision 7fc95a72ec3202f79ac25df0e250a15df48f2f6c and have tried creating compiled hex files both using the Arduino IDE (version 1.6.12) and the Arduino-mk package (my preferred method since I can compile and upload from the Pi that way). Both compile fine and produce a hex file. I can upload the hex file to the device using avrdude and the autoreset script as documented, and once I’ve done that both can be interacted with over serial (e.g. ‘v’ shows the expected output).
However, neither show any packets being received. If I re-upload the pre-compiled hex, everything works fine again.
I suspect it’s possible we’re compiling with different versions of JeeLib, and there is some incompatibility? Please could you state which revision of jeelib is being used for the factory image?