Bureaucrats, dave_user, Administrators
8,154
edits
Changes
→UART2 on mezzanine connector J53
{{AppliesToSBCLynx}}
{{InfoBoxBottom}}
This article details how physical devices are mapped to handled by the Linux device files 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"
| MPUART0 || UART7 || J34 || 2-wire RS232 || <code>/dev/ttymxc6</code> ||
|-
| MPUART1 || UART3 || J21 || RS485 [1]|| <code>/dev/ttymxc2</code> ||
|-
|}
===Ordering code: XUBxx0xxx1xXUBxx0xxxxx===
{| class="wikitable"
|-
| MPUART0 || UART8 || J34 || 2-wire RS232 || <code>/dev/ttymxc7</code> ||
|-
| MPUART1 || UART3 || J21 || RS485 [1] || <code>/dev/ttymxc2</code> |||-|} [1] Supported baud rate range: 9600 Bps - 115200 Bps. ===Ordering code: XUBxx3xxxxx==={| class="wikitable"|-! Physical device !! Processor's resource !! Connector !! Type !! Linux device file !! Notes|-| MPUART0 || UART8 || J38 || RS485 [1] || <code>/dev/ttymxc7</code> |||-| MPUART1 || UART3 || J39 || RS485 [1] || <code>/dev/ttymxc2</code> ||
|-
|}
[1] Supported baud rate range: 9600 Bps - 115200 Bps.
==UART2 on mezzanine connector J53==
Please note that '''this UART is not available if WiFi/Bluetooth module is populated'''.
|-
|}
==CAN==
Please note that '''the CAN interface is optionally available on J21 or J40 connectors''' with a custom Order code.
{| class="wikitable"
|-
! Processor's resource !! Connector !! Type !! Linux device file !! Notes
|-
| FLEXCAN1 || J21 or J40 || PHY translated (on-board)|| <code>can0</code> || Alternative mount of MPUART1 (not available)
|-
|}
==Ethernet==
Ethernet port is associated to <code>eth0</code> interface. It can be managed with standard Linux commands. See for example http://www.tecmint.com/ifconfig-command-examples/.
{| 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 via 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.
On PC side, SBC Lynx is detected as a common USB mass storage device.
==USB host==
The following example shows how an USB memory stick is detected by the Linux kernel when plugged into the J48 connector:
[ 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
