Physical devices mapping (XUELK)
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
Info Box
|
This article details how physical devices are mapped to Linux device files in the context of the XUELK kit.
Contents
Console UARTEdit
| Physical device | Processor's resource | Connector | Type | Linux device file | Notes |
|---|---|---|---|---|---|
| Boot Console | UART1 | J42 | 2-wire LVTTL UART | /dev/ttymxc0 |
Multi-protocol UARTsEdit
Ordering code: XUBxx0xxx0xEdit
| Physical device | Processor's resource | Connector | Type | Linux device file | Notes |
|---|---|---|---|---|---|
| MPUART0 | UART7 | J34 | 2-wire RS232 | /dev/ttymxc6 |
|
| MPUART1 | UART3 | J21 | RS485 | /dev/ttymxc2 |
Ordering code: XUBxx0xxx1xEdit
| Physical device | Processor's resource | Connector | Type | Linux device file | Notes |
|---|---|---|---|---|---|
| MPUART0 | UART8 | J34 | 2-wire RS232 | /dev/ttymxc7 |
|
| MPUART1 | UART3 | J21 | RS485 | /dev/ttymxc2 |