Physical devices mapping (XUELK)
Revision as of 14:33, 4 October 2016 by U0001 (talk | contribs) (Created page with "{{InfoBoxTop}} {{AppliesToSBCLynx}} {{InfoBoxBottom}} This article details how physical devices are mapped to Linux device files in the context of the AXEL_ULite_and_SBC_Lyn...")
| 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.
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: XUBBx0xxxxxEdit
| 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 |