Using Bluetooth FTP Profile Print

 

Bluetooth is widely used when it is necessary to provide a wireless access to the devices located in short distances. In this application note we will show how to organize a wireless FTP access to the NXP i.MX RT1060 EVK running Linux using a USB Bluetooth adapter. In practical embedded applications such a wireless channel may be used to retrieve data collected by the i.MX RT1060 via the standard FTP protocol. The most obvious use case scenario for this need is a technician visiting an embedded device residing at a remote site in order to retrieve data collected and stored locally by the i.MX RT1060 board locally (e.g. the i.MX RT1060 may store data on a EXT2 partition in the SD Card or on a connected USB Flash). Being able to access the i.MX RT1060 over Bluetooth from a notebook or a smartphone, with no need to connect to the i.MX RT1060 with any physical cables, comes in very hand, especially for devices with limited physical access.


Hardware Platform

The hardware platform used in this application note is the NXP i.MX RT1060 EVK board with a USB Bluetooth adapter plugged into the USB OTG 2 J10 connector. The adapter used by Emcraft to perform the tests documented below was based on the LM506 chip. The generic Linux kernel device driver for the USB transport HCI layer (CONFIG_BT_HCIBTUSB) is used in this configuration so other USB Bluetooth adapters should work as described below too.


Software Platform

Support for the Bluetooth FTP server is implemented by the obexftp package:
http://dev.zuckschwerdt.org/openobex/wiki/ObexFtp.

The obexftpd daemon is used to implement the FTP server functionality over Bluetooth. The daemon, once started, waits for connections to the specified port from clients. The obexftp utility is used to implement the FTP client functionality over Bluetooth (this allows to connect to FTP servers running on other Bluetooth devices).

The OBEX FTP protocol is used for store and retrieve files. Support for the OBEX protocol is implemented with the openobex package:
http://dev.zuckschwerdt.org/openobex/wiki/WikiStart.

The functionality described below is available from the rootfs.uImage project provided by Emcraft for the NXP i.MX RT1060 EVK board.


Test Setup

We will use the following terminology below:

  • Target: NXP i.MX RT1060 EVK board with the LM506 Bluetooth adapter plugged into the USB HS port.
    The Bluetooth <Target address> in the examples below is 5C:F3:70:70:FA:D5;
  • Host: Any computer with a Bluetooth interface, running Linux with the Bluetooth tools (bluez-utils, openobex, and obexftp) installed.
    The Bluetooth <Host address> in the examples below is C4:D9:87:8C:B2:24.


Bluetooth FTP Server on i.MX RT1060

Power-on the NXP i.MX RT1060 EVK board and wait for the Linux to boot on the Target. Run the Bluetooth daemons in the background:

...
init started: BusyBox v1.24.2 (2017-10-18 21:56:31 MSK)
/ # hcid -n&
/ # sdpd -n&

Plug-in the Bluetooth adapter to the USB HS interface of the NXP i.MX RT1060 EVK board. Observe the messages similar to the following in the Target console:

usb 1-1: new full-speed USB device number 2 using ci_hdrc
hcid[99]: HCI dev 0 registered
Bluetooth: hci0: BCM: chip id 63
Bluetooth: hci0: BCM20702A
Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
Bluetooth: hci0: BCM20702A1 (001.002.014) build 1338
Bluetooth: hci0: Broadcom Bluetooth Device
hcid[99]: HCI dev 0 up
hcid[99]: Starting security manager 0

Get the <Target address> Bluetooth address of the adapter just plugged-in:

/ # cat /sys/class/bluetooth/hci0/address
5c:f3:70:70:fa:d5

Create a test file in the root/ directory, which will be exported over FTP from the Target:

/ # cd /root/
/root # ln -s /bin/busybox .

Run the FTP server daemon specifying the Bluetooth port to listen upon, and the exported root directory. In the example below the channel number is 2, an FTP root directory is /root:

/ # obexftpd -c /root -b2 &
Waiting for connection...
/ #

List the names of files exported by the Target over Bluetooth by executing the following command on the Host:

[yur@ubuntu rootfs]$ obexftp -b 5c:f3:70:70:fa:d5 -B 2 -l
Connecting..\done
Tried to connect for 66ms
Receiving "(null)"...|<?xml version="1.0"?>
<!DOCTYPE folder-listing SYSTEM "obex-folder-listing.dtd">
<folder-listing version="1.0">
<file name="busybos" size="12" user-perm="RWD" modified="19700101T000041Z" created="19700101T000041Z" accessed="19700101T000041Z" />
</folder-listing>
done
Disconnecting../done

Download the test file from the Target over Bluetooth by executing the following commands on the Host:

[yur@ubuntu rootfs]$ obexftp -b 5c:f3:70:70:fa:d5 -B 2 -g busybox
Connecting..\done
Tried to connect for 39ms
Receiving "busybox"...|done
Disconnecting..\done

[yur@ubuntu rootfs]$ ls -l busybox
-rw-r--r-- 1 void void 366572 2017-10-18 23:45 busybox

Upload the test file to the Target over Bluetooth by executing the following commands on the Host:

[yur@ubuntu rootfs]$ dd if=/dev/zero of=512kB.host bs=1024 count=512
[yur@ubuntu rootfs]$ obexftp -b 5c:f3:70:70:fa:d5 -B 2 -p 512kB.host
Connecting..\done
Tried to connect for 90ms
Sending "512kB.host"...|done
Disconnecting../done

Validate the uploaded file:

/root # ls -lt /root
-rw-r--r--        1 root     root        524288 Jan  1 00:04 512kB.host
lrwxrwxrwx    1 root     root                12 Jan  1 00:00 busybox -> /bin/busybox


Bluetooth FTP Client on i.MX RT1060

The Target may also implement the FTP Client functionality and connect to the FTP servers exported over Bluetooth by other devices. The obexftp utility is integrated into the rootfs project and may be used for this purpose. See the commands executed on the Host above in this application note: similar commands may be run on the Target side if we want it to perform the FTP Client role.