ArmadeusWiki - User contributions [en]

GSM/GPRS

2012-11-22T18:12:55Z

HerveDa: /* Sending AT commands "manually" */

This page will summarize informations to use the GSM/GPRS/3G module of the [[Wireless_extension_board|APF27Wireless board]] and the [[APF51Dev]] (optional).

==Introduction==
GSM/GPRS are generally driven through the RS-232 bus. AT commands are used to dialog with the module.
* GSM MODEM of the [[Wireless_extension_board|APF27Wireless extension board (APW)]] is connected to the UART2 (/dev/ttySMX1) of the [[APF27]].
* GSM/3G MODEM of the [[APF51Dev]] is connected to the i.MX processor through an UART implemented in the FPGA. So the corresponding bitfile has to loaded before trying to access the MODEM.
Both are using a Sagem's Hilo module. Hilo AT commands can be found [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf here]

==Linux configuration (APF27Dev only)==
* Linux will have to be configured in order to tell that an APW is connected to your [[APF27Dev]]:
<pre class="host">
$ make linux26-menuconfig
</pre>
<pre class="config">
System Type --->
Freescale MXC Implementations --->
...
Extension board (Wireless (APW)) --->
[*] GSM/GPRS Modem (NEW)
[ ] Bluetooth & WiFi module (NEW)
[ ] CSI (Camera) pass-through (NEW)
[ ] GPS module (NEW)
</pre>

<pre class="host">
$ make linux26
</pre>
* reflash you Linux kernel

==Configure serial port==
====APF27====
<pre class="apf">
# export GSM_DEVICE=/dev/ttySMX1 (or /dev/ttymxc1 on recent kernels)
# stty -F $GSM_DEVICE raw -echo -echoe -echok 115200
</pre>

====APF51Dev====

