Difference between revisions of "CM-QS600: Linux: Debian"

From Compulab Mediawiki
Jump to: navigation, search
(Overview)
(Audio)
Line 30: Line 30:
  
 
=== kernel ===
 
=== kernel ===
* {{filename|zImage-3.4.0-14.09-cm-qs600-2.bin}} - pre-built Linux kernel version 3.4.0-14.09-cm-qs600-2 for CM-QS600
+
* {{filename|zImage-3.4.0-14.10-cm-qs600-3.bin}} - pre-built Linux kernel version 3.4.0-14.10-cm-qs600-3 for CM-QS600
* {{filename|linux-3.4.0-14.09-cm-qs600-2.config}} - Linux kernel 3.4.0-14.09-cm-qs600-2 configuration file
+
* {{filename|modules-3.4.0-14.10-cm-qs600-3.tar.bz2}} - a modules tarball, that matches the ready to run Linux kernel ({{filename|zImage-3.4.0-14.10-cm-qs600-3.bin}})
* {{filename|linux-3.4.0-14.09-cm-qs600-2.patch}} - patch vs. [https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/tag/refs/tags/ubuntu-ifc6410-14.09 ubuntu-ifc6410-14.09] tag with support for CM-QS600 peripherals
+
* {{filename|linux-3.4.0-14.10-cm-qs600-3.config}} - Linux kernel 3.4.0-14.10-cm-qs600-3 configuration file
* {{filename|patches}} - ordered collection of patches, that form the single patch above ({{filename|linux-3.4.0-14.09-cm-qs600-2.patch}})
+
* {{filename|linux-3.4.0-14.10-cm-qs600-3.patch}} - patch vs. [https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/tag/refs/tags/ubuntu-ifc6410-14.10 ubuntu-ifc6410-14.10] tag with support for CM-QS600 peripherals
 +
* {{filename|patches}} - ordered collection of patches, that form the single patch above ({{filename|linux-3.4.0-14.10-cm-qs600-3.patch}})
  
 
=== utilities ===
 
=== utilities ===
Line 54: Line 55:
 
Regular user account:
 
Regular user account:
 
<pre>
 
<pre>
cm-debian login: user
+
cm-debian login: user
 
Password: 111111
 
Password: 111111
 
</pre>
 
