Manually using GSM

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(Added link to the AT commands page)
m (Reducing the loglevel)
Line 21: Line 21:
  
 
=== Reducing the loglevel ===
 
=== 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 <code>dmesg -n1</code>.
 
To keep the kernel from writing to /dev/ttySAC0, you need to use <code>dmesg -n1</code>.

Revision as of 00:31, 9 March 2007

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: {{{1}}}


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

Powering up the GSM Modem

  • load the "gta01_pm_gsm.ko" kernel module
root@fic-gta01:~$ modprobe gta01_pm_gsm
  • 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

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
Personal tools

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

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

Powering up the GSM Modem

  • load the "gta01_pm_gsm.ko" kernel module
root@fic-gta01:~$ modprobe gta01_pm_gsm
  • 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

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