Digi Etherios connectcore 6 User manual

ConnectCore 6®

Linux BSP

Reference Manual

90001403_A

Digi, Digi International, the Digi logo, and ConnectCore 6®are trademarks or

registered trademarks in the United States and other countries worldwide. All

other trademarks mentioned in this document are the property of their respective

owners.

Information in this document is subject to change without notice and does not

represent a commitment on the part of Digi International. Digi provides this

document “as is,” without warranty of any kind, expressed or implied, including,

but not limited to, the implied warranties of fitness or merchantability for a

particular purpose. Digi may make improvements and/or changes in this manual

or in the product(s) and/or the program(s) described in this manual at any time.

Contacting Technical Support

Digi International Inc. World Headquarters

11001 Bren Road East Minnetonka, MN 55343

Phone: (866) 765-9885 toll-free U.S.A. & Canada

(801) 765-9885 Worldwide

8:00 am - 5:00 pm (U.S. Mountain Time)

Online Support: www.digi.com/support/

Email: [email protected]

Fax: 952-912-4952

Revision Record

Revision Date (MM/DD/YY) Description

A05/22/2014 Preliminary draft release

ConnectCore 6 Linux BSP Reference Manual

Table of Contents

About the ConnectCore 6 Linux BSP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Linux Kernel Device Tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Platform Device Tree Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Unsupported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Bluetooth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

CAN Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

GPIO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

I2C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

One-Time Programmable (OTP) Bits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Real Time Clock (RTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

SD/SDIO/MMC controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Serial port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Serial Peripheral Interface (SPI). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Sound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Touch screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

U-Boot Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

USB device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Serial gadget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Ethernet gadget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

File-backed mass storage gadget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

USB Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Backlight. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Watchdog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Wireless . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

ConnectCore 6 Linux BSP Reference Manual

About the ConnectCore 6 Linux BSP

This is a guide to supported devices and interfaces of the ConnectCore 6 platform in Digi

Embedded Yocto 1.6.

Linux Kernel Device Tree

Introduction

The Flattened Device Tree (FDT, or simply DT) is a data structure for describing the hardware in

a system. Rather than hard coding every detail of a device into the operating system, many

aspects of the hardware can be described in a data structure that is passed to the operating

system at boot time. The data structure itself is a simple tree of named nodes and properties.

Nodes contain properties and child nodes. Properties are simple name-value pairs. The structure

can hold any kind of data. The format is expressive and able to describe most board design

aspects including:

• The number and type of CPUs

• Base addresses and size of RAM

• Busses and bridges

• Peripheral device connections

• Interrupt controllers and IRQ line connections

Advantages

• Ship one FDT image per machine (a few kB) instead of one kernel image per machine (several

MB).

• Reduce or eliminate effort needed to write machine support code (i.e. arch/arm/mach-*).

Most board specific code changes constrained to FDT file and device drivers.

• No need to allocate a new global ARM machine id for each new board variant.

• Reduce the need to recompile the kernel. One kernel image with support for different

hardware can be shipped and be run in different variants (each one with its own FDT

describing the hardware which is really available).

• Expressive format to describe related board variants without allocating new machine numbers

or new ATAGs.

• U-Boot firmware can inspect and modify an FDT image before booting.

Formats

• *.dts: This is a Device Tree file in plain text (human readable).

• *.dtsi: This is like a DTS include file (a plain text file to be included by a DTS file).

• *.dtb: This is a Device Tree Blob: a binary representation of a Device Tree, once compiled

with the Device Tree compiler.

ConnectCore 6 Linux BSP Reference Manual

Platform Device Tree Files

The DTS file for the

ccimx6adpt

platform can be found in the kernel source code tree under:

arch/arm/boot/dts/imx6-ccimx6adpt-ldo.dts

This DTS file includes other DTS and DTSI file in the same path.

Unsupported Devices

The following devices or interfaces are not supported in the BSP of the Early Availability (EA) Kit:

• ADC

• Camera

• LCD parallel interface

• Power management

• PWM (on CPU)

Bluetooth

Bluetooth (if supported by the Atheros wireless chip variant) is connected to UART2.

The MAC address of the Bluetooth interface is taken from U-Boot environment variable

btaddr

which is populated by U-Boot on the Device Tree before booting Linux.

There is no generic Device Tree binding for the Bluetooth interface. Digi has created a

bluetooth entry node to pass the driver the MAC address (filled-in by U-Boot) and the power

down GPIO.

Note: Due to a HW bug in the module, Bluetooth is not supported in version 1 of the

ConnectCore 6 module.

CAN Bus

The CPU has two Flexcan CAN ports. The CAN support is based on the SocketCAN stack. For

more information about this project, documentation, and API, please refer to http://

developer.berlios.de/projects/socketcan/.

FlexCAN Device Tree binding is described at

Documentation/devicetree/bindings/net/can/fsl-

flexcan.txt

bluetooth{

 digi,pwrdown-gpios=<&gpio_extender40>;

 /*U‐BootwillfillintheMACaddresshere*/

};

ConnectCore 6 Linux BSP Reference Manual

Information about programming the CAN socket interface is given in the kernel tree under

Documentation/networking/can.txt

Each CAN port appears like a networking interface in the form can

where

is the port number.

The ports are disabled by default. To configure the CAN, first the bitrate must be set using

tool, for example:

To enable a port execute this command (specifying the appropriate port number):

A sample application called

can_test

is available and can be added to the rootfs by adding “dey-

examples” to the EXTRA_IMAGE_FEATURES of your

local.conf

or by adding “dey-examples-

can” to IMAGE_INSTALL_append. This sample application performs several operations on the

CAN node, like sending and receiving messages. An additional CAN node is needed in the other

end of the bus for the application to work (a CAN analyzer, for example).

For example, to send an 8-bit CAN message to node 'can0' with ID '0x12' and the data pattern

'0x65':

And to receive a similar message:

For more information see the applications help with can_test --help.

Ethernet

The ConnectCore 6 supports both Gigabit and 10/100 Ethernet. By default, the Ethernet

interface is configured for Gigabit.

FEC driver Device Tree binding is described at

Documentation/devicetree/bindings/net/fsl-fec.txt

To configure Ethernet for 10/100 you need to do the following change to the Device Tree:

# ip link set can0 type can bitrate 500000

# ifconfig can0 up

# can_test -l 1 -b 8 -d can0 -i 0x12 -p 0x65 -m

# can_test -l 1 -b 8 -d can0 -i 0x12 -p 0x65

ConnectCore 6 Linux BSP Reference Manual

Note: Due to a HW bug on the Adapter board, 10/100 Ethernet does not work on the

Adapter.

The MAC address is taken from U-Boot environment variable

ethaddr

which is populated by U-

Boot on the Device Tree before booting Linux.

diff‐‐gita/arch/arm/boot/dts/imx6‐ccimx6qdladpt.dtsib/arch/arm/boot/dts/imx6‐

ccimx6qdladpt.dtsi

indexcb713e47d833..0a6adaa4e08d100644

‐‐‐a/arch/arm/boot/dts/imx6‐ccimx6qdladpt.dtsi

+++b/arch/arm/boot/dts/imx6‐ccimx6qdladpt.dtsi

@@‐200,7+200,7@@

};



