{{ImportantMessage|text=SBC Lynx is extremely flexible in terms of hardware configurations. This document details connector's pinout of common SBC Lynx models. For more information about models not documented here, please contact [mailto:sales@dave.eu Sales department].}}
==Introduction==
This document details connectors, buttons and switches that equip SBC Lynx board. '''Please note that not all of them are available on all models'''.
For some connectors, information related to the internal connections to the processor are provided. In these cases, 14x14mm-package processor's balls references are indicated.
The following table lists connectors, buttons and switches available on SBC Lynx.
System console is by default routed to this interface. This is typically used during the development stage.
|}
=J42 connector is compatible with [http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_TTL-232RG_CABLES.pdf FTDI TTL-232RG-VIP-WE cable]. To connect it, please use this wiring:*J42.1: yellow wire*J42.2: orange wire*J42.3: red wire*J42.4: black wire ==Ethernet connector (J16)=== [[File:SBC Lynx-J16.png|thumb|center|300px|J16]]
J16 is a standard RJ45 10/100BaseT Ethernet connector - incorporating magnetics - connected to the Ethernet controller and PHY.
J16 integrates a green status LED providing connection information:
*LED on: link established
*LED blinking: activity.
The following table describes the interface signals:
J43 is a push-pull microSD card slot connected to uSDHC1 port of MX6UL processor.
|13||CD||Card detect||Pulled-up to 3.3V
|}
===USB host port (J48)=== [[File:SBC Lynx-J48.png|thumb|center|300px|J48]] J48 is a standard USB Type A right angle connector connected to the MX6UL USB_OTG2 port signals. The following table reports the connector's pinout:
===USB OTG port (J47)=== [[File:SBC Lynx-J47.png|thumb|center|300px|J47]] J47 is a standard USB Type micro AB connector connected to the MX6UL USB_OTG1 port signals. The following table reports the connector's pinout:
J53 and J54 are 10x1-pin 2.54mm-pitch vertical headers for optional mezzanine expansion boards. These boards can be implemented to extend SBC Lynx functionalities and/or interfaces.
|}
[5] '''To be used for voltage reference only'''.
====Handling bootstrap signals====MEZZANINE_GP0, MEZZANINE_GP1 and MEZZANINE_GP2 are connected to LCD_DATA19, LCD_DATA22 and LCD_DATA23 respectively. As such, they act as bootstrap configuration signals as well. They can be used by application software freely and the they can be connected to user's application circuitry. However, '''any electrical interference during the processor reset cycle must be avoided'''.
There are different solutions to comply with this requirement. The following image shows a concept solution for this problem.
[1] The same considerations apply to all of LCD_DATAx signals that are routed to J45/J52 connectors.
===One-piece interfaces (J45 / J52)== {| class="wikitable" | width="100%"| [[File:SBC Lynx-J45-52.png|thumb|center|300px|J45]]| [[File:XUAE-side-mount.png|thumb|center|300px|example of possible connections on J45]]| [[File:Mech-design-XUAE-bottom.png|thumb|center|300px|J52]]| [[File:SBC-Lynx-onepiece-bottom.png|thumb|center|300px|example of possible connections on J52]]|}
J45 and J52 are two interfaces designed to be populated with Samtec 1.00mm-pitch 30x2-pin FSI One-piece connectors. The peculiarity of this kind of connectors if the fact that they
*allow to mate two boards by using one connector only
!Pin #
!Processor ball
!Nameand default function!Alternative and default functions<br>(Default function is bolded) [1]
| 16||C14||LCD_DATA20||LCD_DATA20 ECSPI1_SCLK / SPI1_SCLK / SDHC2_DATA0USDHC2_DATA0 || Output || IO_3.3V ||SPI1 is available only if NOR is not mounted, [3]
|-
| 18||B14||LCD_DATA21||LCD_DATA21 ECSPI1_SS0 / SPI1_SS0 / SDHC2_DATA1USDHC2_DATA1 || Output || IO_3.3V ||SPI1 is available only if NOR is not mounted, [3]
|-
| 20||A14||LCD_DATA22||LCD_DATA20 ECSPI1_MOSI / SPI1_MOSI / SDHC2_DATA2USDHC2_DATA2 || Output || IO_3.3V ||SPI1 is available only if NOR is not mounted, [3]
|-
| 22||B16||LCD_DATA23||LCD_DATA20 ECSPI1_MISO / SPI1_MISO / SDHC2_DATA3USDHC2_DATA3|| Output || IO_3.3V ||SPI1 is available only if NOR is not mounted, [3]
|-
| 24||-||DGND||Ground|| || ||-
|-
| 26||C17||ENET2_RX_DATA0||ENET2_RX_DATA0 / UART6_TX / I2C3_SCL / || Input || IO_3.3V ||Default: internally used as USB OTG power
|-
| 28||C16||ENET2_RX_DATA1||ENET2_RX_DATA1 / UART6_RX / I2C3_SDA|| Input || IO_3.3V ||Default: internally used as USB OTG over current
| 58||K13||GPIO1_IO00||GPIO TSC(wiper) / TSC_WIPER / ADCADC1_IN0 || Input/Output || IO_3.3V ||Default: internally used as USB OTG ID
|-
| 60||-||DGND||Ground|| || ||-
[2] This signal can be routed here instead of connector J48. Please refer to the [mailto:sales@dave.eu Sale Deparment] for more details.
=[3] LCD_DATAx signals act as bootstrap configuration pins as well. They can be used by application software freely and they can be connected to user's application circuitry. However, '''any electrical interference during the processor reset cycle must be avoided'''. Please see [[#Handling bootstrap signals|Handling bootstrap signals]] section for more details. ==DWM WiFi/Bluetooth module connector (J46)=== [[File:SBC Lynx-J46.png|thumb|center|300px|J46]]
J46 is a 30-pins SlimStack™ Receptacle 0.50mm pitch that allows to connect to DAVE Embedded Systems' DWM Wifi/BT module.
The following table reports the connector's pinout:
===Multiprotocol UARTs and CAN interfaces===There are two UART multiprotocol ports (RS232 / RS485 / RS422) and one CAN interface available on SBC LYNX.They are described in the same section because they share some resources. Please refer to [[#Introduction|this section]] for more details about allowable combinations.===Multiprotocol UARTs===UART interfaces Multiprotocol UARTs are named as MPUART0 (and MPUART1. They are associated to i.MX6UL 's native UART8) and MPUART1 (MX6UL UART3) and respectively. They are routed to connectors through Intersil ISL3330 transceivers (one for each port).
Generally speaking, multiprotocol UARTs
*supports RS232, RS485 and RS422 electrical protocols independently (meaning that, for example, MPUART0 can be configured as RS485 and MPUART1 can be configured as RS485)
**electrical protocol is selected by different mounting options
*can be routed to different types of connector independently; supported connectors are:
This wide flexibility allows to implement many different combinations. The following table details two of them. For actual available options, please contact [mailto:sales@dave.eu Sales department].
| 1||H15||CAN_D||Transmit data input|| Input || IO_3.3V ||Alternative to MPUART1_nCTS
|-
| 4||G14||CAN_R||Receive data output|| Output || IO_3.3V ||Alternative to MPUART1_nRTS
|-
|}
====Connector's pinout====
The following sections detail connectcors' pinout for the supported configuration. In case RS422 or RS485 configurations are used, termination options are selectable by acting on S12 switches, as described in [[Multiprotocol UARTs settings (S12)|this section]].
====Additional options for RS422 and RS485 interfaces====
Other options are available on request, as described in the following sections. For more information, please contact [mailto:sales@dave.eu Sales department].
=====Fail-safe resistors=====
On request, it is possible to populate fail-safe resistors on RS422/RS485 differential signals. For more information, please contact [mailto:sales@dave.eu Sales department].
=====RS485 alternative pinout for DB9 connector=====
[[File:SBC Lynx-J21.png|thumb|center|300px|J21]]
On request, it is possible to implement the following pinout.