Table of Contents
Advertisement
Chapter 2 – Getting Started
Getting Started with the xDot Developer Kit
Getting started depends on what you want to do. By default, xDot ships with firmware that supports AT
Commands that use the serial I/O. For AT Commands, refer to the separate MultiConnect Dots AT Command
Reference Guide.
Two serial interfaces are available through the USB interface, one is used to send AT commands to the xDot and
the other is for debug messages. Refer to Chapter 4, Specifications and Pin Information for information on which
pins are available out of the box.
Before starting your project development, make sure you have the latest firmware for the Developer Kit and xDot.
Go to the xDot mbed page for firmware.
To send commands to the xDot:
1.
Plug the developer board into a USB port.
2.
Open communications software, such as TeraTerm, Putty, or Minicom.
3.
Set the following:
To develop using Mbed, the xDot Mbed page includes libraries and test cases. Refer to
details and links.
For help setting up a MultiConnect
COM Port Enumeration by Operating System
xDots create an AT Commands port and a debug port.
Linux
The following COM ports are created on Linux systems:
/dev/ttyACMx
/dev/ttyACMy
Where x and y may be 0 and 1, 3 and 4, etc.
The COM port with lower number is the AT command port and COM port with the higher number is the debug
port.
Windows
On Windows systems, COM ports appear in the Device Manager:
Debug Port: Mbed Serial Port
®
xDot
Developer Guide for Japan
https://developer.mbed.org/platforms/MTS-xDot-L151CC/
Baud rate = 115,200
Data bits = 8
Parity = N
Stop bits = 1
Flow control = Off
®
®
Conduit
to send data to and from an xDot, refer to
GETTING STARTED
mbed Documentation
for
Related Documentation
.
11
Advertisement
Table of Contents
Need help?
Do you have a question about the MultiConnect xDot and is the answer not in the manual?
Questions and answers