Colibri iMX6 features two Controller Area Network (CAN) interfaces. The interface is provided by secondary functions on the SODIMM pins. The interface is therefore not compatible with all the modules in the Colibri family. The following table shows the location of the pins:
| SODIMM Pin | Colibri Signal Name | i.MX6 Signal Name | Description |
|---|---|---|---|
| 63 186 | PS2 SCL1 ADDRESS17 | FLEXCAN1_RX | CAN receive pin |
| 55 184 | PS2 SDA1 ADDRESS18 | FLEXCAN1_TX | CAN transmit pin |
| 188 | ADDRESS16 | FLEXCAN2_RX | CAN receive pin |
| 178 | DATA30 | FLEXCAN2_TX | CAN transmit pin |
If only one CAN interface is required, the interface on Pin 63/55 is preferable since it is compatible with other NXP based Colibri modules.
Colibri iMX6ULL features two Controller Area Network (CAN) interfaces. The interface is provided by secondary functions on the SODIMM pins. The interface is therefore not compatible with all the modules in the Colibri family. The following table shows the location of the pins:
| SODIMM Pin | Colibri Signal Name | i.MX6ULL Signal Name | Description |
|---|---|---|---|
| 63 48 49 186 | PS2 SCL1 LCD RGB Data<9> SDCard DAT<1> ADDRESS17 | can1.RX | CAN receive pin |
| 55 62 100 192 | PS2 SDA1 LCD RGB Data<8> Keypad_Out<1> SDCard DAT<0> | can1.TX | CAN transmit pin |
| 188 34 50 53 | ADDRESS16 UART_B RTS LCD RGB Data<11> SDCard DAT<3> | can2.RX | CAN receive pin |
| 178 32 51 74 | DATA30 UART_B CTS SDCard DAT<2> LCD RGB Data<10> | can2.TX | CAN transmit pin |
If only one CAN interface is required, the interface on Pin 63/55 is preferable since it is compatible with other NXP based Colibri modules.
Colibri VFxx features two Controller Area Network (CAN) interfaces. The interface is provided by secondary functions on the SODIMM pins. The interface is therefore not compatible with all the modules in the Colibri family. The following table shows the location of the pins:
| SODIMM Pin | Colibri Signal Name | Vybrid Signal Name | Description |
|---|---|---|---|
| 63 | GPIO | CAN1_RX | CAN receive pin |
| 55 | GPIO | CAN1_TX | CAN transmit pin |
| 196 | I2C SCL | CAN0_RX | CAN receive pin |
| 194 | I2C SDA | CAN0_TX | CAN transmit pin |
If only one CAN interface is required, the interface on Pin 63/55 is preferable since it is compatible with other NXP based Colibri modules.
Colibri i.MX7 features two Controller Area Network (CAN) interfaces. The interface is provided by secondary functions on the SODIMM pins. The interface is therefore not compatible with all the modules in the Colibri family. The following table shows the location of the pins:
| SODIMM Pin | Colibri Signal Name | i.MX7 Signal Name | Description |
|---|---|---|---|
| 63 90 169 | PS2 SCL1 SPI RXD DATA10 | can1.RX | CAN receive pin |
| 55 92 | PS2 SDA1 SPI TXD | can1.TX | CAN transmit pin |
| 188 196 81 | ADDRESS16 I2C SCL Camera Input VSYNC | can2.RX | CAN receive pin |
| 178 194 94 | DATA30 I2C SDA Camera Input HSYNC | can2.TX | CAN transmit pin |
If only one CAN interface is required, the interface on Pin 63/55 is preferable since it is compatible with other NXP based Colibri modules.
Colibri i.MX8 features three Controller Area Network (CAN) interfaces, the one located at pin 63/55 is compatible with Colibri iMX6, Colibri iMX6ULL, Colibri iMX7, and the Colibri VFxx modules. When it comes to the 34/22 interface, it is only compatible with Colibri iMX6ULL.
The following table shows the location of the pins:
| SODIMM Pin | Colibri Signal Name | i.MX8X Signal Name | Description |
|---|---|---|---|
| 63 19 |
PS2 SCL1 UART_C RXD |
ADMA.FLEXCAN1.RX | Can receive pin |
| 55 21 |
PS2 SDA1 UART_C TXD |
ADMA.FLEXCAN1.TX | Can transmit pin |
| 34 36 |
UART_B RTS UART_B RXD |
ADMA.FLEXCAN0.RX | Can receive pin |
| 32 38 |
UART_B CTS UART_B TXD |
ADMA.FLEXCAN0.TX | Can transmit pin |
| 33 | UART_X RXD | ADMA.FLEXCAN2.RX | Can receive pin |
| 35 | UART_A TXD | ADMA.FLEXCAN2.TX | Can transmit pin |
Other Colibri modules do not feature a native CAN interface. If CAN is required, a CAN controller can be attached on the SPI or parallel system bus to such modules. The Colibri Evaluation Board features such an external CAN controller. Please refer to the schematic of the Colibri Evaluation Board for more details.
The Colibri Evaluation Board has an SPI to CAN controller (MCP2515), Electrical Isolator and a CAN Transceiver on board. The SPI to CAN controller is compatible with every Colibri module and we provide drivers for it.
The Iris Carrier board does not have a CAN chip or CAN transceivers on board, however you can use the CAN interfaces of the Colibri i.MX7 as 3.3V CAN interface.
The Viola Carrier board does not have a CAN chip or CAN transceivers on board, however you can use the CAN interfaces of the Colibri i.MX7, i.MX6 and Vybrid as 3.3V CAN interface.
