# UART4 (M7 MCU Core)

## Introduction

UART4 is available for general use. Hardware flow control is supported.

Note from the schematic clip below, that the MPU can multiplex these signals with SPI2. This is normally configured in the Linux image, and is not the default configuration.<br>

## UART4 Locator

<figure><img src="https://2768264622-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MQsLUVVC7cJOe9aVARC%2Fuploads%2FaRkQBLhWz7JN5Owj4Q4D%2Fimage.png?alt=media&#x26;token=4f0d82d8-0c0b-4c20-b406-597fb17d414b" alt=""><figcaption><p>UART connectors</p></figcaption></figure>

## UART4 interface voltage

The signaling from the SOM to the NavQPlus carrier board on J11 is at 3V3&#x20;

Alternative output is on the AUX connector at location J12 also at 3V3 signalling. However this is not the default linux BSP, and would require changes to the dtb files.\ <br>

## Schematic

J11/UART4 is the default location for UART4 signals. Also by default UART4 is assigned to the M7 Core on the i.MX8M Plus. An RTOS such as FreeRTOS or Zephyr would normally use it as the default console to the embedded MCU.<br>

<figure><img src="https://2768264622-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MQsLUVVC7cJOe9aVARC%2Fuploads%2FPGeqNy6JBpZKLGAIxMWZ%2Fimage.png?alt=media&#x26;token=dffabf78-d2de-4f6e-8824-cbde3eb6c060" alt=""><figcaption></figcaption></figure>

### UART NetNames

Note  signal names are differed on J11 vs J12. This is only a labelling detail, since the pinmuxing on the chip is used to "move" the UART4 interface from one set of pins on the MPU (and board to board header). In order to route these signals independently on the carrier board, they need their own net names.

### UART ESD

All the UART signals are protected from ESD using the Nexperia IP4292CZ components. This is part of an optimized BOM as they are also required for the USB interfaces. In additional to its exceptional performance the board layout may be optimized because of being able to route traces straight under the component.&#x20;

<figure><img src="https://2768264622-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MQsLUVVC7cJOe9aVARC%2Fuploads%2FL4YtstbIYH75eGXJw4Wm%2Fimage.png?alt=media&#x26;token=f4506d8b-e222-4515-9034-de0ef3dc6393" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2768264622-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MQsLUVVC7cJOe9aVARC%2Fuploads%2FZdqblFgTTq43nPY6Evfk%2Fimage.png?alt=media&#x26;token=c5d21dc3-57a4-4c5f-92bf-5482de640c76" alt=""><figcaption><p>ESD Protection components on UARTS</p></figcaption></figure>

## Software

UART3 may be accessed as a standard `/dev/ttyS_` in Linux.\
\<TODO-check wich ttyS number it is>&#x20;

##