/*10/100/1000KSZ9031PHY*/

+/*

&fec{

 pinctrl‐names="default";

 pinctrl‐0=<&pinctrl_enet_4>;

@@‐211,10+211,9@@

 phy‐supply=<&ldo4>;

 status="okay";

};

+*/



/*10/100LAN8710PHY*/

‐/*

&fec{

 pinctrl‐names="default";

 pinctrl‐0=<&pinctrl_enet_5>;

@@‐225,7+224,6@@

 phy‐supply=<&ldo4>;

 status="okay";

};

‐*/

&gpc{

 fsl,cpu_pupscr_sw2iso=<0xf>;

ConnectCore 6 Linux BSP Reference Manual

The Freescale i.MX6 CPU has a documented errata ERR004512 whereby the maximum

performance of Gigabit ENET is limited to 400Mbps (total for Tx and Rx).

GPIO

The CPU has seven GPIO ports, six with 32 GPIOs and one with 14 GPIOs. GPIOs are multiplexed

with different functionalities of the chip. IOMUX of the pins is done at the device tree.

GPIO Device Tree binding is described at

Documentation/devicetree/bindings/gpio/fsl-imx-

gpio.txt

The GPIOs can be easily accessed from the sysfs. For information about how to manage the

GPIOs from sysfs, refer to the Linux kernel documentation at

Documentation/gpio.txt

The JSCCWMX53 development board contains two user LEDs and two user buttons that can be

used to test the GPIOs.

A sample application called

gpio_sysfs_test

is available and can be added to the rootfs by adding

“dey-examples” to the EXTRA_IMAGE_FEATURES of your

local.conf

or by adding “dey-

examples-gpio-sysfs” to IMAGE_INSTALL_append.

I2C

The CPU has three I2C ports. I2C2 is connected to the Dialog DA9063 PMIC and the Kinetis CPU

and cannot be used for other peripherals.

I2C3 is connected to the HDMI, LCD touch screen, camera, audio codec, and routed to the

Adapter board for additional peripheral connections on the development board.

I2C Device Tree binding is described at

Documentation/devicetree/bindings/i2c/i2c-imx.txt.

One-Time Programmable (OTP) Bits

The i.MX6 CPU contains several one-time programmable bits (also known as e-fuses).

The OTP bits can be read and programmed through the sysfs, under

/sys/fsl_otp

User LED1 User LED2 User Button 1 User Button 2

Port pin GPIO2_2 GPIO2_3 GPIO2_4 GPIO2_5

Linux gpio # 34 35 36 37

WARNING: Programming the OTP bits is an irreversible operation that could

potentially brick your module. Please don’t program the OTP bits unless you are

sure of what you are doing

ConnectCore 6 Linux BSP Reference Manual

Real Time Clock (RTC)

The Dialog DA9030 PMIC provides an Real Time Clock (RTC) circuit with alarm function. To

preserve the date and time during power off, the RTC must be powered externally through a

battery.

DA9030 PMIC’s binding is described at

Documentation/devicetree/bindings/mfd/da9063.txt

For information about RTC control in Linux please refer to the kernel documentation at

Documentation/rtc.txt

A sample application called

rtc_test

is available and can be added to the rootfs by adding “dey-

examples” to the EXTRA_IMAGE_FEATURES of your

local.conf

or by adding “dey-examples-

rtc” to IMAGE_INSTALL_append.

SD/SDIO/MMC controller

The CPU has four uSDHC controllers:

• uSDHC1 is internally connected to the Atheros wireless chip.

• uSDHC2 is available at the module and connected in the development board to a micro SD

socket.

• uSDCH3 is available at the module but also internally connected to the Atheros chip Bluetooth

UART in modules with Bluetooth support (in such modules this controller cannot be used).

• uSDHC4 is internally connected to the eMMC.

MMC binding is described at

Documentation/devicetree/bindings/mmc/mmc.txt

Serial port

The CPU has five UARTs. UART1 is a full modem whereas the other four UARTS (2..5) are only

four wires.

UART2 is internally connected to the Atheros chip Bluetooth UART in modules with Bluetooth

support (in such modules this UART cannot be used).

Please refer to the hardware reference manual of your board to determine available ports and

multiplexed functionality.

The driver only supports RS-232 mode. UART binding is described at

Documentation/devicetree/

bindings/tty/serial/fsl-imx-uart.txt

The standard serial programming API applies to the serial ports. For information about serial

programming, see the

Serial Programming HOWTO

http://tldp.org/HOWTO/Serial-

Programming-HOWTO/index.html

or the

Serial Programming Guide for POSIX Operating Systems

http://digilander.libero.it/robang/rubrica/serial.htm

ConnectCore 6 Linux BSP Reference Manual

Serial Peripheral Interface (SPI)

The CPU has five SPI controllers. Please refer to the hardware reference manual of your board to

determine available ports and multiplexed functionality.

ECSPI2 used to communicate with the Kinetis CPU (on module variants with Kinetis) and is

routed to the development board SPI connector.

SPI binding is described at

Documentation/devicetree/bindings/spi/fsl-imx-spi.txt

A sample application called

spi_test

is available to use with spidev driver to test the port in

loopback mode by connecting MISO and MOSI lines. The application can be added to the rootfs

by adding “dey-examples” to the EXTRA_IMAGE_FEATURES of your

local.conf

or by adding

“dey-examples-spidev” to IMAGE_INSTALL_append.

Sound

The module can output sound through through external audio chip SGTL5000 on the

development board (default) or through the HDMI interface. The available cards can be listed

with:

To change the default device, please refer to ALSA documentation at http://www.alsa-

project.org/main/index.php/Asoundrc.

The sound driver can be accessed using the ALSA API. ALSA utilities package also offer user

space applications:

• aplay: for playback

• arecord: for recording

• alsactl: for configuration

• amixer: for specific control setup

# aplay -L

null

Discard all samples (playback) or generate zero samples (capture)

default:CARD=sgtl5000audio

sgtl5000-audio,

Default Audio Device

sysdefault:CARD=sgtl5000audio

sgtl5000-audio,

Default Audio Device

default:CARD=imxhdmisoc

imx-hdmi-soc,

Default Audio Device

sysdefault:CARD=imxhdmisoc

imx-hdmi-soc,

Default Audio Device

Table of contents

Other Digi Single Board Computer manuals

Digi

Digi ConnectCore Application guide

Digi

Digi JACKRABBIT BL1800 User manual

Digi

Digi Rabbit Smartcat BL2100 Series User manual

Digi

Digi ConnectCore MP15 Quick user guide

Digi

Digi ConnectCore MP13 Quick user guide

Digi

Digi i.MX6UL Quick user guide

Popular Single Board Computer manuals by other brands

Aaeon

Aaeon EPIC-BT07 user manual

WIN Enterprises

WIN Enterprises PL-80910 user manual

AXIOMTEK

AXIOMTEK SBC81206 Series user manual

Embest

Embest SOM-PH8800 user manual

SeaLevel

SeaLevel SBC-R9 user manual

SMART Embedded Computing

SMART Embedded Computing ATCA-8310 quick start guide

WinSystems

WinSystems PPM-LX800-G Operation manual

GIGAIPC

GIGAIPC QBiP-8665A/ user manual

VersaLogic

VersaLogic Python EBX-11 Reference manual

Micro Computer Specialists

Micro Computer Specialists IRV-3702 user manual

Boser

Boser HS-7321 manual

Premier Farnell

Premier Farnell Embest SBC8530 quick start guide

OLIMEX

OLIMEX A10S-OLinuXino-MICRO user manual

E-TOP

E-TOP PISA-E1 user manual

Nexcom

Nexcom Peak 703P Series user manual

Boser

Boser HS-6301 manual

GIGAIPC

GIGAIPC QBiP-1165G7B user manual

OLIMEX

OLIMEX A13-OLinuXino user manual

Digi ETHERIOS ConnectCore 6 User manual

Popular Single Board Computer manuals by other brands