{{Note|Don't forget to put "Wireless" J42 jumper (near microSD connector) '''AND''' power on FPGA Bank 3 (with corresponding J39 jumper).}}
* On APF51Dev, GSM/3G module is accessed through serial ports synthetized in APF51's FPGA. So we have to load it first. (Needed dual UARTs FPGA firmware can be found under armadeus-4.0 distribution in ''firmware/pod_scripts'' directory, with the [[POD]] script needed to regenerate it, and is by default installed in rootfs).
<pre class="apf">
# load_fpga /lib/firmware/fpga/apf51_gsm_gps_firmware.bin
</pre>
* Once firmware loaded, drivers related to FPGA can be used :
<pre class="apf">
# modprobe irq_ocore
# modprobe 8250
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
# modprobe twin_uarts_irq_mng
# modprobe twin_uarts_16750
serial8250.0: ttyS0 at MMIO 0xb8000020 (irq = 320) is a TI16750
serial8250.0: ttyS1 at MMIO 0xb8000040 (irq = 321) is a TI16750
</pre>
* Bring MODEM out of reset state (POK_IN/PWON pin, connected to [[APF51_PMIC#GPIO|PMIC GPIO6]]):
<pre class="apf">
# modprobe wm831x-gpio
# echo 245 > /sys/class/gpio/export
# echo out > /sys/class/gpio/gpio245/direction
# echo 1 > /sys/class/gpio/gpio245/value
</pre>
* Configure serial port:
<pre class="apf">
# ls /dev/ttyS*
/dev/ttyS0 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3
</pre>

* If the /dev/ttyS[0-1] files don't exist, create it/them with ''mknod'' :
<pre class="apf">
# mknod /dev/ttyS0 c 4 64
# mknod /dev/ttyS1 c 4 65
</pre>
Then :
<pre class="apf">
# export GSM_DEVICE=/dev/ttyS0
# stty -F $GSM_DEVICE -echo -echoe -echok 115200
</pre>

==Basic Usage==
===Sending AT commands "manually"===
* Sending AT commands with ''minicom'' utility (one of the command coming with [[busybox]]):

{{Note|minicom seem to be remove use microcom instead}}

<pre class="apf">
# minicom $GSM_DEVICE
</pre>
( To exit ''minocom'' you will have to type '''<CTRL-x>''' )
* Check module presence:
<pre class="apf">
ATI3
SAGEM HiC,A.005.00

OK
</pre>

{{Note| If no echo are printed on serial console: you can't see what you're typing. In that case, to reactivate the echo, use:
<pre class="apf">
ATE1
</pre>
}}

{{Note| By default, the module starts in auto baudrate. This mays result in loss of communication with baud rate higher than 19200 bauds. To avoid problems, the baud rate has to be fixed (here to 115200 bauds):
<pre class="apf">
AT+IPR=115200
</pre>
}}

* Get constructor name:
<pre class="apf">
AT+CGMI
SAGEM

OK
</pre>
* Get model name:
<pre class="apf">
AT+CGMM
HILO GPRS

OK
</pre>
* Enter PIN code (here 0000). '''!! Use your own and beware that you will only get 3 tries !!:'''
<pre class="apf">
AT+CPIN="0000"

OK
</pre>
* Check PIN code status:
<pre class="apf">
AT+CPIN?
+CPIN: READY

OK
</pre>
{{Note|Don't launch further AT commands if PIN code wasn't entered successfully}}

* Check module status (0 Ready, 1 Unavailable, 2 Status unknown, 3 Ringing, 4 Call in progress, 5 Asleep):
<pre class="apf">
AT+CPAS
+CPAS: 0

OK
</pre>
* Get Indicator control (<battchg>[0-4],<signal>[0-4],<service>0/1,<message>0/1,<call>0/1,<smsfull>0/1):
<pre class="apf">
AT+CIND?
+CIND: 0,4,1,0,0,0,1

OK
</pre>
* Get signal quality (should be better than 12/99):
<pre class="apf">
AT+CSQ
+CSQ: 24,99

OK
</pre>
* Voice call "123456789" (; is important here to signify a voice call, otherwise a data call is tried and may fail if you don't have the right subscribe)
<pre class="apf">
ATD"123456789";
OK
</pre>
* Terminate current call:
<pre class="apf">
ATH
OK
</pre>

===Sending AT commands in shell scripts===

<source lang="bash">
GSM_DEVICE=/dev/ttyXXX
send_at_cmd()
{
echo -e -n "$1\015" > $GSM_DEVICE
sleep 1 # Adjustable ! (usleep)
}

send_at_cmd AT
</source>

* See ''target/test/test_gsm.sh'' for more details

==Sending SMS==
* Supposing you are already connected to the modem with cu
* Check if you can send SMS with your SIM card (you should get +CMGF: (0,1))
<pre class="apf">
AT+CMGF=?
</pre>
* If OK, switch to SMS sending mode:
<pre class="apf">
AT+CMGF=1
</pre>
* Write a message for 0661234567 phone number:
<pre class="apf">
AT+CMGW="0661326109"

> Hey ! How are you doing ??
> <-- Ctrl+z to end SMS here

+CMGW: 8
</pre>
* +CMGW give you the number of your SMS saved in SIM card or phone memory
* Then, at anytime, you can send your SMS with (pass previous number as parameter):
<pre class="apf">
AT+CMSS=8
</pre>

==Tools to look at==
* http://www.developershome.com/sms/freeLibForSMS.asp
* http://www.gnokii.org/
* http://www.alamin.org/en/index.html
* http://www.gammu.org/wiki/index.php?title=Gammu:Main_Page
* http://gatling.ikk.sztaki.hu/~kissg/gsm/index.html

==Data tranfers (EDGE/3G)==

===PPP installation (done by default on APF51)===
<pre class="host">
$ make linux26-menuconfig
</pre>

<pre class="config">
Device Drivers --->
[*] Network device support --->
<M> PPP (point-to-point protocol) support
[ ] PPP multilink support (EXPERIMENTAL)
[ ] PPP filtering
<M> PPP support for async serial ports
< > PPP support for sync tty ports
< > PPP Deflate compression
< > PPP BSD-Compress compression
< > PPP MPPE compression (encryption) (EXPERIMENTAL)
< > PPP over Ethernet (EXPERIMENTAL)
</pre>

<pre class="host">
$ make menuconfig
</pre>

<pre class="config">
Package Selection for the target --->
Networking applications --->
[*] pppd
[ ] filtering
[ ] radius
</pre>

<pre class="host">
$ make linux26 && make
</pre>

* reflash kernel & rootfs

===PPP configuration===
{{Note|Following instructions are given for the French operator "Bouygtel" and may need to be ajusted accordingly, depending on your operator/country}}

* Create a "chat" script that will be used to initiate MODEM dialup (here we use the "cat > xxxx << EOF trick" to automatically create the file, but you can also manually edit it with ''vi'' or ''nano''):
<pre class="apf">
# mkdir -p /etc/chatscripts/
# cat > /etc/chatscripts/bouygtel <<EOF
ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO ANSWER' ABORT DELAYED ABORT ERROR
'' AT
OK AT+IPR=115200
OK AT+CPIN="0000"
OK AT+CFUN=1
OK AT+COPS?
OK AT+CSQ
OK 'AT+CGDCONT=1,"IP","ebouygtel.com","",0,0'
OK 'AT&FE0Q0V1'
OK 'ATD*99#'
CONNECT ""
EOF
</pre>
* Don't forget to set the baudrate (default: 115200) to have a stable communication between the modem and the processor
* Don't forget to update "AT+CPIN=" with your real PIN code and "AT+CGDCONT" and "ATD*99#" with your operator parameters.
* If you want to test your chat script (verbose mode -v, on console -s, with 5 second timeout by default for commands -t 5), then launch:
<pre class="apf">
# /usr/sbin/chat -v -s -t 5 -f /etc/chatscripts/bouygtel > $GSM_DEVICE < $GSM_DEVICE
</pre>
* If this test was OK, you may have to poweroff/poweron the MODEM to bring it to its initial state and go further.

====For '''APF51'''====
* create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttyS0''):
<pre class="apf">
# mkdir -p /etc/ppp/peers/
# cat > /etc/ppp/peers/bouygtel <<EOF
noauth
connect "/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel"
debug
ttyS0
defaultroute
noipdefault
usepeerdns
EOF

# cat > /etc/ppp/options.ttyS0 <<EOF
115200
EOF
</pre>

====For '''APF27'''====
{{Note| Check if /dev/ttySMX1 exists, if not create it with :
<pre class="apf">
mknod /dev/ttySMX1 c 204 42
</pre>
}}
* create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttySMX1''):
<pre class="apf">
# mkdir -p /etc/ppp/peers/
# cat > /etc/ppp/peers/bouygtel <<EOF
noauth
connect "/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel"
debug
ttySMX1
defaultroute
noipdefault
usepeerdns
EOF

# cat > /etc/ppp/options.ttySMX1 <<EOF
115200
EOF
</pre>

===PPP Usage===
* Load PPP module:
<pre class="apf">
# modprobe ppp (APF27)
or
# modprobe ppp_async (APF51)
</pre>
* Setup serial port name depending on your platform (''/dev/ttyS0'' on APF51, ''/dev/ttySMX1'' on APF27)
<pre class="apf">
# export GSM_DEVICE=/dev/ttyS0
or
# export GSM_DEVICE=/dev/ttySMX1
</pre>

* Launch the beast:
<pre class="apf">
# pppd $GSM_DEVICE 115200 call bouygtel
</pre>

===Test===
<pre class="apf">
# ping www.google.fr
</pre>

=== Troubleshots ===
* Might be needed after a successful IP setup:
<pre class="apf">
# cp /etc/ppp/resolv.conf /etc/resolv.conf
# route add default ppp0 (due to defaultroute option in ppp ?)
</pre>

* To see what happened after having launched ''pppd'' or ''chat'':
<pre class="apf">
# tail -f /var/log/messages
</pre>

==GSM Muxing==
===Why ?===
* By default AT commands usage is single threaded, ie only one program can open MODEM serial port and send AT commands at a given time. However it could be interesting to be able to send multiple AT commands from multiple programs at the same time, for example in order to: have a PPP link, send SMS and monitor network signal quality.
* This can be done by a "GSM mux", if your MODEM support the GSM 07.10 muxing norm (which is the case with our HiLo modules).
===Build gsmmux===
* To build GSM mux (if not already done):
<pre class="host">
$ make menuconfig
</pre>
<pre class="config">
Package Selection for the target --->
Hardware handling --->
[*] gsmmux
Version to use (sagem) --->
</pre>
<pre class="host">
$ make
</pre>

===Use it===
* If you have access to Sagem's version (you will get as much as virtual serial port as times you pass ''/dev/ptmx'' to the daemon):
<pre class="apf">
# gsmMuxd -p $GSM_DEVICE -b 115200 -x /dev/ptmx /dev/ptmx /dev/ptmx
</pre>
* Virtual serial ports will be created in ''/dev/pts/'':
<pre class="apf">
/dev/pts/0 /dev/pts/1 /dev/pts/2
</pre>
* to know how ''/dev/ptmx'' & ''/dev/pts/x'' is working: [http://linux.die.net/man/4/ptmx]
* If you have telnet or SSH sessions running ''/dev/pts/0'' may already be used ans so virtual serial ports will be allocated from ''/dev/pts/1'', etc...

===Going further===
* In recent Linux kernels, there is also a driver to hanlde GSM muxing: n_gsm
* People wanting to do a "real" phone can take a look at [http://ofono.org/documentation ofono]

==SMS using SMS server tools 3==
simple AT commands can be used to sent SMS. If you need more flexibility or advanced management of your SMS, you can use SMS Server Tools 3.
SMS Server Tools 3 is a SMS Gateway software which can send and receive short messages through GSM modems and mobile phones.

===Build SMS Server Tools3===
* To build SMS Server Tools 3:
<pre class="host">
$ make menuconfig
</pre>
<pre class="config">
Package Selection for the target --->
Hardware handling --->
[*] SMS Server Tools3
</pre>
<pre class="host">
$ make
</pre>

=== Configuration ===
The SMS server can be configured by using a configuration file (smsd.conf) located on the target in the /etc/smsd directory.
The following parameters have to be verified:
* device: uart port used to communicate with the modem. If GSMUX is used, then this parameter is of form /dev/pts/x where is x is the number of the virtual port
* baudrate: baudrate of the uart port
* rtscts: must be yes
* incoming: yes if you want to receive SMS

=== Usage ===
start the sms deamon:
<pre class="host">
smsd -c /etc/smsd/smsd.conf
</pre>
Then put a SMS file in the /var/spool/outgoing directory. Once placed a SMS will be sent.

Incoming SMS can be read in the /var/spool/incoming directory.

Reports and logs are also generated.

==Links==
* [http://support.sagemcom.com/site/modele_fax.php?page=produit&numero_type=22&produit=877 HiLo 3G documentation at Sagem]
* [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf HiLo AT Commands]
* [http://www.developershome.com/sms/ SMS tutorial]
* http://wiki.openmoko.org/wiki/Neo_1973_and_Neo_FreeRunner_gsm_modem
* [http://www.anotherurl.com/library/at_test.htm AT Test commands]
* http://www.gsm-modem.de/gsm-faq.html
* [http://www.technologuepro.com/gsm/commande_at.htm Les commandes AT]
* [http://smstools3.kekekasvi.com SMS Server Tools 3]

[[Category:Wireless]]

GSM/GPRS

2012-11-22T18:12:09Z

HerveDa: /* Sending AT commands "manually" */

This page will summarize informations to use the GSM/GPRS/3G module of the [[Wireless_extension_board|APF27Wireless board]] and the [[APF51Dev]] (optional).

==Introduction==
GSM/GPRS are generally driven through the RS-232 bus. AT commands are used to dialog with the module.
* GSM MODEM of the [[Wireless_extension_board|APF27Wireless extension board (APW)]] is connected to the UART2 (/dev/ttySMX1) of the [[APF27]].
* GSM/3G MODEM of the [[APF51Dev]] is connected to the i.MX processor through an UART implemented in the FPGA. So the corresponding bitfile has to loaded before trying to access the MODEM.
Both are using a Sagem's Hilo module. Hilo AT commands can be found [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf here]

==Linux configuration (APF27Dev only)==
* Linux will have to be configured in order to tell that an APW is connected to your [[APF27Dev]]:
<pre class="host">
$ make linux26-menuconfig
</pre>
<pre class="config">
System Type --->
Freescale MXC Implementations --->
...
Extension board (Wireless (APW)) --->
[*] GSM/GPRS Modem (NEW)
[ ] Bluetooth & WiFi module (NEW)
[ ] CSI (Camera) pass-through (NEW)
[ ] GPS module (NEW)
</pre>

<pre class="host">
$ make linux26
</pre>
* reflash you Linux kernel

==Configure serial port==
====APF27====
<pre class="apf">
# export GSM_DEVICE=/dev/ttySMX1 (or /dev/ttymxc1 on recent kernels)
# stty -F $GSM_DEVICE raw -echo -echoe -echok 115200
</pre>

====APF51Dev====

{{Note|Don't forget to put "Wireless" J42 jumper (near microSD connector) '''AND''' power on FPGA Bank 3 (with corresponding J39 jumper).}}
* On APF51Dev, GSM/3G module is accessed through serial ports synthetized in APF51's FPGA. So we have to load it first. (Needed dual UARTs FPGA firmware can be found under armadeus-4.0 distribution in ''firmware/pod_scripts'' directory, with the [[POD]] script needed to regenerate it, and is by default installed in rootfs).
<pre class="apf">
# load_fpga /lib/firmware/fpga/apf51_gsm_gps_firmware.bin
</pre>
* Once firmware loaded, drivers related to FPGA can be used :
<pre class="apf">
# modprobe irq_ocore
# modprobe 8250
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
# modprobe twin_uarts_irq_mng
# modprobe twin_uarts_16750
serial8250.0: ttyS0 at MMIO 0xb8000020 (irq = 320) is a TI16750
serial8250.0: ttyS1 at MMIO 0xb8000040 (irq = 321) is a TI16750
</pre>
* Bring MODEM out of reset state (POK_IN/PWON pin, connected to [[APF51_PMIC#GPIO|PMIC GPIO6]]):
<pre class="apf">
# modprobe wm831x-gpio
# echo 245 > /sys/class/gpio/export
# echo out > /sys/class/gpio/gpio245/direction
# echo 1 > /sys/class/gpio/gpio245/value
</pre>
* Configure serial port:
<pre class="apf">
# ls /dev/ttyS*
/dev/ttyS0 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3
</pre>

* If the /dev/ttyS[0-1] files don't exist, create it/them with ''mknod'' :
<pre class="apf">
# mknod /dev/ttyS0 c 4 64
# mknod /dev/ttyS1 c 4 65
</pre>
Then :
<pre class="apf">
# export GSM_DEVICE=/dev/ttyS0
# stty -F $GSM_DEVICE -echo -echoe -echok 115200
</pre>

==Basic Usage==
===Sending AT commands "manually"===
* Sending AT commands with ''minicom'' utility (one of the command coming with [[busybox]]):

minicom seem to be remove use microcom instead

<pre class="apf">
# minicom $GSM_DEVICE
</pre>
( To exit ''minocom'' you will have to type '''<CTRL-x>''' )
* Check module presence:
<pre class="apf">
ATI3
SAGEM HiC,A.005.00

OK
</pre>

{{Note| If no echo are printed on serial console: you can't see what you're typing. In that case, to reactivate the echo, use:
<pre class="apf">
ATE1
</pre>
}}

{{Note| By default, the module starts in auto baudrate. This mays result in loss of communication with baud rate higher than 19200 bauds. To avoid problems, the baud rate has to be fixed (here to 115200 bauds):
<pre class="apf">
AT+IPR=115200
</pre>
}}

* Get constructor name:
<pre class="apf">
AT+CGMI
SAGEM

OK
</pre>
* Get model name:
<pre class="apf">
AT+CGMM
HILO GPRS

OK
</pre>
* Enter PIN code (here 0000). '''!! Use your own and beware that you will only get 3 tries !!:'''
<pre class="apf">
AT+CPIN="0000"

OK
</pre>
* Check PIN code status:
<pre class="apf">
AT+CPIN?
+CPIN: READY

OK
</pre>
{{Note|Don't launch further AT commands if PIN code wasn't entered successfully}}

* Check module status (0 Ready, 1 Unavailable, 2 Status unknown, 3 Ringing, 4 Call in progress, 5 Asleep):
<pre class="apf">
AT+CPAS
+CPAS: 0

OK
</pre>
* Get Indicator control (<battchg>[0-4],<signal>[0-4],<service>0/1,<message>0/1,<call>0/1,<smsfull>0/1):
<pre class="apf">
AT+CIND?
+CIND: 0,4,1,0,0,0,1

OK
</pre>
* Get signal quality (should be better than 12/99):
<pre class="apf">
AT+CSQ
+CSQ: 24,99

OK
</pre>
* Voice call "123456789" (; is important here to signify a voice call, otherwise a data call is tried and may fail if you don't have the right subscribe)
<pre class="apf">
ATD"123456789";
OK
</pre>
* Terminate current call:
<pre class="apf">
ATH
OK
</pre>

===Sending AT commands in shell scripts===

<source lang="bash">
GSM_DEVICE=/dev/ttyXXX
send_at_cmd()
{
echo -e -n "$1\015" > $GSM_DEVICE
sleep 1 # Adjustable ! (usleep)
}

send_at_cmd AT
</source>

* See ''target/test/test_gsm.sh'' for more details

==Sending SMS==
* Supposing you are already connected to the modem with cu
* Check if you can send SMS with your SIM card (you should get +CMGF: (0,1))
<pre class="apf">
AT+CMGF=?
</pre>
* If OK, switch to SMS sending mode:
<pre class="apf">
AT+CMGF=1
</pre>
* Write a message for 0661234567 phone number:
<pre class="apf">
AT+CMGW="0661326109"

> Hey ! How are you doing ??
> <-- Ctrl+z to end SMS here

+CMGW: 8
</pre>
* +CMGW give you the number of your SMS saved in SIM card or phone memory
* Then, at anytime, you can send your SMS with (pass previous number as parameter):
<pre class="apf">
AT+CMSS=8
</pre>

==Tools to look at==
* http://www.developershome.com/sms/freeLibForSMS.asp
* http://www.gnokii.org/
* http://www.alamin.org/en/index.html
* http://www.gammu.org/wiki/index.php?title=Gammu:Main_Page
* http://gatling.ikk.sztaki.hu/~kissg/gsm/index.html

==Data tranfers (EDGE/3G)==

===PPP installation (done by default on APF51)===
<pre class="host">
$ make linux26-menuconfig
</pre>

<pre class="config">
Device Drivers --->
[*] Network device support --->
<M> PPP (point-to-point protocol) support
[ ] PPP multilink support (EXPERIMENTAL)
[ ] PPP filtering
<M> PPP support for async serial ports
< > PPP support for sync tty ports
< > PPP Deflate compression
< > PPP BSD-Compress compression
< > PPP MPPE compression (encryption) (EXPERIMENTAL)
< > PPP over Ethernet (EXPERIMENTAL)
</pre>

<pre class="host">
$ make menuconfig
</pre>

<pre class="config">
Package Selection for the target --->
Networking applications --->
[*] pppd
[ ] filtering
[ ] radius
</pre>

<pre class="host">
$ make linux26 && make
</pre>

* reflash kernel & rootfs

===PPP configuration===
{{Note|Following instructions are given for the French operator "Bouygtel" and may need to be ajusted accordingly, depending on your operator/country}}

* Create a "chat" script that will be used to initiate MODEM dialup (here we use the "cat > xxxx << EOF trick" to automatically create the file, but you can also manually edit it with ''vi'' or ''nano''):
<pre class="apf">
# mkdir -p /etc/chatscripts/
# cat > /etc/chatscripts/bouygtel <<EOF
ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO ANSWER' ABORT DELAYED ABORT ERROR
'' AT
OK AT+IPR=115200
OK AT+CPIN="0000"
OK AT+CFUN=1
OK AT+COPS?
OK AT+CSQ
OK 'AT+CGDCONT=1,"IP","ebouygtel.com","",0,0'
OK 'AT&FE0Q0V1'
OK 'ATD*99#'
CONNECT ""
EOF
</pre>
* Don't forget to set the baudrate (default: 115200) to have a stable communication between the modem and the processor
* Don't forget to update "AT+CPIN=" with your real PIN code and "AT+CGDCONT" and "ATD*99#" with your operator parameters.
* If you want to test your chat script (verbose mode -v, on console -s, with 5 second timeout by default for commands -t 5), then launch:
<pre class="apf">
# /usr/sbin/chat -v -s -t 5 -f /etc/chatscripts/bouygtel > $GSM_DEVICE < $GSM_DEVICE
</pre>
* If this test was OK, you may have to poweroff/poweron the MODEM to bring it to its initial state and go further.

====For '''APF51'''====
* create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttyS0''):
<pre class="apf">
# mkdir -p /etc/ppp/peers/
# cat > /etc/ppp/peers/bouygtel <<EOF
noauth
connect "/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel"
debug
ttyS0
defaultroute
noipdefault
usepeerdns
EOF

# cat > /etc/ppp/options.ttyS0 <<EOF
115200
EOF
</pre>

====For '''APF27'''====
{{Note| Check if /dev/ttySMX1 exists, if not create it with :
<pre class="apf">
mknod /dev/ttySMX1 c 204 42
</pre>
}}
* create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttySMX1''):
<pre class="apf">
# mkdir -p /etc/ppp/peers/
# cat > /etc/ppp/peers/bouygtel <<EOF
noauth
connect "/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel"
debug
ttySMX1
defaultroute
noipdefault
usepeerdns
EOF

# cat > /etc/ppp/options.ttySMX1 <<EOF
115200
EOF
</pre>

===PPP Usage===
* Load PPP module:
<pre class="apf">
# modprobe ppp (APF27)
or
# modprobe ppp_async (APF51)
</pre>
* Setup serial port name depending on your platform (''/dev/ttyS0'' on APF51, ''/dev/ttySMX1'' on APF27)
<pre class="apf">
# export GSM_DEVICE=/dev/ttyS0
or
# export GSM_DEVICE=/dev/ttySMX1
</pre>

* Launch the beast:
<pre class="apf">
# pppd $GSM_DEVICE 115200 call bouygtel
</pre>

===Test===
<pre class="apf">
# ping www.google.fr
</pre>

=== Troubleshots ===
* Might be needed after a successful IP setup:
<pre class="apf">
# cp /etc/ppp/resolv.conf /etc/resolv.conf
# route add default ppp0 (due to defaultroute option in ppp ?)
</pre>

* To see what happened after having launched ''pppd'' or ''chat'':
<pre class="apf">
# tail -f /var/log/messages
</pre>

==GSM Muxing==
===Why ?===
* By default AT commands usage is single threaded, ie only one program can open MODEM serial port and send AT commands at a given time. However it could be interesting to be able to send multiple AT commands from multiple programs at the same time, for example in order to: have a PPP link, send SMS and monitor network signal quality.
* This can be done by a "GSM mux", if your MODEM support the GSM 07.10 muxing norm (which is the case with our HiLo modules).
===Build gsmmux===
* To build GSM mux (if not already done):
<pre class="host">
$ make menuconfig
</pre>
<pre class="config">
Package Selection for the target --->
Hardware handling --->
[*] gsmmux
Version to use (sagem) --->
</pre>
<pre class="host">
$ make
</pre>

===Use it===
* If you have access to Sagem's version (you will get as much as virtual serial port as times you pass ''/dev/ptmx'' to the daemon):
<pre class="apf">
# gsmMuxd -p $GSM_DEVICE -b 115200 -x /dev/ptmx /dev/ptmx /dev/ptmx
</pre>
* Virtual serial ports will be created in ''/dev/pts/'':
<pre class="apf">
/dev/pts/0 /dev/pts/1 /dev/pts/2
</pre>
* to know how ''/dev/ptmx'' & ''/dev/pts/x'' is working: [http://linux.die.net/man/4/ptmx]
* If you have telnet or SSH sessions running ''/dev/pts/0'' may already be used ans so virtual serial ports will be allocated from ''/dev/pts/1'', etc...

===Going further===
* In recent Linux kernels, there is also a driver to hanlde GSM muxing: n_gsm
* People wanting to do a "real" phone can take a look at [http://ofono.org/documentation ofono]

==SMS using SMS server tools 3==
simple AT commands can be used to sent SMS. If you need more flexibility or advanced management of your SMS, you can use SMS Server Tools 3.
SMS Server Tools 3 is a SMS Gateway software which can send and receive short messages through GSM modems and mobile phones.

===Build SMS Server Tools3===
* To build SMS Server Tools 3:
<pre class="host">
$ make menuconfig
</pre>
<pre class="config">
Package Selection for the target --->
Hardware handling --->
[*] SMS Server Tools3
</pre>
<pre class="host">
$ make
</pre>

=== Configuration ===
The SMS server can be configured by using a configuration file (smsd.conf) located on the target in the /etc/smsd directory.
The following parameters have to be verified:
* device: uart port used to communicate with the modem. If GSMUX is used, then this parameter is of form /dev/pts/x where is x is the number of the virtual port
* baudrate: baudrate of the uart port
* rtscts: must be yes
* incoming: yes if you want to receive SMS

=== Usage ===
start the sms deamon:
<pre class="host">
smsd -c /etc/smsd/smsd.conf
</pre>
Then put a SMS file in the /var/spool/outgoing directory. Once placed a SMS will be sent.

Incoming SMS can be read in the /var/spool/incoming directory.

Reports and logs are also generated.

==Links==
* [http://support.sagemcom.com/site/modele_fax.php?page=produit&numero_type=22&produit=877 HiLo 3G documentation at Sagem]
* [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf HiLo AT Commands]
* [http://www.developershome.com/sms/ SMS tutorial]
* http://wiki.openmoko.org/wiki/Neo_1973_and_Neo_FreeRunner_gsm_modem
* [http://www.anotherurl.com/library/at_test.htm AT Test commands]
* http://www.gsm-modem.de/gsm-faq.html
* [http://www.technologuepro.com/gsm/commande_at.htm Les commandes AT]
* [http://smstools3.kekekasvi.com SMS Server Tools 3]

[[Category:Wireless]]

How to create web sms sender

2012-10-21T17:12:09Z

HerveDa:

First install a web server

I choose lighttpd (make menuconfig ->Package selection for the target ). Select Show package that are also provide by busybox and lighttpd.

We also need php support (Interpreter language and scripting). Enable php and fastcgi, active also PCRE extenstion.

Second adapt exemple script for sending sms. This is mine [http://pastebin.com/sL4V3eFp] (I still have to improve it so if you have comments)

Third create web pages a basic formular and a php treatement page or all in one. Dont forget that we have to send smsm in GSM 03.38 so I have made my small convert function [http://pastebin.com/MJrDx25j].

How to create web sms sender

2012-10-19T03:52:29Z

HerveDa: New page: First install a web server I choose lighttpd (make menuconfig ->Package selection for the target ). Select Show package that are also provide by busybox and lighttpd. Second adapt exempl...

First install a web server

I choose lighttpd (make menuconfig ->Package selection for the target ). Select Show package that are also provide by busybox and lighttpd.

Second adapt exemple script for sending sms

Third create web page.

User:HerveDa

2012-10-19T03:18:40Z

HerveDa:

Project:

[[Aircraft modelling assitant pilot]] (school project)

[[How to create web sms sender]]

User:HerveDa

2012-10-19T03:16:35Z

HerveDa:

Project:

[[Aircraft modelling assitant pilot]] (school project)

[[WEB SMS]]

Ubuntu/Debian installation prerequisites

2012-10-14T02:45:04Z

HerveDa: /* Optional packages */

==Mandatory packages==
* you can use the following commands (one at a time) to get them (assuming your userid is allowed to use ''sudo'' (execution of commands as root)):
<pre class="host">
sudo apt-get install -y build-essential gcc g++ autoconf automake libtool bison flex gettext
sudo apt-get install -y patch subversion texinfo wget git-core
sudo apt-get install -y libncurses5 libncurses5-dev
sudo apt-get install -y zlib1g-dev liblzo2-2 liblzo2-dev
sudo apt-get install -y libacl1 libacl1-dev gawk cvs curl lzma
sudo apt-get install -y uuid-dev mercurial
</pre>

{{Warning|For recent Ubuntu and Debian based systems, the following is now required if your ''/bin/sh'' is '''not''' pointing to ''/bin/bash'':
<pre class="host">
$ ls -al /bin/sh
lrwxrwxrwx 1 root root 4 2007-12-08 18:33 /bin/sh -> dash

$ sudo dpkg-reconfigure dash
and select no
</pre>
Indeed dash do not support all the capabilities needed by Buildroot (our build system).
}}

* if your distribution is localized in a language different of English, you will need to install "en_US" locale in order to compile the toolchain (by default our toolchain (uClibc) is configured to only support English). If not, you will get compilation errors like this one:
<pre class="host">
...
extra/locale/locale_mmap.h:46: error: '__LOCALE_DATA_WCctype_II_LEN' undeclared here (not in a function)
...
</pre>
To solve this, install en_US.UTF-8 locale with the following:
<pre class="host">
$ sudo dpkg-reconfigure locales
</pre>

==Optional packages==
Not mandatory but useful to add for compiling some Buildroot packages:
<pre class="host">
sudo apt-get -y install libglib2.0-dev
sudo apt-get -y install libnetpbm10-dev (for fbtest)
sudo apt-get -y install python-xcbgen (for Matchbox)
</pre>

===Java devt===
====Ubuntu====

* To compile java jamvm and gnu-classpath:
<pre class="host">
sudo apt-get -y install gcj-jdk
</pre>

====Debian====
To compile java jamvm and gnu-classpath:
<pre class="host">
sudo apt-get -y install java-gcj-compat-dev default-jdk
</pre>

Aircraft modelling assitant pilot

2012-06-08T19:09:49Z

HerveDa:

This project was to create an pilot assistant for aircraft model making.

The idea it to have the hard real time part on the FPGA and the soft on the CPU.

The system have two informations altitude from barometric sensor and positioning from an three axis gyroscope.

The system have to control the plane if the pilot lost control

This picture resume the architecture of the project.

[[Image:architecture.jpg]]

If the program estimate the pilot did not loose the control FPGA forward PWM signal from the receiver to servo motors

If the pilot lost control the FPGA generate PWM signal.

File:Architecture.jpg

2012-06-08T19:06:25Z

HerveDa:

File:Architecture.svg

2012-06-08T19:03:59Z

HerveDa:

Aircraft modelling assitant pilot

2012-06-08T19:03:06Z

HerveDa:

GSM/GPRS

2012-06-08T18:19:42Z

HerveDa: /* APF51Dev */

This page will summarize informations to use the GSM/GPRS/3G module of the [[Wireless_extension_board|APF27Wireless board]] and the [[APF51Dev]] (optional).

==Introduction==
GSM/GPRS are generally driven through the RS-232 bus. AT commands are used to dialog with the module.
* GSM MODEM of the [[Wireless_extension_board|APF27Wireless extension board (APW)]] is connected to the UART2 (/dev/ttySMX1) of the [[APF27]].
* GSM/3G MODEM of the [[APF51Dev]] is connected to the i.MX processor through an UART implemented in the FPGA. So the corresponding bitfile has to loaded before trying to access the MODEM.
Both are using a Sagem's Hilo module. Hilo AT commands can be found [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf here]

==Linux configuration (APF27Dev only)==
* Linux will have to be configured in order to tell that an APW is connected to your [[APF27Dev]]:
<pre class="host">
$ make linux26-menuconfig
</pre>
<pre class="config">
System Type --->
Freescale MXC Implementations --->
...
Extension board (Wireless (APW)) --->
[*] GSM/GPRS Modem (NEW)
[ ] Bluetooth & WiFi module (NEW)
[ ] CSI (Camera) pass-through (NEW)
[ ] GPS module (NEW)
</pre>

<pre class="host">
$ make linux26
</pre>
* reflash you Linux kernel

==Configure serial port==
====APF27====
<pre class="apf">
# export GSM_DEVICE=/dev/ttySMX1 (or /dev/ttymxc1 on recent kernels)
# stty -F $GSM_DEVICE raw -echo -echoe -echok 115200
</pre>

====APF51Dev====

* Don't forget to put "Wireless" jumper J42 on your [[APF51Dev]] (near microSD connector) '''AND''' power on FPGA Bank 3 (with corresponding jumper J39).
* On APF51Dev, GSM/3G module is accessed through serial ports synthetized in APF51's FPGA. So we have to load it first. (Needed dual UARTs FPGA firmware can be found under armadeus-4.0 distribution in ''firmware/pod_scripts'' directory, with the [[POD]] script needed to regenerate it, and is by default installed in rootfs).
<pre class="apf">
# load_fpga /lib/firmware/fpga/apf51_gsm_gps_firmware.bin
</pre>
* Once firmware loaded, drivers related to FPGA can be used :
<pre class="apf">
# modprobe irq_ocore
# modprobe 8250
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
# modprobe twin_uarts_irq_mng
# modprobe twin_uarts_16750
serial8250.0: ttyS0 at MMIO 0xb8000020 (irq = 320) is a TI16750
serial8250.0: ttyS1 at MMIO 0xb8000040 (irq = 321) is a TI16750
</pre>
* Bring MODEM out of reset state (POK_IN/PWON pin, connected to [[APF51_PMIC#GPIO|PMIC GPIO6]]):
<pre class="apf">
# modprobe wm831x-gpio
# echo 245 > /sys/class/gpio/export
# echo out > /sys/class/gpio/gpio245/direction
# echo 1 > /sys/class/gpio/gpio245/value
</pre>
* Configure serial port:
<pre class="apf">
# ls /dev/ttyS*
/dev/ttyS0 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3
</pre>

* If the /dev/ttyS[0-1] files don't exist, create it/them with ''mknod'' :
<pre class="apf">
# mknod /dev/ttyS0 c 4 64
# mknod /dev/ttyS1 c 4 65
</pre>
Then :
<pre class="apf">
# export GSM_DEVICE=/dev/ttyS0
# stty -F $GSM_DEVICE raw -echo -echoe -echok 115200
</pre>

==Basic Usage==
===Sending AT commands "manually"===
* Sending AT commands with ''cu'' utility (be sure to [[cu/uucp|have installed it before]]):
<pre class="apf">
# cu -l $GSM_DEVICE
</pre>
( To exit ''cu'' you will have to type ~. )
* Check module presence:
<pre class="apf">
ATI3
SAGEM HiC,A.005.00

OK
</pre>

{{Note| If no echo are printed on serial console: you can't see what you're typing. In that case, to reactivate the echo, use:
<pre class="apf">
ATE1
</pre>
}}

{{Note| By default, the module starts in auto baudrate. This mays result in loss of communication with baud rate higher than 19200 bauds. To avoid problems, the baud rate has to be fixed (here to 115200 bauds):
<pre class="apf">
AT+IPR=115200
</pre>
}}

* Get constructor name:
<pre class="apf">
AT+CGMI
SAGEM

OK
</pre>
* Get model name:
<pre class="apf">
AT+CGMM
HILO GPRS

OK
</pre>
* Enter PIN code (here 0000). '''!! Use your own and beware that you will only get 3 tries !!:'''
<pre class="apf">
AT+CPIN="0000"

OK
</pre>
* Check PIN code status:
<pre class="apf">
AT+CPIN?
+CPIN: READY

OK
</pre>
{{Note|Don't launch further AT commands if PIN code wasn't entered successfully}}

* Check module status (0 Ready, 1 Unavailable, 2 Status unknown, 3 Ringing, 4 Call in progress, 5 Asleep):
<pre class="apf">
AT+CPAS
+CPAS: 0

OK
</pre>
* Get Indicator control (<battchg>[0-4],<signal>[0-4],<service>0/1,<message>0/1,<call>0/1,<smsfull>0/1):
<pre class="apf">
AT+CIND?
+CIND: 0,4,1,0,0,0,1

OK
</pre>
* Get signal quality (should be better than 12/99):
<pre class="apf">
AT+CSQ
+CSQ: 24,99

OK
</pre>
* Voice call "123456789" (; is important here to signify a voice call, otherwise a data call is tried and may fail if you don't have the right subscribe)
<pre class="apf">
ATD"123456789";
OK
</pre>
* Terminate current call:
<pre class="apf">
ATH
OK
</pre>

===Sending AT commands in shell scripts===

<source lang="bash">
GSM_DEVICE=/dev/ttyXXX
send_at_cmd()
{
echo -e -n "$1\015" > $GSM_DEVICE
sleep 1 # Adjustable ! (usleep)
}

send_at_cmd AT
</source>

* See ''target/test/test_gsm.sh'' for more details

==Sending SMS==
* Supposing you are already connected to the modem with cu
* Check if you can send SMS with your SIM card (you should get +CMGF: (0,1))
<pre class="apf">
AT+CMGF=?
</pre>
* If OK, switch to SMS sending mode:
<pre class="apf">
AT+CMGF=1
</pre>
* Write a message for 0661234567 phone number:
<pre class="apf">
AT+CMGW="0661326109"

> Hey ! How are you doing ??
> <-- Ctrl+z to end SMS here

+CMGW: 8
</pre>
* +CMGW give you the number of your SMS saved in SIM card or phone memory
* Then, at anytime, you can send your SMS with (pass previous number as parameter):
<pre class="apf">
AT+CMSS=8
</pre>

==Tools to look at==
* http://www.developershome.com/sms/freeLibForSMS.asp
* http://www.gnokii.org/
* http://www.alamin.org/en/index.html
* http://www.gammu.org/wiki/index.php?title=Gammu:Main_Page
* http://gatling.ikk.sztaki.hu/~kissg/gsm/index.html

==Data tranfers (EDGE/3G)==

===PPP installation (done by default on APF51)===
<pre class="host">
$ make linux26-menuconfig
</pre>

<pre class="config">
Device Drivers --->
[*] Network device support --->
<M> PPP (point-to-point protocol) support
[ ] PPP multilink support (EXPERIMENTAL)
[ ] PPP filtering
<M> PPP support for async serial ports
< > PPP support for sync tty ports
< > PPP Deflate compression
< > PPP BSD-Compress compression
< > PPP MPPE compression (encryption) (EXPERIMENTAL)
< > PPP over Ethernet (EXPERIMENTAL)
</pre>

<pre class="host">
$ make menuconfig
</pre>

<pre class="config">
Package Selection for the target --->
Networking applications --->
[*] pppd
[ ] filtering
[ ] radius
</pre>

<pre class="host">
$ make linux26 && make
</pre>

* reflash kernel & rootfs

===PPP configuration===
{{Note|Following instructions are given for the French operator "Bouygtel" and may need to be ajusted accordingly, depending on your operator/country}}

* Create a "chat" script that will be used to initiate MODEM dialup (here we use the "cat > xxxx << EOF trick" to automatically create the file, but you can also manually edit it with ''vi'' or ''nano''):
<pre class="apf">
# mkdir -p /etc/chatscripts/
# cat > /etc/chatscripts/bouygtel <<EOF
ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO ANSWER' ABORT DELAYED ABORT ERROR
'' AT
OK AT+IPR=115200
OK AT+CPIN="0000"
OK AT+CFUN=1
OK AT+COPS?
OK AT+CSQ
OK 'AT+CGDCONT=1,"IP","ebouygtel.com","",0,0'
OK 'AT&FE0Q0V1'
OK 'ATD*99#'
CONNECT ""
EOF
</pre>
* Don't forget to set the baudrate (default: 115200) to have a stable communication between the modem and the processor
* Don't forget to update "AT+CPIN=" with your real PIN code and "AT+CGDCONT" and "ATD*99#" with your operator parameters.
* If you want to test your chat script (verbose mode -v, on console -s, with 5 second timeout by default for commands -t 5), then launch:
<pre class="apf">
# /usr/sbin/chat -v -s -t 5 -f /etc/chatscripts/bouygtel > $GSM_DEVICE < $GSM_DEVICE
</pre>
* If this test was OK, you may have to poweroff/poweron the MODEM to bring it to its initial state and go further.

====For '''APF51'''====
* create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttyS0''):
<pre class="apf">
# mkdir -p /etc/ppp/peers/
# cat > /etc/ppp/peers/bouygtel <<EOF
noauth
connect "/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel"
debug
ttyS0
defaultroute
noipdefault
usepeerdns
EOF

# cat > /etc/ppp/options.ttyS0 <<EOF
115200
EOF
</pre>

====For '''APF27'''====
{{Note| Check if /dev/ttySMX1 exists, if not create it with :
<pre class="apf">
mknod /dev/ttySMX1 c 204 42
</pre>
}}
* create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttySMX1''):
<pre class="apf">
# mkdir -p /etc/ppp/peers/
# cat > /etc/ppp/peers/bouygtel <<EOF
noauth
connect "/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel"
debug
ttySMX1
defaultroute
noipdefault
usepeerdns
EOF

# cat > /etc/ppp/options.ttySMX1 <<EOF
115200
EOF
</pre>

===PPP Usage===
* Load PPP module:
<pre class="apf">
# modprobe ppp (APF27)
or
# modprobe ppp_async (APF51)
</pre>
* Setup serial port name depending on your platform (''/dev/ttyS0'' on APF51, ''/dev/ttySMX1'' on APF27)
<pre class="apf">
# export GSM_DEVICE=/dev/ttyS0
or
# export GSM_DEVICE=/dev/ttySMX1
</pre>

* Launch the beast:
<pre class="apf">
# pppd $GSM_DEVICE 115200 call bouygtel
</pre>

===Test===
<pre class="apf">
# ping www.google.fr
</pre>

=== Troubleshots ===
* Might be needed after a successful IP setup:
<pre class="apf">
# cp /etc/ppp/resolv.conf /etc/resolv.conf
# route add default ppp0 (due to defaultroute option in ppp ?)
</pre>

* To see what happened after having launched ''pppd'' or ''chat'':
<pre class="apf">
# tail -f /var/log/messages
</pre>

==GSM Muxing==
===Why ?===
* By default AT commands usage is single threaded, ie only one program can open MODEM serial port and send AT commands at a given time. However it could be interesting to be able to send multiple AT commands from multiple programs at the same time, for example in order to: have a PPP link, send SMS and monitor network signal quality.
* This can be done by a "GSM mux", if your MODEM support the GSM 07.10 muxing norm (which is the case with our HiLo modules).
===Build gsmmux===
* To build GSM mux (if not already done):
<pre class="host">
$ make menuconfig
</pre>
<pre class="config">
Package Selection for the target --->
Hardware handling --->
[*] gsmmux
Version to use (sagem) --->
</pre>
<pre class="host">
$ make
</pre>

===Use it===
* If you have access to Sagem's version (you will get as much as virtual serial port as times you pass ''/dev/ptmx'' to the daemon):
<pre class="apf">
# gsmMuxd -p $GSM_DEVICE -b 115200 -x /dev/ptmx /dev/ptmx /dev/ptmx
</pre>
* Virtual serial ports will be created in ''/dev/pts/'':
<pre class="apf">
/dev/pts/0 /dev/pts/1 /dev/pts/2
</pre>
* to know how ''/dev/ptmx'' & ''/dev/pts/x'' is working: [http://linux.die.net/man/4/ptmx]
* If you have telnet or SSH sessions running ''/dev/pts/0'' may already be used ans so virtual serial ports will be allocated from ''/dev/pts/1'', etc...

===Going further===
* In recent Linux kernels, there is also a driver to hanlde GSM muxing: n_gsm
* People wanting to do a "real" phone can take a look at [http://ofono.org/documentation ofono]

==Links==
* [http://support.sagemcom.com/site/modele_fax.php?page=produit&numero_type=22&produit=877 HiLo 3G documentation at Sagem]
* [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf HiLo AT Commands]
* [http://www.developershome.com/sms/ SMS tutorial]
* http://wiki.openmoko.org/wiki/Neo_1973_and_Neo_FreeRunner_gsm_modem
* [http://www.anotherurl.com/library/at_test.htm AT Test commands]
* http://www.gsm-modem.de/gsm-faq.html
* [http://www.technologuepro.com/gsm/commande_at.htm Les commandes AT]

[[Category:Wireless]]

GSM/GPRS

2012-06-08T18:18:23Z

HerveDa:

This page will summarize informations to use the GSM/GPRS/3G module of the [[Wireless_extension_board|APF27Wireless board]] and the [[APF51Dev]] (optional).

==Introduction==
GSM/GPRS are generally driven through the RS-232 bus. AT commands are used to dialog with the module.
* GSM MODEM of the [[Wireless_extension_board|APF27Wireless extension board (APW)]] is connected to the UART2 (/dev/ttySMX1) of the [[APF27]].
* GSM/3G MODEM of the [[APF51Dev]] is connected to the i.MX processor through an UART implemented in the FPGA. So the corresponding bitfile has to loaded before trying to access the MODEM.
Both are using a Sagem's Hilo module. Hilo AT commands can be found [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf here]

==Linux configuration (APF27Dev only)==
* Linux will have to be configured in order to tell that an APW is connected to your [[APF27Dev]]:
<pre class="host">
$ make linux26-menuconfig
</pre>
<pre class="config">
System Type --->
Freescale MXC Implementations --->
...
Extension board (Wireless (APW)) --->
[*] GSM/GPRS Modem (NEW)
[ ] Bluetooth & WiFi module (NEW)
[ ] CSI (Camera) pass-through (NEW)
[ ] GPS module (NEW)
</pre>

<pre class="host">
$ make linux26
</pre>
* reflash you Linux kernel

==Configure serial port==
====APF27====
<pre class="apf">
# export GSM_DEVICE=/dev/ttySMX1 (or /dev/ttymxc1 on recent kernels)
# stty -F $GSM_DEVICE raw -echo -echoe -echok 115200
</pre>

====APF51Dev====


* Don't forget to put "Wireless" jumper J42 on your [[APF51Dev]] (near microSD connector) '''AND''' power on FPGA Bank 3 (with corresponding jumper J39).

* On APF51Dev, GSM/3G module is accessed through serial ports synthetized in APF51's FPGA. So we have to load it first. (Needed dual UARTs FPGA firmware can be found under armadeus-4.0 distribution in ''firmware/pod_scripts'' directory, with the [[POD]] script needed to regenerate it, and is by default installed in rootfs).
<pre class="apf">
# load_fpga /lib/firmware/fpga/apf51_gsm_gps_firmware.bin
</pre>
* Once firmware loaded, drivers related to FPGA can be used :
<pre class="apf">
# modprobe irq_ocore
# modprobe 8250
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
# modprobe twin_uarts_irq_mng
# modprobe twin_uarts_16750
serial8250.0: ttyS0 at MMIO 0xb8000020 (irq = 320) is a TI16750
serial8250.0: ttyS1 at MMIO 0xb8000040 (irq = 321) is a TI16750
</pre>
* Bring MODEM out of reset state (POK_IN/PWON pin, connected to [[APF51_PMIC#GPIO|PMIC GPIO6]]):
<pre class="apf">
# modprobe wm831x-gpio
# echo 245 > /sys/class/gpio/export
# echo out > /sys/class/gpio/gpio245/direction
# echo 1 > /sys/class/gpio/gpio245/value
</pre>
* Configure serial port:
<pre class="apf">
# ls /dev/ttyS*
/dev/ttyS0 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3
</pre>

* If the /dev/ttyS[0-1] files don't exist, create it/them with ''mknod'' :
<pre class="apf">
# mknod /dev/ttyS0 c 4 64
# mknod /dev/ttyS1 c 4 65
</pre>
Then :
<pre class="apf">
# export GSM_DEVICE=/dev/ttyS0
# stty -F $GSM_DEVICE raw -echo -echoe -echok 115200
</pre>

==Basic Usage==
===Sending AT commands "manually"===
* Sending AT commands with ''cu'' utility (be sure to [[cu/uucp|have installed it before]]):
<pre class="apf">
# cu -l $GSM_DEVICE
</pre>
( To exit ''cu'' you will have to type ~. )
* Check module presence:
<pre class="apf">
ATI3
SAGEM HiC,A.005.00

OK
</pre>

{{Note| If no echo are printed on serial console: you can't see what you're typing. In that case, to reactivate the echo, use:
<pre class="apf">
ATE1
</pre>
}}

{{Note| By default, the module starts in auto baudrate. This mays result in loss of communication with baud rate higher than 19200 bauds. To avoid problems, the baud rate has to be fixed (here to 115200 bauds):
<pre class="apf">
AT+IPR=115200
</pre>
}}

* Get constructor name:
<pre class="apf">
AT+CGMI
SAGEM

OK
</pre>
* Get model name:
<pre class="apf">
AT+CGMM
HILO GPRS

OK
</pre>
* Enter PIN code (here 0000). '''!! Use your own and beware that you will only get 3 tries !!:'''
<pre class="apf">
AT+CPIN="0000"

OK
</pre>
* Check PIN code status:
<pre class="apf">
AT+CPIN?
+CPIN: READY

OK
</pre>
{{Note|Don't launch further AT commands if PIN code wasn't entered successfully}}

* Check module status (0 Ready, 1 Unavailable, 2 Status unknown, 3 Ringing, 4 Call in progress, 5 Asleep):
<pre class="apf">
AT+CPAS
+CPAS: 0

OK
</pre>
* Get Indicator control (<battchg>[0-4],<signal>[0-4],<service>0/1,<message>0/1,<call>0/1,<smsfull>0/1):
<pre class="apf">
AT+CIND?
+CIND: 0,4,1,0,0,0,1

OK
</pre>
* Get signal quality (should be better than 12/99):
<pre class="apf">
AT+CSQ
+CSQ: 24,99

OK
</pre>
* Voice call "123456789" (; is important here to signify a voice call, otherwise a data call is tried and may fail if you don't have the right subscribe)
<pre class="apf">
ATD"123456789";
OK
</pre>
* Terminate current call:
<pre class="apf">
ATH
OK
</pre>

===Sending AT commands in shell scripts===

<source lang="bash">
GSM_DEVICE=/dev/ttyXXX
send_at_cmd()
{
echo -e -n "$1\015" > $GSM_DEVICE
sleep 1 # Adjustable ! (usleep)
}

send_at_cmd AT
</source>

* See ''target/test/test_gsm.sh'' for more details

==Sending SMS==
* Supposing you are already connected to the modem with cu
* Check if you can send SMS with your SIM card (you should get +CMGF: (0,1))
<pre class="apf">
AT+CMGF=?
</pre>
* If OK, switch to SMS sending mode:
<pre class="apf">
AT+CMGF=1
</pre>
* Write a message for 0661234567 phone number:
<pre class="apf">
AT+CMGW="0661326109"

> Hey ! How are you doing ??
> <-- Ctrl+z to end SMS here

+CMGW: 8
</pre>
* +CMGW give you the number of your SMS saved in SIM card or phone memory
* Then, at anytime, you can send your SMS with (pass previous number as parameter):
<pre class="apf">
AT+CMSS=8
</pre>

==Tools to look at==
* http://www.developershome.com/sms/freeLibForSMS.asp
* http://www.gnokii.org/
* http://www.alamin.org/en/index.html
* http://www.gammu.org/wiki/index.php?title=Gammu:Main_Page
* http://gatling.ikk.sztaki.hu/~kissg/gsm/index.html

==Data tranfers (EDGE/3G)==

===PPP installation (done by default on APF51)===
<pre class="host">
$ make linux26-menuconfig
</pre>

<pre class="config">
Device Drivers --->
[*] Network device support --->
<M> PPP (point-to-point protocol) support
[ ] PPP multilink support (EXPERIMENTAL)
[ ] PPP filtering
<M> PPP support for async serial ports
< > PPP support for sync tty ports
< > PPP Deflate compression
< > PPP BSD-Compress compression
< > PPP MPPE compression (encryption) (EXPERIMENTAL)
< > PPP over Ethernet (EXPERIMENTAL)
</pre>

<pre class="host">
$ make menuconfig
</pre>

<pre class="config">
Package Selection for the target --->
Networking applications --->
[*] pppd
[ ] filtering
[ ] radius
</pre>

<pre class="host">
$ make linux26 && make
</pre>

* reflash kernel & rootfs

===PPP configuration===
{{Note|Following instructions are given for the French operator "Bouygtel" and may need to be ajusted accordingly, depending on your operator/country}}

* Create a "chat" script that will be used to initiate MODEM dialup (here we use the "cat > xxxx << EOF trick" to automatically create the file, but you can also manually edit it with ''vi'' or ''nano''):
<pre class="apf">
# mkdir -p /etc/chatscripts/
# cat > /etc/chatscripts/bouygtel <<EOF
ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO ANSWER' ABORT DELAYED ABORT ERROR
'' AT
OK AT+IPR=115200
OK AT+CPIN="0000"
OK AT+CFUN=1
OK AT+COPS?
OK AT+CSQ
OK 'AT+CGDCONT=1,"IP","ebouygtel.com","",0,0'
OK 'AT&FE0Q0V1'
OK 'ATD*99#'
CONNECT ""
EOF
</pre>
* Don't forget to set the baudrate (default: 115200) to have a stable communication between the modem and the processor
* Don't forget to update "AT+CPIN=" with your real PIN code and "AT+CGDCONT" and "ATD*99#" with your operator parameters.
* If you want to test your chat script (verbose mode -v, on console -s, with 5 second timeout by default for commands -t 5), then launch:
<pre class="apf">
# /usr/sbin/chat -v -s -t 5 -f /etc/chatscripts/bouygtel > $GSM_DEVICE < $GSM_DEVICE
</pre>
* If this test was OK, you may have to poweroff/poweron the MODEM to bring it to its initial state and go further.

====For '''APF51'''====
* create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttyS0''):
<pre class="apf">
# mkdir -p /etc/ppp/peers/
# cat > /etc/ppp/peers/bouygtel <<EOF
noauth
connect "/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel"
debug
ttyS0
defaultroute
noipdefault
usepeerdns
EOF

# cat > /etc/ppp/options.ttyS0 <<EOF
115200
EOF
</pre>

====For '''APF27'''====
{{Note| Check if /dev/ttySMX1 exists, if not create it with :
<pre class="apf">
mknod /dev/ttySMX1 c 204 42
</pre>
}}
* create the PPPd config files (''/etc/ppp/peers/bouygtel'' and ''/etc/ppp/options.ttySMX1''):
<pre class="apf">
# mkdir -p /etc/ppp/peers/
# cat > /etc/ppp/peers/bouygtel <<EOF
noauth
connect "/usr/sbin/chat -v -t 5 -f /etc/chatscripts/bouygtel"
debug
ttySMX1
defaultroute
noipdefault
usepeerdns
EOF

# cat > /etc/ppp/options.ttySMX1 <<EOF
115200
EOF
</pre>

===PPP Usage===
* Load PPP module:
<pre class="apf">
# modprobe ppp (APF27)
or
# modprobe ppp_async (APF51)
</pre>
* Setup serial port name depending on your platform (''/dev/ttyS0'' on APF51, ''/dev/ttySMX1'' on APF27)
<pre class="apf">
# export GSM_DEVICE=/dev/ttyS0
or
# export GSM_DEVICE=/dev/ttySMX1
</pre>

* Launch the beast:
<pre class="apf">
# pppd $GSM_DEVICE 115200 call bouygtel
</pre>

===Test===
<pre class="apf">
# ping www.google.fr
</pre>

=== Troubleshots ===
* Might be needed after a successful IP setup:
<pre class="apf">
# cp /etc/ppp/resolv.conf /etc/resolv.conf
# route add default ppp0 (due to defaultroute option in ppp ?)
</pre>

* To see what happened after having launched ''pppd'' or ''chat'':
<pre class="apf">
# tail -f /var/log/messages
</pre>

==GSM Muxing==
===Why ?===
* By default AT commands usage is single threaded, ie only one program can open MODEM serial port and send AT commands at a given time. However it could be interesting to be able to send multiple AT commands from multiple programs at the same time, for example in order to: have a PPP link, send SMS and monitor network signal quality.
* This can be done by a "GSM mux", if your MODEM support the GSM 07.10 muxing norm (which is the case with our HiLo modules).
===Build gsmmux===
* To build GSM mux (if not already done):
<pre class="host">
$ make menuconfig
</pre>
<pre class="config">
Package Selection for the target --->
Hardware handling --->
[*] gsmmux
Version to use (sagem) --->
</pre>
<pre class="host">
$ make
</pre>

===Use it===
* If you have access to Sagem's version (you will get as much as virtual serial port as times you pass ''/dev/ptmx'' to the daemon):
<pre class="apf">
# gsmMuxd -p $GSM_DEVICE -b 115200 -x /dev/ptmx /dev/ptmx /dev/ptmx
</pre>
* Virtual serial ports will be created in ''/dev/pts/'':
<pre class="apf">
/dev/pts/0 /dev/pts/1 /dev/pts/2
</pre>
* to know how ''/dev/ptmx'' & ''/dev/pts/x'' is working: [http://linux.die.net/man/4/ptmx]
* If you have telnet or SSH sessions running ''/dev/pts/0'' may already be used ans so virtual serial ports will be allocated from ''/dev/pts/1'', etc...

===Going further===
* In recent Linux kernels, there is also a driver to hanlde GSM muxing: n_gsm
* People wanting to do a "real" phone can take a look at [http://ofono.org/documentation ofono]

==Links==
* [http://support.sagemcom.com/site/modele_fax.php?page=produit&numero_type=22&produit=877 HiLo 3G documentation at Sagem]
* [http://www.libelium.com/tienda/catalog/images/arduino/AT_Commands.pdf HiLo AT Commands]
* [http://www.developershome.com/sms/ SMS tutorial]
* http://wiki.openmoko.org/wiki/Neo_1973_and_Neo_FreeRunner_gsm_modem
* [http://www.anotherurl.com/library/at_test.htm AT Test commands]
* http://www.gsm-modem.de/gsm-faq.html
* [http://www.technologuepro.com/gsm/commande_at.htm Les commandes AT]

[[Category:Wireless]]

Aircraft modelling assitant pilot

2012-05-31T19:51:16Z

HerveDa: New page: This project was to create an pilot assistant for aircraft model making. The idea it to have the hard real time part on the FPGA and the soft on the CPU. The system have two informations...

User:HerveDa

2012-05-31T19:43:14Z

HerveDa:

Project:

[[Aircraft modelling assitant pilot]] (school project)

User:HerveDa

2012-05-31T19:40:38Z

HerveDa: New page: Project: Aircraft modelling assitant pilot (school project)

Project:

Aircraft modelling assitant pilot (school project)

MemberList

2012-01-23T19:54:23Z

HerveDa: /* Here is the list of the (active) members and their skills */

==Here is the list of the (active) members and their skills==

This list is maintained by the users themself.

*0: Novice
*1: Notions. At least one successfull experiment
*2: Confirmed
 

{| border="1" cellpadding="5" cellspacing="0" summary="Signal connections"
|- style="background:#efefef;"
! '''Name / IRC Nickname''' || '''Linux Apps'''|| '''Linux Drivers'''|| '''FPGA''' || '''Board Design''' || '''Projet/Domain'''
|----------------
|[[User:Salocin68|Nicolas Colombain / Salocin]] || 1 || 1 || 1 || 2 || domotics
|----------------
|[[User:JulienB|Julien Boibessot / Artemys]] || 2 || 2 || 0 || 1 || multimedia
|----------------
|[[User:JeanBaptisteM|Jean-Baptiste Mayer / JiBee]] || 2 || 1 || 1 || 1 || robotics
|----------------
|[[User:NicolasA|Nicolas Aguirre]] || 2 || 0 || 1 || 1 || multimedia
|----------------
|[[User:BenoitC|Benoît Canet]] || 2 || 0 || 0 || 0 || multimedia
|----------------
|[[User:SonZerro|Sonzerro]] || 0 || 0 || 1 || 2 || domotics
|----------------
|[[User:HenriG|Henri Geist]] || 1 || 1 || 0 || 1 || robotics
|----------------
|[[User:BorredonB|Bernard Borredon]] || 2 || 1 || 0 || 1 || domotics
|----------------
|[[User:ThomasB|Thomas Bores]] || 2 || 0 || 0 || 1 || Entertainment
|----------------
|[[User:FabriceM|Fabrice Mousset / KroMignon]] || 1 || 1 || 2 || 1 || Domotics & multimedia
|----------------
|[[User:AmineH|Amine EL HEDADI]] || 2 || 2 || 0 || 0 || domotics & robotics
|----------------
|[[User:PhilippeM|Philippe Monteil]] || 2 || 0 || 0 || 0 || multimedia
|----------------
|[[User:CedricZ|Cédric Zmyj]] || 0 || 0 || 0 || 0 || domotics & robotics
|----------------
|[[User:JeanMichelN|Jean Michel Naimo / jeanmi12 ]] || 2 || 1 || 1 || 1 || Domotics & entertainment
|----------------
|[[User:OlivierC|Olivier Coutanceau]] || 1 || 0 || 0 || 0 || multimedia
|----------------
|[[User:ArnaudC|Arnaud COFFINET]] || 0 || 0 || 1 || 2 || multimedia & domotics
|----------------
|[[User:SylvainP|Sylvain PARRINO]] || 2 || 1 || 0 || 0 || robotics
|----------------
|[[User:AurelienH|Aurélien HIRON]] || 2 || 0 || 0 || 1 || robotics
|----------------
|[[User:GuillaumeT|Guillaume TRANNOY]] || 0 || 0 || 0 || 2 || domotics & robotics
|----------------
|[[User:JulienN|Julien NICOLAS / jujun]] || 2 || 1 || 0 || 1 || multimedia & network
|----------------
|[[User:StephaneF|Stéphane Falck]] || 0 || 0 || 0 || 0 || multimedia & robotics & domotics
|----------------
|[[User:GillesD|Gilles DUSSIN/ Sellig]] || 1 || 0 || 1 || 1 || robotics
|----------------
|[[User:MaximeL|Maxime Liron]] || 0 || 0 || 0 || 0 || domotics, robotics & multimedia
|----------------
|[[User:NicolasC|Nicolas CHARLERY/ realniko]] || 2 || 0 || 0 || 0 || electronic
|----------------
|[[User:BenoitJ|Benoit JESTER]] || 0 || 0 || 0 || 0 || robotics
|----------------
|[[User:FabienM|Fabien MARTEAU/ FabM]] || 1 || 2 || 1 || 1 || robotics,domotics
|----------------
|[[User:XavierA|Xavier AZNAR]] || 1 || 1 || 0 || 0 || environment, entertainment, domotic
|----------------
|[[User:AlbericA|Albéric AUBLANC / PoueT]] || 2 || 0 || 1 || 0 || domotics & multimedia, robotics, entertainment,
|----------------
|[[User:FredericB| Frédéric Blain / creber]] || 2 || 1 || 0 || 0 || system, domotics
|----------------
|[[User:JeanBaptisteMa| Jean-Baptiste Maillet]] || 2 || 1 || 0 || 0 || system
|----------------
|[[User:JeanFrancoisR| Jean-François Rousval]] || 2 || 1 || 0 || 1 ||
|----------------
|[[User:JulienPeeters| Julien Peeters]] || 2 || 1 || 0 || 0 || domotics, real-time, entertainment, network
|----------------
|[[User:YoannC| Yoann Congal / Alpheb]] || 0 || 0 || 0 || 1 || robotics
|----------------
|[[User:MatthieuT| Matthieu Texier / weeber]] || 1 || 0 || 1 || 0 || robotics, real-time
|----------------
|[[User:MartialG| Martial Guex]] || 2 || 1 || 1 || 2 || transceiver RF, real-time, wireless
|----------------
|[[User:NicolasL| Nicolas Lantz]] || 2 || 2 || 1 || 1 ||
|----------------
|[[User:GuillaumeD| Guillaume DELVIT]] || 1 || 1 || 1 || 1 || system, asynchronous CPU
|----------------
|[[User:BernardR|Bernard REMOND ]] || x || x || x || x ||
|----------------
|[[User:SamirH| Samir HAMNACHE]] || 0 || 0 || 0 || 1 || électronique
|----------------
|[[User:OlivierT|Olivier TARDIEU]] || 0 || 0 || 0 || 1 || électronique,robotics,domotics
|----------------
|[[User:ThibautR|Thibault Rétornaz]] || 1 || 1 || 1 || 0 || bio-med, électronique
|----------------
|[[User:FrancoisM|Francois Minaud]] || 1 || 1 || 1 || 0 || domotics, real-time, network
|----------------
|[[User:BrunoS|Bruno Suarez]] || 2 || 0 || 0 || 0 || électronique, Network
|----------------
|[[User:guillaumeDe|Guillaume Denis]] || 0 || 0 || 2 || 1 || Electronique numérique, FPGA
|----------------
|[[User:KevinP|Kévin PETIT]] || 1 || 0 || 1 || 1 || Multimedia
|----------------
|[[User:PierreBa|Pierre Baudemont / b4ud3]] || 2 || 0 || 1 || 0 || domotics, robotics
|----------------
|[[User:BrunoL|Bruno Landré]] || 0 || 0 || 0 || 0 || robotics
|----------------
|[[User:AntonioMB|Antonio Meléndez]] || 0 || 0 || 1 || 2 || domotics, robotics, eletcronics
|----------------
|[[User:MichelTe|Michel Le Mer]] || 0 || 0 || 2 || 2 || electronics, software
|----------------
|[[User:JulienBa|Julien Baley]] || 0 || 0 || 0 || 0 ||
|----------------
|[[User:FrankA|Frank ANJEAUX]] || 1 || 0 || 0 || 1 || software,robotics, domotics, electronics
|----------------
|[[User:JulienViaud|Julien viaud/polric]] || 2 || 0 || 1 || 1 ||
|----------------
|[[User:NicolasCa|Nicolas CARTIER]] || 1 || 1 || 0 || 2 || domotics & robotics
|----------------
|[[User:PierreAlexandreS|Pierre Alexandre SCHEMBRI]] || 2 || 1 || 2 || 2 || electronics, board design, embedded software, FPGA, robotics, low power
|----------------
|[[User:AlexG|Alex GONZALEZ]] || 2 || 2 || 0 || 1 || telecommunications, network & multimedia
|----------------
|[[User:JulienL|Julien Lefrique / apapi]] || 1 || 0 || 1 || 1 ||
|----------------
|[[User:PaoloB|Paolo Bernini / nihil84]] || 2 || 1 || 0 || 0 || robotics, real-time
|----------------
|[[User:MichielE|Michiel Ettema]] || 0 || 0 || 0 || 1 || telecommunications, networking
|----------------
|[[User:NicolasD|Nicolas Duclos]] || 2 || 1 || 0 || 0 || telecommunications, domotics and funs
|----------------
|[[User:SebastienP|Sebastien Philippe]] || 1 || 2 || 1 || 2 || electronics, board design, embedded linux
|----------------
|[[User:PaulM|Paul MONSINJON]] || 1 || 1 || 2 || 1 || robotics, fpga, embedded linux
|----------------
|[[User:OlivierR|Olivier REYNET]] || 1 || 0 || 0 || 0 || robotics, linux, networking
|----------------
|[[User:HugoP|Hugo Petit]] || 0 || 0 || 1 || 2 || electronics, automotive, board design, embedded software
|----------------
|[[User:PhilippeL|Philippe Leduc]] || 1 || 0 || 1 || 1 || robotics, real-time, embedded software, domotic
|----------------
|[[User:PierreDe|Pierre Delarboulas]] || 1 || 1 || 0 || 0 || robotics, domotic
|----------------
|[[User:WilliamB|William Benharbone]] || 0 || 0 || 1 || 1 || electronics, board design and funs
|----------------
|[[User:JeanJacquesP|JeanJacques Pitrolle]] || 2 || 1 || 0 || 0 || embedded software, robotics
|----------------
|[[User:SebastienVC|Sébastien Van Cauwenberghe]] || 2 || 2 || 2 || 0 || Power Electronics, Embedded Systems, FPGA's
|----------------
|[[User:PhilBB|Phil Bergeron-Burns]] || 0 || 0 || 2 || 0 || bio-medical
|----------------
|[[User:JaumeF|Jaume Figueras i Jové]] || 0 || 0 || 2 || 0 || academic, mapping
|----------------
|[[User:MathieuB|Mathieu Boucher]] || 1 || 2 || 1 || 0 ||
|----------------
|[[User:SamuelM|Samuel Martin / smartin]] || 2 || 0 || 1 || 1 || embedded systems, real-time, robotics, multimedia
|----------------
|[[User:GaelV|Gaël Vanderbruggen]] || 1 || 0 || 0 || 0 || bio-medical, robotics, multimedia
|----------------
|[[User:JeanMarcM| pieddemamouth/Jean-Marc Montanier]] || 1 || 0 || 0 || 1 || robotics
|----------------
|[[User:ChaoyiH| Chaoyi HU]] || 1 || 0 || 0 || 2 || entertainement, telecommunications, electronic
|----------------
|[[User:FrancoisG| Francois Goudal / Fanfwe]] || 2 || 2 || 1 || 1 || robotics, telecommunications
|----------------
|[[User:PhilippeLe| Philippe Le Rhun]] || 1 || 0 || 0 || 2 || entertainement, robotics, domotic
|----------------
|[[User:JeremieG| Jeremie Girouard]] || 0 || 0 || 0 || 0 || expérimentations,learning, Embedded Systems
|----------------
|[[User:RafalK| Rafal Kapela]] || 2 || 0 || 2 || 0 || Multimedia, real-time video content processing
|----------------
|[[User:XavierB| Xavier Bruhière]] || 1 || 1 || 1 || 1 || Robotics, domotic, learning
|----------------
||[[User:HerveDa| Dang Hervé]] || 0 || 0 || 0 || 0 || Robotics, aeronautics...
|}

==Links==
* [[Members | Geographical position of the members]]

[[Category:Association]]

Kermit

2012-01-12T16:37:50Z

HerveDa: Undo revision 10400 by HerveDa (Talk)

Kermit is a serial line terminal emulator that allows you to take control of your board through the RS232 line. With it you can have access to the U-Boot/Linux console of your APF without needing to connect a keyboard/screen to the board. ([http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/ For more informations on remote console])

==Installation==
The 'sudo' command requires from the user to be registered in the 'sudo' group or to be in the sudoers list on your PC.
===On *Ubuntu / Debian===
$ sudo apt-get install ckermit

you may have to configure your distribution to accept compatible software from the internet. This can be done through the synaptic package manager -> repositories.. ->debian software -> Non-DFSG-compatible software.

===On Fedora===
# rpm -q ckermit

===On OpenSUSE 11.3===
# sudo zypper addrepo http://download.opensuse.org/repositories/openSUSE:/11.3:/Contrib/standard/ Contrib
# zypper install ckermit

==Configuration==
* Edit/Create ''.kermrc'' file in your ''$HOME/'' directory (ex: ''/home/james/.kermrc'') and fill it with:
set line /dev/ttyS0
set speed 115200
set carrier-watch off
set handshake none
set flow-control none
robust
set file type bin
set file name lit
set rec pack 1000
set send pack 1000
set window 5
set transmit linefeed on
{{:Serial port selection generalities}}

==Usage==
* To launch it:
<pre class="host>
$ kermit -c
</pre>
* If you get an error message such:
<pre class="host>
/dev/ttyS0
?SET SPEED has no effect without prior SET LINE
</pre>
then recheck that you have read/write rights on the serial port (Typically on Ubuntu: you are not member of "dialout" group).
On OpenSUSE 11.3 you may need to be in "dialout" and 'uucp" groups and give the rights to write in /var/lock:
<pre class="host>
sudo chmod 777 /var/lock
</pre>

* To switch from terminal mode to command mode:
CTRL + \ then c
* To switch from command mode to terminal mode:
C-Kermit>c then ENTER
* To quit:
Switch in command mode
C-Kermit>q then ENTER

== Usefull tips ==

* Download a file via serial in U-Boot :
<pre class="apf">
BIOS> loadb
## Ready for binary (kermit) download to 0xA0000000 at 115200 bps...
</pre>
Then type <Ctrl-\>c and send your file with command :
<pre class="apf">
kermit> send filename
</pre>

==Links==
* http://www.columbia.edu/kermit/ckermit.html

Kermit

2012-01-12T16:37:15Z

HerveDa: Undo revision 10399 by HerveDa (Talk)

Kermit is a serial line terminal emulator that allows you to take control of your board through the RS232 line. With it you can have access to the U-Boot/Linux console of your APF without needing to connect a keyboard/screen to the board. ([http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/ For more informations on remote console])

==Installation==
The 'sudo' command requires from the user to be registered in the 'sudo' group or to be in the sudoers list on your PC.
===On *Ubuntu / Debian===
$ sudo apt-get install ckermit

$ sudo apt-get install gkermit -testé sur Debian 6

you may have to configure your distribution to accept compatible software from the internet. This can be done through the synaptic package manager -> repositories.. ->debian software -> Non-DFSG-compatible software.

===On Fedora===
# rpm -q ckermit

===On OpenSUSE 11.3===
# sudo zypper addrepo http://download.opensuse.org/repositories/openSUSE:/11.3:/Contrib/standard/ Contrib
# zypper install ckermit

==Configuration==
* Edit/Create ''.kermrc'' file in your ''$HOME/'' directory (ex: ''/home/james/.kermrc'') and fill it with:
set line /dev/ttyS0
set speed 115200
set carrier-watch off
set handshake none
set flow-control none
robust
set file type bin
set file name lit
set rec pack 1000
set send pack 1000
set window 5
set transmit linefeed on
{{:Serial port selection generalities}}

==Usage==
* To launch it:
<pre class="host>
$ kermit -c
</pre>
* If you get an error message such:
<pre class="host>
/dev/ttyS0
?SET SPEED has no effect without prior SET LINE
</pre>
then recheck that you have read/write rights on the serial port (Typically on Ubuntu: you are not member of "dialout" group).
On OpenSUSE 11.3 you may need to be in "dialout" and 'uucp" groups and give the rights to write in /var/lock:
<pre class="host>
sudo chmod 777 /var/lock
</pre>

* To switch from terminal mode to command mode:
CTRL + \ then c
* To switch from command mode to terminal mode:
C-Kermit>c then ENTER
* To quit:
Switch in command mode
C-Kermit>q then ENTER

== Usefull tips ==

* Download a file via serial in U-Boot :
<pre class="apf">
BIOS> loadb
## Ready for binary (kermit) download to 0xA0000000 at 115200 bps...
</pre>
Then type <Ctrl-\>c and send your file with command :
<pre class="apf">
kermit> send filename
</pre>

==Links==
* http://www.columbia.edu/kermit/ckermit.html

Kermit

2012-01-12T16:36:36Z

HerveDa:

Kermit

2012-01-12T16:35:12Z

HerveDa: /* On *Ubuntu / Debian */

Kermit is a serial line terminal emulator that allows you to take control of your board through the RS232 line. With it you can have access to the U-Boot/Linux console of your APF without needing to connect a keyboard/screen to the board. ([http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/ For more informations on remote console])

==Installation==
The 'sudo' command requires from the user to be registered in the 'sudo' group or to be in the sudoers list on your PC.
===On *Ubuntu / Debian===
$ sudo apt-get install ckermit

$ sudo apt-get install gkermit -testé sur Debian 6

you may have to configure your distribution to accept compatible software from the internet. This can be done through the synaptic package manager -> repositories.. ->debian software -> Non-DFSG-compatible software.

===On Fedora===
# rpm -q ckermit

===On OpenSUSE 11.3===
# sudo zypper addrepo http://download.opensuse.org/repositories/openSUSE:/11.3:/Contrib/standard/ Contrib
# zypper install ckermit

==Configuration==
* Edit/Create ''.kermrc'' file in your ''$HOME/'' directory (ex: ''/home/james/.kermrc'') and fill it with:
set line /dev/ttyS0
set speed 115200
set carrier-watch off
set handshake none
set flow-control none
robust
set file type bin
set file name lit
set rec pack 1000
set send pack 1000
set window 5
set transmit linefeed on
{{:Serial port selection generalities}}

==Usage==
* To launch it:
<pre class="host>
$ kermit -c
</pre>
* If you get an error message such:
<pre class="host>
/dev/ttyS0
?SET SPEED has no effect without prior SET LINE
</pre>
then recheck that you have read/write rights on the serial port (Typically on Ubuntu: you are not member of "dialout" group).
On OpenSUSE 11.3 you may need to be in "dialout" and 'uucp" groups and give the rights to write in /var/lock:
<pre class="host>
sudo chmod 777 /var/lock
</pre>

* To switch from terminal mode to command mode:
CTRL + \ then c
* To switch from command mode to terminal mode:
C-Kermit>c then ENTER
* To quit:
Switch in command mode
C-Kermit>q then ENTER

== Usefull tips ==

* Download a file via serial in U-Boot :
<pre class="apf">
BIOS> loadb
## Ready for binary (kermit) download to 0xA0000000 at 115200 bps...
</pre>
Then type <Ctrl-\>c and send your file with command :
<pre class="apf">
kermit> send filename
</pre>

==Links==
* http://www.columbia.edu/kermit/ckermit.html