Definitely a RFM12B. And unless you specifically uploaded the RFM12B version of the software, it will have defaulted to the RFM69 software and the sketch will lock up and not communicate.
This should not affect how the Pi itself runs, but of course if the radio isnât working, youâll have no input to emonHub, and nothing into anywhere else downstream.
The firmware that Trystan linked to (post 51) MQTT change now nothing works even after returning to defaults - #51 by TrystanLea is definitely for the RFM12B and communicates at 9600 baud (youâll need that setting in emonhub.conf).
But that is not the same as what Brian posted here (post 63) MQTT change now nothing works even after returning to defaults - #63 by borpin
I have that file on my emonPi, and the C source contains this:
#define RF69_COMPAT 1 // define this to use the RF69 driver i.s.o. RF12
If the .hex was compiled from that, and this link
has that same line in the source, IT WONâT WORK because it will be using RFM69CW commands to a RFM12B radio.
You must make sure you get the RFM12B compiled version RFM12_Demo_ATmega328.cpp.hex
Notwithstanding that, you should still be able to program the Atmel '328P.
The first problem will be communicating with the Atmel '328P in programming mode. Thatâs not happening, according to
avrdude-original: stk500_recv(): programmer is not responding.
When youâve solved that, the second problem will be getting the correct sketch, or changing that line and recompiling, and uploading it to the '328P.
Sorry Iâm not a Pi expert, so I canât help with the how-to.
[Edit]
Have you changed the clock speed of your Pi? Remove the following lines from /boot/config.txt :
arm_freq=1200
arm_freq_min=600
and replace with
[pi3]
arm_freq=1200
arm_freq_min=600
[pi2]
arm_freq=900
arm_freq_min=600
[all]
