Manually using GSM

From Openmoko

Revision as of 08:40, 2 August 2007 by Shadowjack (Talk | contribs)

Jump to: navigation, search

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

Thankfully, this may now be partially obsolete. The dialer now works!

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

Connecting to GSM Modem

  • 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
  • enable CTS/RTS flow control
root@fic-gta01:~$ stty -F /dev/ttySAC0 crtscts
  • access the GSM Modem UART
root@fic-gta01:~$ cu -l /dev/ttySAC0
Connected.
AT-Command Interpreter Ready
OK

If it will hang on "Connected" message then probably your device has nonworking GSM modem - check Bug #256

cu seems to have problems with the hardware flow control. The one way I always managed to get GSM working is to start cu first and then on a different console issue the stty command. --DanielWillmann 01:15, 20 March 2007 (CET)

Using it manually

Registering with the Network

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

Answering an incoming call

RING
ATA
OK

Dialling an outgoing call

To actually be able to talk you have to configure your audio accordingly

root@fic-gta01:~$ cd /etc/alsa/
root@fic-gta01:/etc/alsa$ wget http://opensource.wolfsonmicro.com/~gg/neo1973/gsmheadset.working.state
root@fic-gta01:/etc/alsa$ alsactl -f /etc/alsa/gsmheadset.working.state restore

Up the "Amp right" volume to hear the speaker on both ears, then dial

ATD012340234;   

If you get NO CARRIER, try...

ATD+xxyzzzzzzz

ie, ATD+<country_code><area_code><phone_number>

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

Using tui

Tui (available from www.sf.net/projects/tui) is able to do all this. It is still text-based, but input-rxvt can take data from touchscreen, so you can actually do the calls using your finger. It also plays wav file on incoming call, so it is theoretically usable. It even does caller id.

Manually using GPRS

See Manually using GPRS

Personal tools

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

Thankfully, this may now be partially obsolete. The dialer now works!

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

Connecting to GSM Modem

  • 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
  • enable CTS/RTS flow control
root@fic-gta01:~$ stty -F /dev/ttySAC0 crtscts
  • access the GSM Modem UART
root@fic-gta01:~$ cu -l /dev/ttySAC0
Connected.
AT-Command Interpreter Ready
OK

If it will hang on "Connected" message then probably your device has nonworking GSM modem - check Bug #256

cu seems to have problems with the hardware flow control. The one way I always managed to get GSM working is to start cu first and then on a different console issue the stty command. --DanielWillmann 01:15, 20 March 2007 (CET)

Using it manually

Registering with the Network

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

Answering an incoming call

RING
ATA
OK

Dialling an outgoing call

To actually be able to talk you have to configure your audio accordingly

root@fic-gta01:~$ cd /etc/alsa/
root@fic-gta01:/etc/alsa$ wget http://opensource.wolfsonmicro.com/~gg/neo1973/gsmheadset.working.state
root@fic-gta01:/etc/alsa$ alsactl -f /etc/alsa/gsmheadset.working.state restore

Up the "Amp right" volume to hear the speaker on both ears, then dial

ATD012340234;   

If you get NO CARRIER, try...

ATD+xxyzzzzzzz

ie, ATD+<country_code><area_code><phone_number>

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

Using tui

Tui (available from www.sf.net/projects/tui) is able to do all this. It is still text-based, but input-rxvt can take data from touchscreen, so you can actually do the calls using your finger. It also plays wav file on incoming call, so it is theoretically usable. It even does caller id.

Manually using GPRS

See Manually using GPRS