</pre>
Line 66: Line 67:
  
 
Debian Linux image for CM-QS600 includes all the information required to use Debian package management utilities. You can use [http://linux.die.net/man/8/apt-get apt-get] and [http://www.wlug.org.nz/dpkg(8) dpkg] out of the box.
 
Debian Linux image for CM-QS600 includes all the information required to use Debian package management utilities. You can use [http://linux.die.net/man/8/apt-get apt-get] and [http://www.wlug.org.nz/dpkg(8) dpkg] out of the box.
 +
 +
=== Audio ===
 +
 +
CM-QS600 provides an analog and a digital HDMI audio interfaces. The audio configuration can be set using [http://www.alsa-project.org/main/index.php/Use_Case_Manager ALSA UCM] command line tool. Proper UCM profile configuration files are available in the image in the folder {{filename|/usr/share/alsa/ucm/apq8064-tabla-snd-card/}}.
 +
* To enable analog output run the following command:
 +
<pre>
 +
root@cm-debian:~# alsaucm -c apq8064-tabla-snd-card set _verb HiFi set _enadev Headphones
 +
</pre>
 +
* To enable HDMI output run the following command:
 +
<pre>
 +
root@cm-debian:~# alsaucm -c apq8064-tabla-snd-card set _verb HDMI set _enadev HDMI-stereo
 +
</pre>
 +
* To play back an audio file launch {{filename|aplay}} playback tool:
 +
<pre>
 +
root@cm-debian:~# aplay <audio-file.wav>
 +
</pre>
 +
 +
=== Bluetooth ===
 +
 +
CM-QS600 features Bluetooth 4.0 interface. Following sections describe the initialization and simple use cases of Bluetooth device.
 +
 +
==== Host Controller Interface (HCI) Initialization ====
 +
 +
* Attach the ttyHS0 serial port to the HCI Bluetooth subsystem:
 +
<pre>
 +
root@cm-debian:~# hciattach -s 115200 /dev/ttyHS0 ath3k 3000000
 +
Device setup complete
 +
</pre>
 +
* Run HCI device configuration utility to retrieve detailed information about the Bluetooth device:
 +
<pre>
 +
root@cm-debian:~# hciconfig -a
 +
hci0:  Type: BR/EDR  Bus: UART
 +
        BD Address: 00:3C:7F:F0:F0:0A  ACL MTU: 1021:8  SCO MTU: 124:0
 +
        UP RUNNING PSCAN
 +
        RX bytes:1153 acl:0 sco:0 events:37 errors:0
 +
        TX bytes:927 acl:0 sco:0 commands:37 errors:0
 +
        Features: 0xff 0xfe 0x0d 0xfe 0x98 0x7f 0x79 0x87
 +
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
 +
        Link policy: RSWITCH HOLD SNIFF
 +
        Link mode: SLAVE ACCEPT
 +
        Name: 'cm-debian-0'
 +
        Class: 0x6e0100
 +
        Service Classes: Networking, Rendering, Capturing, Audio, Telephony
 +
        Device Class: Computer, Uncategorized
 +
        HCI Version: 3.0 (0x5)  Revision: 0x102
 +
        LMP Version: 3.0 (0x5)  Subversion: 0x0
 +
        Manufacturer: Atheros Communications, Inc. (69)
 +
</pre>
 +
 +
==== A2DP Headphones ====
 +
* Scan for available devices to find out Headphones BT device address:
 +
<pre>
 +
root@cm-debian:~# hcitool scan
 +
Scanning ...
 +
00:07:A4:F2:B3:CB Motorola HT820
 +
root@cm-debian:~#
 +
</pre>
 +
 +
* Add new PCM device by editing {{filename|/etc/asound.conf}}:
 +
 +
<pre>
 +
pcm.btheadphones {
 +
  type plug
 +
  slave {
 +
      pcm {
 +
          type bluetooth
 +
          device 00:07:A4:F2:B3:CB
 +
          profile "auto"
 +
      }
 +
  }
 +
  hint {
 +
      show on
 +
      description "BT Headphones"
 +
  }
 +
}
 +
ctl.btheadphones {
 +
  type bluetooth
 +
}
 +
</pre>
 +
 +
* List device names to ensure correct settings in {{filename|/etc/asound.conf}}:
 +
<pre>
 +
root@cm-debian:~# aplay -L
 +
null
 +
    Discard all samples (playback) or generate zero samples (capture)
 +
btheadphones
 +
    BT Headphones
 +
default:CARD=apq8064tablasnd
 +
    apq8064-tabla-snd-card,
 +
    Default Audio Device
 +
sysdefault:CARD=apq8064tablasnd
 +
    apq8064-tabla-snd-card,
 +
    Default Audio Device
 +
</pre>
 +
 +
* Put the headphones in the pairing mode and launch {{filename|bluez-simple-agent}} application and provide device PIN code on request:
 +
<pre>
 +
root@cm-debian:~# bluez-simple-agent hci0 00:07:A4:F2:B3:CB
 +
RequestPinCode (/org/bluez/2101/hci0/dev_00_07_A4_F2_B3_CB)
 +
Enter PIN Code: 0000
 +
Release
 +
New device (/org/bluez/2101/hci0/dev_00_07_A4_F2_B3_CB)
 +
</pre>
 +
 +
* Launch {{filename|aplay}} playback tool:
 +
<pre>
 +
root@cm-debian:~# aplay -D btheadphones <audio-file.wav>
 +
</pre>
 +
 +
==== Obex FTP service ====
 +
 +
The OBject EXchange protocol (OBEX) can be used to exchange all kind of objects like files, pictures, calendar entries (vCal) and business cards (vCard) over bluetooth, IrDA, USB and serial cable links.
 +
CM-QS600 Linux example root file system contains file transfer utility for devices that use the OBEX protocol. Following examples demonstrate its usage with an Android device (phone).
 +
* Install [https://play.google.com/store/apps/details?id=it.medieval.blueftp&hl=en Bluetooth File Transfer] application via Google Play.
 +
* Enable bluetooth on the phone. On CM-QS600, scan for available devices to find out phone's BT address:
 +
<pre>
 +
root@cm-debian:~# hcitool scan
 +
Scanning ...
 +
        BC:F5:AC:53:15:60      Nexus 5
 +
</pre>
 +
* Ensure the phone supports Obex FTP service:
 +
<pre>
 +
root@cm-debian:~# sdptool search FTP
 +
Inquiring ...
 +
Searching for FTP on BC:F5:AC:53:15:60 ...
 +
Service Name: OBEX FTP
 +
Service RecHandle: 0x1000b
 +
Service Class ID List:
 +
  UUID 128: 00001106-0000-1000-8000-00805f9b34fb
 +
Protocol Descriptor List:
 +
  "L2CAP" (0x0100)
 +
  "RFCOMM" (0x0003)
 +
    Channel: 4
 +
</pre>
 +
* Do NOT pair CM-QS600 and Android device explicitly.
 +
* Transfer a file from CM-QS600 to the phone. Confirm device pairing on the phone if required:
 +
<pre>
 +
root@cm-debian:~# obexftp -b BC:F5:AC:53:15:60 --put testfile.txt
 +
Browsing BC:F5:AC:53:15:60 ...
 +
Connecting..\done
 +
Tried to connect for 1044ms
 +
Sending "testfile.jpg"...|done
 +
Disconnecting../done
 +
</pre>
 +
* List a content of a {{filename|Pictures}} directory on the phone:
 +
<pre>
 +
root@cm-debian:~# obexftp -b BC:F5:AC:53:15:60 --list Pictures
 +
Browsing BC:F5:AC:53:15:60 ...
 +
Connecting..\done
 +
Tried to connect for 23ms
 +
Receiving "Pictures".../<?xml version="1.0" encoding="utf-8"?>
 +
<!DOCTYPE folder-listing SYSTEM "obex-folder-listing.dtd">
 +
<folder-listing version="1.0">
 +
  <folder name="cache" size="4096" modified="20141026T185556" user-perm="RWD" />
 +
  <file name="testpicture.jpeg" size="161335" modified="20141128T104723" user-perm="RWD" />
 +
</folder-listing>done
 +
Disconnecting..-done
 +
</pre>
 +
* Transfer a file from the phone to CM-QS600. Confirm device pairing on the phone if required:
 +
<pre>
 +
root@cm-debian:~# obexftp -b BC:F5:AC:53:15:60 -g Pictures/testpicture.jpeg
 +
Browsing BC:F5:AC:53:15:60 ...
 +
Connecting..\done
 +
Tried to connect for 24ms
 +
Receiving "Pictures/testpicture.jpeg"... Sending "Pictures"...|done
 +
-done
 +
Disconnecting..\done
 +
</pre>
 +
 +
=== WLAN ===
 +
 +
CM-QS600 features 802.11b/g/n wireless interface, implemented with the Atheros QCA6234 Wireless module.
 +
 +
==== WLAN Initialization ====
 +
* The ath6kl WLAN driver gets loaded automatically. Make sure that the WLAN driver is loaded:
 +
<pre>
 +
root@cm-debian:~# lsmod | grep ath6kl_sdio
 +
ath6kl_sdio          320500  0
 +
cfg80211              184104  1 ath6kl_sdio
 +
</pre>
 +
If the WLAN driver has not been loaded automatically, it can be loaded manually:
 +
<pre>
 +
root@cm-debian:~# modprobe ath6kl_sdio 
 +
</pre>
 +
* {{cmd|iwconfig}} command from {{cmd|wireless-tools}} packge can be used to retrieve detailed information about WLAN interfaces:
 +
<pre>
 +
root@cm-debian:~# iwconfig wlan0
 +
wlan0    IEEE 802.11abgn  ESSID:off/any 
 +
          Mode:Managed  Access Point: Not-Associated 
 +
          Retry  long limit:7  RTS thr:off  Fragment thr:off
 +
          Encryption key:off
 +
          Power Management:off
 +
</pre>
 +
* WLAN interface activating:
 +
<pre>
 +
root@cm-debian:~# ifconfig wlan0 up
 +
</pre>
 +
* Sample WLAN scanning:
 +
<pre>
 +
root@cm-debian:~# iwlist wlan0 scan
 +
</pre>
 +
The output will show the list of Access Points and Ad-Hoc cells in range.
 +
For more information about connecting to wireless networks and tunning WLAN interfaces refer to “wpa_supplicant” and “wireless-tools” man pages.
  
 
== See also ==
 
== See also ==

Revision as of 07:25, 26 December 2014

Overview

The CompuLab CM-QS600 System-on-Module / Computer-on-Module Linux kernel is based on the Snapdragon 600 Linux Platform Ubuntu-based 14.09 release by Linaro. The example run-time Linux filesystem image for CM-QS600 is based on Debian GNU/Linux Wheezy. The CompuLab Linux package for CM-QS600 includes ready to run root filesystem demo archive, Linux kernel configuration and source code patches.

The default Debian Wheezy Linux image includes more than 400 software packages. Among them:

  • Core system
  • Debian package management system
  • X11 Windowing System
  • Fluxbox desktop manager
  • Iceweasel browser
  • Samba connectivity suite
  • SSH server and client
  • ALSA configuration and usage utilities
  • Bluetooth tools and daemons

The CM-QS600: Linux: Getting started page provides a brief introduction on how to install the run-time Linux image.

Package contents

version.txt

The contents of the version.txt identifies the package version.

images

  • boot-cm-qs600.img - boot image based on Linux kernel image binary for CM-QS600
  • bootramfs-cm-qs600.img - boot image based on Linux kernel image binary for CM-QS600 and initramfs required for installation images onto the eMMC
  • debian-image.tar.bz2 - archive of the Debian root file system
  • zImage-cm-qs600 - ready to run Linux kernel image binary for CM-QS600

kernel

  • zImage-3.4.0-14.10-cm-qs600-3.bin - pre-built Linux kernel version 3.4.0-14.10-cm-qs600-3 for CM-QS600
  • modules-3.4.0-14.10-cm-qs600-3.tar.bz2 - a modules tarball, that matches the ready to run Linux kernel (zImage-3.4.0-14.10-cm-qs600-3.bin)
  • linux-3.4.0-14.10-cm-qs600-3.config - Linux kernel 3.4.0-14.10-cm-qs600-3 configuration file
  • linux-3.4.0-14.10-cm-qs600-3.patch - patch vs. ubuntu-ifc6410-14.10 tag with support for CM-QS600 peripherals
  • patches - ordered collection of patches, that form the single patch above (linux-3.4.0-14.10-cm-qs600-3.patch)

utilities

The utilities directory contains miscellaneous utilities useful for development

  • mkbootimg - prebuilt mkbootimg utility binary


Using Debian Linux on CM-QS600

Connection and Logging In

Use the following username and password to login:

Account with administrative privileges:

cm-debian login: root
Password: 111111

Regular user account:

cm-debian login: user
Password: 111111

To login into the Linux system, you may use a serial console (ttyHSL0) at 115200 bps, or connect through the network, or use a keyboard and HDMI display.

Networking

To configure networking, edit /etc/network/interfaces, /etc/resolv.conf, /etc/hostname and /etc/hosts. For more information about Debian Linux network configuration read Network setup chapter in the Debian Reference.

Software Management

Debian Linux image for CM-QS600 includes all the information required to use Debian package management utilities. You can use apt-get and dpkg out of the box.

Audio

CM-QS600 provides an analog and a digital HDMI audio interfaces. The audio configuration can be set using ALSA UCM command line tool. Proper UCM profile configuration files are available in the image in the folder /usr/share/alsa/ucm/apq8064-tabla-snd-card/.

  • To enable analog output run the following command:
root@cm-debian:~# alsaucm -c apq8064-tabla-snd-card set _verb HiFi set _enadev Headphones
  • To enable HDMI output run the following command:
root@cm-debian:~# alsaucm -c apq8064-tabla-snd-card set _verb HDMI set _enadev HDMI-stereo
  • To play back an audio file launch aplay playback tool:
root@cm-debian:~# aplay <audio-file.wav>

Bluetooth

CM-QS600 features Bluetooth 4.0 interface. Following sections describe the initialization and simple use cases of Bluetooth device.

Host Controller Interface (HCI) Initialization

  • Attach the ttyHS0 serial port to the HCI Bluetooth subsystem:
root@cm-debian:~# hciattach -s 115200 /dev/ttyHS0 ath3k 3000000
Device setup complete
  • Run HCI device configuration utility to retrieve detailed information about the Bluetooth device:
root@cm-debian:~# hciconfig -a
hci0:   Type: BR/EDR  Bus: UART
        BD Address: 00:3C:7F:F0:F0:0A  ACL MTU: 1021:8  SCO MTU: 124:0
        UP RUNNING PSCAN 
        RX bytes:1153 acl:0 sco:0 events:37 errors:0
        TX bytes:927 acl:0 sco:0 commands:37 errors:0
        Features: 0xff 0xfe 0x0d 0xfe 0x98 0x7f 0x79 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH HOLD SNIFF 
        Link mode: SLAVE ACCEPT 
        Name: 'cm-debian-0'
        Class: 0x6e0100
        Service Classes: Networking, Rendering, Capturing, Audio, Telephony
        Device Class: Computer, Uncategorized
        HCI Version: 3.0 (0x5)  Revision: 0x102
        LMP Version: 3.0 (0x5)  Subversion: 0x0
        Manufacturer: Atheros Communications, Inc. (69)

A2DP Headphones

  • Scan for available devices to find out Headphones BT device address:
root@cm-debian:~# hcitool scan
Scanning ...
	00:07:A4:F2:B3:CB	Motorola HT820
root@cm-debian:~#
  • Add new PCM device by editing /etc/asound.conf:
pcm.btheadphones {
   type plug
   slave {
       pcm {
           type bluetooth
           device 00:07:A4:F2:B3:CB
           profile "auto"
       }
   }
   hint {
       show on
       description "BT Headphones"
   }
}
ctl.btheadphones {
  type bluetooth
}
  • List device names to ensure correct settings in /etc/asound.conf:
root@cm-debian:~# aplay -L
null
    Discard all samples (playback) or generate zero samples (capture)
btheadphones
    BT Headphones
default:CARD=apq8064tablasnd
    apq8064-tabla-snd-card, 
    Default Audio Device
sysdefault:CARD=apq8064tablasnd
    apq8064-tabla-snd-card, 
    Default Audio Device
  • Put the headphones in the pairing mode and launch bluez-simple-agent application and provide device PIN code on request:
root@cm-debian:~# bluez-simple-agent hci0 00:07:A4:F2:B3:CB 
RequestPinCode (/org/bluez/2101/hci0/dev_00_07_A4_F2_B3_CB)
Enter PIN Code: 0000
Release
New device (/org/bluez/2101/hci0/dev_00_07_A4_F2_B3_CB)
  • Launch aplay playback tool:
root@cm-debian:~# aplay -D btheadphones <audio-file.wav>

Obex FTP service

The OBject EXchange protocol (OBEX) can be used to exchange all kind of objects like files, pictures, calendar entries (vCal) and business cards (vCard) over bluetooth, IrDA, USB and serial cable links. CM-QS600 Linux example root file system contains file transfer utility for devices that use the OBEX protocol. Following examples demonstrate its usage with an Android device (phone).

  • Install Bluetooth File Transfer application via Google Play.
  • Enable bluetooth on the phone. On CM-QS600, scan for available devices to find out phone's BT address:
root@cm-debian:~# hcitool scan
Scanning ...
        BC:F5:AC:53:15:60       Nexus 5
  • Ensure the phone supports Obex FTP service:
root@cm-debian:~# sdptool search FTP
Inquiring ...
Searching for FTP on BC:F5:AC:53:15:60 ...
Service Name: OBEX FTP
Service RecHandle: 0x1000b
Service Class ID List:
  UUID 128: 00001106-0000-1000-8000-00805f9b34fb
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 4
  • Do NOT pair CM-QS600 and Android device explicitly.
  • Transfer a file from CM-QS600 to the phone. Confirm device pairing on the phone if required:
root@cm-debian:~# obexftp -b BC:F5:AC:53:15:60 --put testfile.txt 
Browsing BC:F5:AC:53:15:60 ...
Connecting..\done
Tried to connect for 1044ms
Sending "testfile.jpg"...|done
Disconnecting../done
  • List a content of a Pictures directory on the phone:
root@cm-debian:~# obexftp -b BC:F5:AC:53:15:60 --list Pictures
Browsing BC:F5:AC:53:15:60 ...
Connecting..\done
Tried to connect for 23ms
Receiving "Pictures".../<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE folder-listing SYSTEM "obex-folder-listing.dtd">
<folder-listing version="1.0">
  <folder name="cache" size="4096" modified="20141026T185556" user-perm="RWD" />
  <file name="testpicture.jpeg" size="161335" modified="20141128T104723" user-perm="RWD" />
</folder-listing>done
Disconnecting..-done
  • Transfer a file from the phone to CM-QS600. Confirm device pairing on the phone if required:
root@cm-debian:~# obexftp -b BC:F5:AC:53:15:60 -g Pictures/testpicture.jpeg
Browsing BC:F5:AC:53:15:60 ...
Connecting..\done
Tried to connect for 24ms
Receiving "Pictures/testpicture.jpeg"... Sending "Pictures"...|done
-done
Disconnecting..\done

WLAN

CM-QS600 features 802.11b/g/n wireless interface, implemented with the Atheros QCA6234 Wireless module.

WLAN Initialization

  • The ath6kl WLAN driver gets loaded automatically. Make sure that the WLAN driver is loaded:
root@cm-debian:~# lsmod | grep ath6kl_sdio
ath6kl_sdio           320500  0
cfg80211              184104  1 ath6kl_sdio

If the WLAN driver has not been loaded automatically, it can be loaded manually:

root@cm-debian:~# modprobe ath6kl_sdio   
  • iwconfig command from wireless-tools packge can be used to retrieve detailed information about WLAN interfaces:
root@cm-debian:~# iwconfig wlan0
wlan0     IEEE 802.11abgn  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
  • WLAN interface activating:
root@cm-debian:~# ifconfig wlan0 up
  • Sample WLAN scanning:
root@cm-debian:~# iwlist wlan0 scan

The output will show the list of Access Points and Ad-Hoc cells in range. For more information about connecting to wireless networks and tunning WLAN interfaces refer to “wpa_supplicant” and “wireless-tools” man pages.

See also