Changes

Jump to: navigation, search

Physical devices mapping (XUELK)

29 bytes removed, 15:45, 30 December 2020
UART2 on mezzanine connector J53
{{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.
====UART8/RS232 initialization=Ordering code: XUBxx3xxxxx===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 > /sys/class/gpio/exportecho out > /sys/classdev/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/gpio/exportecho in > /sys/class/gpiottymxc2</gpio133/directionecho 134 code> /sys/class/gpio/export||echo in > /sys/class/gpio/gpio134/direction|-</pre>|}
====UART3/RS232 initialization [21] ====In order to use UART3 as RS232 interface, some GPIOs need to be configured as followsSupported baud rate range:<pre>echo 114 > /sys/class/gpio/exportecho out > /sys/class/gpio/gpio114/directionecho 1 > /sys/class/gpio/gpio114/valueecho 133 > /sys/class/gpio/exportecho out > /sys/class/gpio/gpio133/directionecho 1 > /sys/class/gpio/gpio133/valueecho 134 > /sys/class/gpio/exportecho out > /sys/class/gpio/gpio134/directionecho 1 > /sys/class/gpio/gpio134/value</pre> [2] RS232 configuration is available on request (different Order Code)9600 Bps - 115200 Bps.
==UART2 on mezzanine connector J53==
|-
|}
 
==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/.
8,154
edits

Navigation menu