background image

© 2014 Digi International Inc.

     4

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.

Summary of Contents for ETHERIOS ConnectCore 6

Page 1: ...ConnectCore 6 Linux BSP Reference Manual 90001403_A ...

Page 2: ...s 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 ...

Page 3: ...e 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 Wir...

Page 4: ...usses 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 ...

Page 5: ... 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 ...

Page 6: ...ALL_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 h...

Page 7: ...x 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 p...

Page 8: ...ilable 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 bo...

Page 9: ...s 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 U...

Page 10: ...S 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 ...

Page 11: ...us on the development board Although the display is multi touch user space does only support single touch events U Boot Environment U Boot environment can be accessed from Linux user space using the fw_printenv and fw_setenv tools Config file etc fw_env config determines the device start offset and size of the environment and its redundant copy The default config file points to the U Boot environm...

Page 12: ...net device using the usbnet driver on Linux hosts or Microsoft s RNDIS driver on Windows hosts To load the Ethernet gadget This command will create an Ethernet interface in the target called usb0 and will assign random MAC addresses to the target and the host We need to give this new network interface usb0 an IP address for example On a host computer the usbnet module must be loaded so that the de...

Page 13: ... 1920x1080M 60 bpp 32 video2 set by default to OFF off The kernel command line expands these variables like this video mxcfb0 video0 video mxcfb1 video1 video mxcfb2 video2 The possible combinations are Only HDMI Set video0 to dev hdmi 1920x1080M 60 bpp 32 Set video1 and video2 to off Only LVDS with Fusion 10 LCD display Set video0 to dev ldb LDB HSD101PFW2 bpp 32 Set video1 and video2 to off LVDS...

Page 14: ...on called wd_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 watchdog to IMAGE_INSTALL_append The watchdog test application sets the watchdog timeout value and refreshes the watchdog timer every second during the test time After the test time is over the watchdog is not refreshed anymore and the driver...

Page 15: ...less chip connected to uSDHC1 The MAC address is taken from U Boot environment variable wlanaddr 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 wireless entry node to pass the driver the MAC address filled in by U Boot and the power down GPIO wireless digi pwrdown gpios gpio_extender 3 0 U ...

Reviews:

Related manuals for ETHERIOS ConnectCore 6