Manually using GSM

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(Powering up the GSM Modem)
m (add notice to gsmd/libgsmd-util)
Line 1: Line 1:
 +
'''When men were real men and typed their own AT commands...'''
  
 
This is a short guide how to manually get GSM going.
 
This is a short guide how to manually get GSM going.
Line 6: Line 7:
 
* GTA01Bv2 or GTA01Bv3 with very recent u-boot bootloader, providing usbtty (serial over USB) support)
 
* GTA01Bv2 or GTA01Bv3 with very recent u-boot bootloader, providing usbtty (serial over USB) support)
 
* Do not connect any debug board!
 
* Do not connect any debug board!
 
  
 
== Walk-Through ==
 
== Walk-Through ==
Line 44: Line 44:
 
  OK
 
  OK
  
=== Registering with the Network ===
+
=== Using it manually ===
 +
==== Registering with the Network ====
  
 
* enter the following [[Hardware:AT_Commands]]:
 
* enter the following [[Hardware:AT_Commands]]:
Line 58: Line 59:
 
</pre>
 
</pre>
  
=== Anwering an incoming call ===
+
==== Anwering an incoming call ====
 
<pre>
 
<pre>
 
RING
 
RING
Line 65: Line 66:
 
</pre>
 
</pre>
  
=== Dialling an outgoing call ===
+
==== Dialling an outgoing call ====
  
 
<pre>
 
<pre>
Line 71: Line 72:
 
</pre>
 
</pre>
  
=== Hanging up ===
+
==== Hanging up ====
 
<pre>
 
<pre>
 
ATH
 
ATH
 
OK
 
OK
 
</pre>
 
</pre>
 +
 +
=== Using [[gsmd]] ===
 +
 +
You can use the [[gsmd]] and [[libgsmd-util]] programs to have a slightly more high-level interface to the GSM Modem.  It's still console based, though.
 +
 +
For further instructions, see [[gsmd]]

Revision as of 01:37, 9 March 2007

When men were real men and typed their own AT commands...

This is a short guide how to manually get GSM going.

Contents

Requirements

  • GTA01Bv2 or GTA01Bv3 with very recent u-boot bootloader, providing usbtty (serial over USB) support)
  • Do not connect any debug board!

Walk-Through

Booting the system

  • Make sure the rootfs you use has 'auto usb0' in /etc/network/interfaces
  • Configure the host's usb0 interface to 192.168.0.200 netmask 255.255.255.0
  • ssh to root@192.168.0.201

Disabling the getty

Our default images all have a getty running on /dev/ttySAC0, please edit /etc/inittab and disable the getty on that port

Reducing the loglevel

NOTE: You don't need this in kernel builds with patchset ≥ 1288


To keep the kernel from writing to /dev/ttySAC0, you need to use dmesg -n1.

Powering up the GSM Modem

  • verify there is no getty or any other app running on /dev/ttySAC0
root@fic-gta01:~$ lsof | grep ttySAC0
  • power-up the GSM Modem
root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on
  • change permissions on ttySAC0
root@fic-gta01:~$ chown uucp.uucp /dev/ttySAC0
  • setup /usr/spool/uucp
root@fic-gta01:~$ mkdir /usr/spool
root@fic-gta01:~$ mkdir /usr/spool/uucp
root@fic-gta01:~$ chown uucp.uucp /usr/spool/uucp
  • access the GSM Modem UART
root@fic-gta01:~$ cu -l /dev/ttySAC0
Connected.
AT-Command Interpreter Ready
OK

Using it manually

Registering with the Network

ATE1
OK
AT+CFUN=1
ERROR
AT+CPIN="...."
OK
AT+COPS
OK

Anwering an incoming call

RING
ATA
OK

Dialling an outgoing call

ATD012340234;

Hanging up

ATH
OK

Using gsmd

You can use the gsmd and libgsmd-util programs to have a slightly more high-level interface to the GSM Modem. It's still console based, though.

For further instructions, see gsmd

Personal tools

When men were real men and typed their own AT commands...

This is a short guide how to manually get GSM going.

Requirements

  • GTA01Bv2 or GTA01Bv3 with very recent u-boot bootloader, providing usbtty (serial over USB) support)
  • Do not connect any debug board!

Walk-Through

Booting the system

  • Make sure the rootfs you use has 'auto usb0' in /etc/network/interfaces
  • Configure the host's usb0 interface to 192.168.0.200 netmask 255.255.255.0
  • ssh to root@192.168.0.201

Disabling the getty

Our default images all have a getty running on /dev/ttySAC0, please edit /etc/inittab and disable the getty on that port

Reducing the loglevel

NOTE: You don't need this in kernel builds with patchset ≥ 1288


To keep the kernel from writing to /dev/ttySAC0, you need to use dmesg -n1.

Powering up the GSM Modem

  • verify there is no getty or any other app running on /dev/ttySAC0
root@fic-gta01:~$ lsof | grep ttySAC0
  • power-up the GSM Modem
root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on
  • change permissions on ttySAC0
root@fic-gta01:~$ chown uucp.uucp /dev/ttySAC0
  • setup /usr/spool/uucp
root@fic-gta01:~$ mkdir /usr/spool
root@fic-gta01:~$ mkdir /usr/spool/uucp
root@fic-gta01:~$ chown uucp.uucp /usr/spool/uucp
  • access the GSM Modem UART
root@fic-gta01:~$ cu -l /dev/ttySAC0
Connected.
AT-Command Interpreter Ready
OK

Using it manually

Registering with the Network

ATE1
OK
AT+CFUN=1
ERROR
AT+CPIN="...."
OK
AT+COPS
OK

Anwering an incoming call

RING
ATA
OK

Dialling an outgoing call

ATD012340234;

Hanging up

ATH
OK

Using gsmd

You can use the gsmd and libgsmd-util programs to have a slightly more high-level interface to the GSM Modem. It's still console based, though.

For further instructions, see gsmd