• 07/14/2017
  • Public Content

Setting Up Serial Communication for Linux* Hosts

  1. Linux has support for FTDI chips by default. If you need the drivers, you can find them on http://www.ftdichip.com/Drivers/VCP.htm.
  2. Plug the Micro USB cable (Type B) into a regular
    Type A USB port
    on your host computer.
  3. Plug the other end of the cable in to the
    Micro USB Type B port
    on the development platform.
  4. On your host computer, open a Terminal window.
  5. If you do not have a shell session manager installed, such as picocom or Screen, you will need to install one. To do so, enter the command:
    By adding user to the "dialup" group you can avoid the need for "sudo" level commands.
    sudo apt-get install picocom
  6. If prompted, enter your computer user password.
  7. Use the screen utility to connect to your development platform using /dev/ttyUSB0 as the device dev path and the baud-rate 115200. For example:
    picocom -b 115200 /dev/ttyUSB0
  8. If prompted, enter your computer user password to continue.
Failing to close the Screen or picocom connection fully may stop you from being able to log in next time without rebooting the development platform. Close Screen sessions every time you are done with your serial connection.
To end a Screen session, type
Ctrl + A
, then
Ctrl + Q.

Product and Performance Information


Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804