L-Tek FF1705

The L-Tek FF1705 platform is based on the low cost, low power MultiConnect® xDot™ Module from MultiTech, complete with an integrated DAPLink interface, all in an Arduino form factor

Overview

The L-Tek FF1705 is a development platform for the MultiConnect® xDot™, an ARM® mbed™ programmable, low-power RF module, that provides long-range, low bit rate M2M data connectivity to sensors, industrial equipment and remote appliances.

Conveniently integrated with a DAPLink programming and debug interface, and complete with Arduino compatible headers, this platform can be used to prototype applications using a wide range of IO boards and peripherals supported by mbed in the the mbed Component library.

Additionally, this platform can be used as a shield when fitted to an Arduino form-factor MCU development platform by running the MultiTech AT Command Firmware. To do this, the UART crossover switch (small slide switch) needs to be switched to the "ON" position.

See the Factory Firmware section below for more details.

Windows Serial Driver

The mbed serial driver must be installed on windows PCs before the USB debug serial port from the xDot can be used.

Offline Development Options

It is possible to develop offline for the xDot using mbed-cli and the Eclipse IDE. See wiki page for more information.


http://i.imgur.com/cXTmFNA.jpg

The pinout diagram above shows the commonly used interfaces and their locations. In addition to their stated functions, all GPIO pins (PA_*, PB_*) can also be used as DigitalIn and DigitalOut interfaces.

InterruptIn Limitations

Due to the processor's architecture, only one pin of the same number (e.g. PA_1 & PB_1) may be configured as an InterruptIn. If multiple pins of the same number are configured as InterruptIn, only the last pin configured will actually trigger an interrupt in the processor. The rest will be ignored.

Pin numbers 1, 6, 7, 8, and 13 are internally used as interrupts from the LoRa radio and may not be configured as external interrupts. Doing so will break the LoRa functionality of the xDot and cause undefined behavior.

Example: If the WAKE (PA_0) pin is configured to wake the xDot from low power modes, GPIO2 (PB_0) may not be configured as an InterruptIn. Doing so will cause the WAKE pin to not wake the xDot as desired.

PwmOut Limitations

PwmOut objects using different channels of the same timer must use the same prescaler value. Each timer has a single prescaler which applies to all channels in the timer.

For STM32L15x devices, two possible prescaler values are allowed:

  • 1us which allows for a period/pulse from 1us to 65535us
  • 500us which allows for a period/pulse from 500us to 32.76s

5V Tolerant IO Limitations

If the external voltage on a GPIO is greater than VDD + 0.3V, use of the internal pullup or pulldown resistors could damage the xDot. External pullup or pulldown resistors should be used instead.

For more information see the notes below section 6.3.1 of the STM32L151CC Data Sheet.

mbed Library Limitations

This platform exclusively supports mbed OS version 5. It is compatible with the mbed-os library available to import from https://github.com/armmbed/mbed-os. The use of the mbed 2 SDK "classic" library will result in an error. Most of the APIs are compatible between mbed versions, but please remember to use the right mbed library (mbed-os).


xDot Features


The FF1705 includes the DAPLink interface. Firmware for the FF1705 will be included in DAPLink releases. To update the interface firmware on your FF1705, follow these steps:

You can re-program your FF1705 at any time by plugging it in with the button held down. This will cause it to appear as the "CRP DISABLD" drive, at which point you can follow the steps above.


Example Programs

The following programs support multiple Dot devices. Before examples or the AT firmware are compiled, a Dot library must be imported. See the Dot-Examples or Dot-AT-Firmware landing pages for more details.

Import programDot-Examples

Example programs for MultiTech Dot devices demonstrating how to use the Dot devices and the Dot libraries for LoRa communication.

Import programDot-AT-Firmware

AT command firmware for MultiTech Dot devices.

The mbed OS API References contain example code which demonstrates how to use common peripherals like Digital IO, Analog IO, Serial, SPI, I2C, PWM, RTOS, Timers, Tickers, etc.



Factory Firmware

The xDot ships from the factory pre-loaded with custom AT Command Firmware. This firmware provides a serial AT command interface for configuring and using the xDot. This firmware is great during development for testing LoRa transmissions and in production when using a separate host processor that controls the xDot via AT commands. It is available here. AT command documentation is available here.

Technical Reference

Documentation

Data Sheets



Getting Started with mbed

1. Connect your microcontroller to a PC

Use the USB lead to connect your mbed to a PC. The status light will come on, indicating it has power. After a few seconds of activity, the PC will recognise the mbed Microcontroller as a standard USB drive.

/media/uploads/dan/winxp-disk.png/media/uploads/dan/mac-disk.png
Windows XP exampleMac OS X example

Go to the new USB Drive, and click MBED.HTM to open it in a web browser.

If you do not have an mbed account, choose "Signup", and create your mbed Account. Otherwise, log in with your normal username and password.

This will give you access to the website, tools, libraries and documentation.



PC Configuration

Your mbed Microcontroller can appear on your computer as a serial port. On Mac and Linux, this will happen by default. For Windows, you need to install a driver:

Windows

See Windows-serial-configuration for full details about setting up Windows for serial communication with your mbed Microcontroller

From a host PC to communicate with mbed you will need a terminal application. This allows the mbed Microcontroller to print to your PC screen, and for you to send characters back to your mbed.

Some terminal programs (e.g. TeraTerm) list the available serial ports by name. However, if you do need to know the identity of the serial port so that you can attach a terminal or an application to it:

WindowsMacLinux
Find the identity of the COM port by opening ''Device Manager''. To do this navigate ''Start -> Control Panel -> System -> Hardware -> Device Manager''.To find the device name under Mac OS X, use the command ''ls /dev/tty.usbmodem*''To find the device name under Linux, use the command ''ls /dev/ttyACM*''
windowsmaclinux

On both Mac and Linux PCs, the port with the higher number will be the USB serial debug port. For example, if you have Linux and get ports /dev/ttyACM0 and /dev/ttyACM1, ttyACM1 will be the debug port and ttyACM0 the AT command/secondary port.



Downloading A program

1. Save a program binary (.bin) to the Platform

Download the appropriate "Hello World!" binary:

Note: the source code for this program will be seen in the next section.

Save the program binary file to your mbed Microcontroller Disk, just like you would with a normal USB disk. The Status LED will flash as the PC writes the file to the Microcontroller disk. The file is now consumed.

blink

2. Press the Reset Button

When the Reset Button in pressed, the microcontroller will be reset and the last programmed application will begin to run.

3. Hello World!

The Microcontroller is now running the program; flashing LED1 forever! If you reset the Microcontroller, or disconnect and reconnect the power, the program will simply restart.



Hello World!

Import programmbed-os-example-blinky

This is a very simple guide, reviewing the steps required to get Blinky working on an mbed OS platform.



Where Next

Follow the guide to creating your own programs using the online compiler


Schematics

The FF1705 is an open hardware design delivered as part of the mbed-HDK

  Pre-order


Please log in to start a discussion or ask a question.