Based on my sigfox multi-board shield, it is possible to hack sigfox with a raspberry pi. The standard telecom Design firmware allow to use it as a modem. The raspberry Pi just have to send the expected AT commands
Configure the Raspberry-Pi
The serial port of the RaspberryPi is used for boot console and must be reconfigured to be available for application.
Edit /etc/inittab ; the last line should be
T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100
add a # in front of this line to disable it
#T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100
Then edit /boot/cmdline.txt and change the line from
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 ...
to
dwc_otg.lpm_enable=0 console=tty1 ...
Now you can reboot the raspberry Pi
Install console tool and connect
Once restarted, install minicom serial console
sudo apt-get install minicom
and launch it
minicom -b 9600 -o -D /dev/ttyAMA0
Now you can type any AT command like AT?
AT OK AT? ---------------- E => Echo I => Information Q => Quiet V => Verbose X => Extended result code Z => Reset ? => Help &F => Factory &V => Status &W => Save S200 => Reboot banner display
Hi,
thanks for your work.
I have a problem, i can’t make minicom work. I’m connected to my raspberry with ssh. When i run minicom on AMA0, i can’t use my keyboard. Do i need to use a real keyboard connected on my raspberry ? Is it possible to use ssh to interact with the minicom running on the rapsberry ?
Thx
According to our direct discussion, the cause was the version of rasbian used : wheezie is recommended.
Thank you for your answer.
I think I’ve made a mistake during my first test (i didn’t comment the line ttyAMA0 in /etc/inittab, i think).
So, i restart from a fresh whezzie installation : it worked !
Then, I have restart from a clean whezzie install, then upgrade to jessy, and then following the tuto again : it also works.
(i really thing it was my fault, the first time)