
OSDAUG OpenSDA User's Guide Page 7 of 9
1.2.4 USB Communications Device Class (CDC)
Several of the default OpenSDA Applications provided by Freescale, including the MSD Flash
Programmer and the P&E Debug Application, provide a USB Communications Device Class (CDC)
interface that bridges serial communications between the USB Host and a UART serial interface on the
target processor.
With a Windows host operating system, the USB CDC interface will automatically be assigned a COM
number, such as COM10 or COM11. To understand which COM number has been assigned to the unit,
refer to the Windows Device Manager (Start->Run->”mmc devmgmt.msc”) and look in the “Ports”
section. Many free terminal applications, such as Tera Term and PuTTY, are available to send and
receive serial traffic in Windows.
When the USB CDC interface enumerates on the Linux host operating system, it is generally assigned a
tty* hardware identifier. Many free terminal applications, such as minicom, are available to send and
receive serial traffic in Linux. Make sure you have the appropriate permissions in the operating system
to access this port. Drivers, which can be downloaded from http://www.pemicro.com/opensda, help
configure these permissions.
The OpenSDA Applications do not drive the serial transmit pin to the target microcontroller until the
CDC serial port is opened by an application on the host operating system. After that, these pins will be
driven and will remain driven even after the USB CDC serial port is closed.
NOTE: There is a known Windows issue that affects most terminal applications. The virtual COM port
will be removed from the device manager when the USB cable is unplugged even if a terminal
application has the virtual COM port opened. The virtual COM port will not be accessible even after
the virtual serial device is reconnected unless the virtual COM port is released by the application prior
to the reconnection, which may require closing the application first. It is recommended that the
terminal application be closed before the OpenSDA USB cable is unplugged.
2 Getting Started with OpenSDA
Follow these simple steps to interact with an embedded OpenSDA.
2.1 Getting into Bootloader Mode
The Bootloader runs automatically when a powered USB cable is attached to the OpenSDA-compliant
device and immediately executes the installed OpenSDA Application unless forced into Bootloader
mode by the user. To force the device into Bootloader mode, use the following procedure:
1. Unplug the USB cable (if attached).
2. Press and hold the Reset button.
3. Plug in a USB cable from a USB Host to the OpenSDA USB port.
4. Release the RESET/Bootloader button.
5. A removable drive will be visible in the host file system with a volume label of BOOTLOADER.
For more information, double-click the FSL_WEB.HTM link to open the tools pages for the
development system in use and explore the other files embedded in the hardware. See Table 1 for a
description of these files.