...

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 RT1050 EVK /RT1060 EVKB 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 RT1050 RT10XX 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 RT1050 RT10XX board locally (e.g. the i.MX RT1050 RT10XX may store data on a EXT2 partition in the SD Card or on a connected USB Flash). Being able to access the i.MX RT1050 RT10XX over Bluetooth from a notebook or a smartphone, with no need to connect to the i.MX RT1050 RT10XX with any physical cables, comes in very hand, especially for devices with limited physical access.

1. Hardware Platform

The hardware platform used in this application note is the NXP i.MX RT1050 EVK EVKB board with a USB Bluetooth adapter plugged into the USB 2 J9 connector or the NXP i.MX RT1060 EVKB board with a USB Bluetooth adapter plugged into the USB 2 J10 J47 connector. 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.

2. Software Platform

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

...

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

3. Test Setup

We will use the following terminology below:

• Target: NXP i.MX RT1050 EVK /RT1060 EVKB board with the Bluetooth adapter plugged into the USB HS port.
  The Bluetooth <Target address> in the examples below is 04:7F:0E:31:B7:94;

• 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 BC30:7703:37C8:5CC9:3210:57E6.

4. Bluetooth FTP Server on i.MX

...

RT10XX

1. Power-on the NXP i.MX RT1050

...

1. /RT1060 EVKB board and wait for the Linux to boot on the

...

1. target. Run the Bluetooth daemons in the background:

   Code Block
   ... / # hcid -n& hcid[96]: Bluetooth HCI daemon / # sdpd -n& [2] 97 sdpd -n

2. Plug-in the Bluetooth adapter to the USB HS interface of the NXP i.MX RT1050

...

1. /RT1060 EVKB board. Observe the messages similar to the following in the

...

1. target console:

   Code Block

...

1. ci_hdrc ci_hdrc.0: EHCI Host Controller ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 2 ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00 hub 2-0:1.0: USB hub found hub 2-0:1.0: 1 port detected usb 2-1: new full-speed USB device number 2 using ci_hdrc usb

...

1. 2-1: Duplicate descriptor for config 1 interface 1 altsetting 5, skipping

...

1. Bluetooth: hci0: CSR: Setting up dongle with HCI ver=9 rev=0001 Bluetooth: hci0: LMP ver=9 subver=0001; manufacturer=2279 Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once... Bluetooth: hci0: CSR:

...

1. Couldn't

...

1. suspend the device for our Barrot 8041a02 receive-issue workaround Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported. Bluetooth:

...

1. hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported. Bluetooth: hci0: HCI Set Event Filter command not supported. hcid[74]: HCI dev 0 registered hcid[74]: HCI dev 0 up hcid[

...

1. 80]: Can't set encrypt on hci0: Invalid request code (56) hcid[

...

1. 74]: Starting security manager 0

2. Get the

...

1. <target address> Bluetooth address of the adapter just plugged-in:

   Code Block
   / # hcitool dev Devices: hci0 04:7F:0E:31:B7:94 / #

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

...

1. target:

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

2. 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:

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

3. List the names of files exported by the

...

1. target over Bluetooth by executing the following command on the

...

1. host:

   Code Block
   $ sudo obexftp -b 04:7F:0E:31:B7:94 -B 2 -l Connecting..\done

...

1. Receiving "(null)"...|<?xml version="1.0"?> <!DOCTYPE folder-listing SYSTEM "obex-folder-listing.dtd"> <folder-listing version="1.0"> <file name="busybox" size="12" user-perm="RWD" modified="

...

1. 19700101T001051Z" created="

...

1. 19700101T001051Z" accessed="

...

1. 19700101T001051Z" /> </folder-listing> done Disconnecting../done

2. Download the test file from the

...

1. target over Bluetooth by executing the following commands on the

...

1. host:

   Code Block
   $ sudo obexftp -b 04:7F:0E:31:B7:94 -B 2 -g busybox Connecting..\done Receiving "busybox"...-done Disconnecting..\done $ $ ls -l busybox -rw-r--r-- 1 root root 377384 окт 12 15:49 busybox

2. Upload the test file to the

...

1. target over Bluetooth by executing the following commands on the

...

1. host:

   Code Block
   $ dd if=/dev/zero of=512kB.host bs=1024 count=512 512+0 records in 512+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0,00793397 s, 66,1 MB/s $ sudo obexftp -b 04:7F:0E:31:B7:94 -B 2 -p 512kB.host Connecting..\done Sending "512kB.host"...|done Disconnecting../done

2. Validate the uploaded file on the target:

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

5. Bluetooth

...

FTP Client on i.MX

...

RT10XX

The Target 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 target side if we want it to perform the FTP Client role.