Difference between revisions of "RIALTO SBC/Interfaces and Connectors/CAN"
(Created page with "<section begin="History" /> {| style="border-collapse:collapse; " ! colspan="4" style="width:100%; text-align:left" ; border-bottom:solid 2px #ededed" |History |- ! style="bo...") |
(→Device mapping) |
||
| Line 53: | Line 53: | ||
=== Device mapping === | === Device mapping === | ||
| − | CAN devices are mapped to <code> | + | CAN devices are mapped to <code>can0</code> device in Linux. The device mapping depends on the device tree configuration. |
=== Device usage === | === Device usage === | ||
Latest revision as of 11:28, 7 February 2024
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
| History | |||
|---|---|---|---|
| Issue Date | Notes | ||
| 2024/01/12 | First release | ||
CAN interface[edit | edit source]
Description[edit | edit source]
The CAN interface is optionally available on RIALTO SBC at the connector J66.
- J66 is a Phoenix 282837-3 3x50.8mm connector. On this connector are mapped these instances: UART3 or CAN.
CAN interface is connected to the i.MX6UL FLEXCAN controller.
Signals[edit | edit source]
The following table describes the interface signals:
| Pin# | Pin name | Pin function | Pin Notes |
|---|---|---|---|
| 1 | EXT1_P1 | RS232_RX or CAN_P | optional RS232 or CAN port |
| 2 | EXT1_P2 | RS232_TX or CAN_M | optional RS232 or CAN port |
| 3 | EXT1_GND | GND | connected to DGND directly or to PCN GND ring via RC filter |
Device mapping[edit | edit source]
CAN devices are mapped to can0 device in Linux. The device mapping depends on the device tree configuration.
Device usage[edit | edit source]
The peripheral can be configured using ifconfig and ip link utilities and can be tested with the can-utils utilities.
