Attempts to program firmware to the rfm2pi fail as follows
pi@raspberrypi:~/RFM2Pi/firmware/RF12_Demo_atmega328 $ avrdude -v -c arduino -p ATMEGA328P -P /dev/ttyAMA0 -b 38400 -U flash:w:RF12_Demo_atmega328.cpp.hex
avrdude-original: Version 6.1, compiled on Jul 7 2015 at 10:29:47
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch
System wide configuration file is "/etc/avrdude.conf"
User configuration file is "/root/.avrduderc"
User configuration file does not exist or is not a regular file, skipping
Using Port : /dev/ttyAMA0
Using Programmer : arduino
Overriding Baud Rate : 38400
avrdude-original: Using autoreset DTR on GPIO Pin 7
strace: |autoreset: Broken pipe
strace: |autoreset: Broken pipe
avrdude-original: stk500_recv(): programmer is not responding
Any pointers would be great. Is anyone using rfm2pi with a Pi3 ?
Firmware should be pre-loaded onto the RFM2Pi. Do you have an RFM12Pi or an RFM69Pi? Does the LED on the module lightup when the Pi is powered up?
If you have an RFM12Pi, set minicom to 9600 bps
sudo minicom -D /dev/ttyAMA0 -b9600
If you have an RFM69Pi, set minicom to 38400 bps
sudo minicom -D /dev/ttyAMA0 -b38400
Once you have the serial window open hit [v] to get the unit to return it’s firmware an settings.
Before you can use the serial port you will need to disconnect it from the terminal. Since your using a Pi3 first need to disable Bluetooth on the Pi3 and map UART1 back to UART0 (ttyAMA0), see blog post.
I highly recomend using our latest emonSD pre-built SD card image, it will work out of the box with the RFM69Pi. Follow user guide . The pre-built image is based on Raspiban Jessie has Emoncms, nodeRED and opneHAB all pre-installed.
Oh dear, did you try 9600 baud and sending serial ‘v’ ? You could try attaching the module while minicom is open to try and capture it;s initial serial output.
The serial baud of the RFM2Pi 's prior to the RFM69Pi’s (RFM12Pi’s?) did change to 57600 for a short time with the change from rfm12b to rfm69cw modules, they then changed to 38400 til end of production. so a RFM2Pi can be 9600,38400 or 57600
The fact your device is 57600 means it is not likely to be an rfm12b module but the later rfm69cw module, I’m not sure how important that may be to your project. certainly when writing your firmware it is important.
With that in mind the sketch you were originally trying to upload was now written for the rfm69 models, although it should still upload it will not function, (or tell you why).
And just for the record
won’t actually have the expected result, the ‘v’ option to return the firmware version and current configuration wasn’t added until after the baud was changed to 57600, hopefully the unrecognized option would invoke a full print of the help text.
You will need to use a RFM2Pi sketch that has a “# define RF69_COMPAT 1” line near the top to get the right JeeLib functions.
Now you have confirmed a working serial connection I hope the upload works for you, if it doesn’t can confirm the reset line is working by checking the led on the rfm2pi flashes (just as it would at sttartup) when trying to upload?
