Bureaucrats, dave_user, Administrators
743
edits
Changes
minor changes to history table
{{InfoBoxBottom}}
This article details how physical devices are handled by the Linux kernel in the context of the [[AXEL_ULite_and_SBC_Lynx_Embedded_Linux_Kit_(XUELK)|XUELK kit]].
== History ==
{| class="wikitable" border="1"
!Version
!Date
![[AXEL_ULite_and_SBC_Lynx_Embedded_Linux_Kit_(XUELK)|XUELK version]]
!Notes
|-
|{{oldid|6648|1.0.0}}
|December 2016
|1.0.0
|First public release
|-
|1.2.0
|May 2017
|1.2.0
|Update for new XUELK release
|-
|2.0.0
|September 2017
|2.0.0
|Validated on latest XUELK release
|-
|}
==Console UART==
{| class="wikitable"
|}
==Multi-protocol UARTs==
{{ImportantMessage|text=From [[AXEL_ULite_and_SBC_Lynx_Embedded_Linux_Kit_(XUELK)|XUELK]] version 1.2.0 UART are automatically initialized at boot time, depending on [[ConfigID (XUELK)|ConfigID]]. For XUELK release 1.1.3 and below, in order to use UART8 as RS232 interface, some GPIOs need to be configured as follows explained {{oldid|6648|into release 1.0.0 of this page}} }}
===Ordering code: XUBxx0xxx0x===
{| class="wikitable"
|-
|}
===Ordering code: XUBxx0xxx1xXUBxx0xxxxx===
{| class="wikitable"
|-
[1] Supported baud rate range: 9600 Bps - 115200 Bps.
===Ordering code: XUBxx3xxxxx=UART8/RS232 initialization====In order to use UART8 as RS232 interface, some GPIOs need to be configured as follows:<pre>echo 113 > /sys/{| class/gpio/export="wikitable"echo out > /sys/class/gpio/gpio113/direction|-echo 1 > /sys/class/gpio/gpio113/value! Physical device !! Processor's resource !! Connector !! Type !! Linux device file !! Notesecho 136 > /sys/class/gpio/export|-echo out > /sys/class/gpio/gpio136/directionecho | MPUART0 || UART8 || J38 || RS485 [1 ] || <code> /sys/class/gpio/gpio136/valueecho 137 > /sysdev/class/gpio/exportecho out > /sys/class/gpio/gpio137/directionecho 1 > /sys/class/gpio/gpio137/valuettymxc7</precode>||====UART3/RS485 initialization====|-In order to use | MPUART1 || UART3 as || J39 || RS485 interface, some GPIOs need to be configured as follows:[1] || <pre>echo 114 code> /sysdev/class/gpio/exportecho out > /sys/class/gpio/gpio114/directionecho 1 > /sys/class/gpio/gpio114/valueecho 133 > /sys/class/gpiottymxc2</exportecho in code> /sys/class/gpio/gpio133/direction||echo 134 > /sys/class/gpio/export|-</pre>|}
==UART2 on mezzanine connector J53==
{| class="wikitable"
|-
! Processor's resource !! Connector .pin# !! Type !! Linux virtual resource !! Notes
|-
| MX6UL_PAD_UART5_RX_DATA__GPIO1_IO31 || J53 .6 || LVTTL GPIO || GPIO #31 || see following examples
|-
| MX6UL_PAD_UART5_TX_DATA__GPIO1_IO30 || J53 .5 || LVTTL GPIO || GPIO #30 || see following examples
|-
| MX6UL_PAD_LCD_DATA19__GPIO3_IO24 || J53 .7 || LVTTL GPIO || GPIO #24 || see following examples
|-
| MX6UL_PAD_LCD_DATA22__GPIO3_IO27 || J53 .8 || LVTTL GPIO || GPIO #27 || see following examples
|-
| MX6UL_PAD_LCD_DATA23__GPIO3_IO28 || J53 .9 || LVTTL GPIO || GPIO #28 || see following examples
|-
|}
Once mounted (at <code>/run/media/sda1</code> in the esampleexample), the memory stick can be accessed by regular commands:
<pre>
root@sbc-lynx:~# mount
[1] This type of cables forces the ID signal of the USB port to be connected to ground, selecting the host mode on SBC Lynx side.
===Device mode===
The following examples shows how to configure SBC Lynx to act as a mass storage device.
[ 80.060663] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
</pre>
Once mounted (at <code>/mnt/usb/</code> in the example), the memory stick can be accessed by with regular commands:
<pre>
root@imx6ulevk:~# mkdir /mnt/usb
