auracaster/hci_uart_iso_timesync
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update nRF5340 DK information

Browse Source
This commit is contained in:
Matthias Ringwald
2024-12-12 15:30:15 +01:00
parent b7dd60fd52
commit caffd7b8a1
1 changed files with 44 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

67
README.md
View File

@@ -17,27 +17,66 @@ It has been tested on the nRF5340 Audio DK, but it should work with any nRF5340
## nRF5340 Development Kit ## nRF5340 Development Kit
The first Virtual UART (UART1, ...) is Zephyr UART 1
The second Virtual UART (UART2, ...) is Zephyr UART 0
### Pinout
Signal direction as seen from the nRF5340.
| PIN | Arduino | MCU | Direction |
|----------|---------|-------|-----------|
| TX | D0 | P1.00 | out |
| RX | D1 | P1.01 | in |
| RTS | D7 | P1.11 | out |
| CTS | D8 | P1.10 | in |
| Time Sync| D10 | P1.06 | out |
### HCI over USB CDC ### HCI over USB CDC
```sh ```sh
west build --pristine -b nrf5340dk/nrf5340/cpuapp -- -DEXTRA_DTC_OVERLAY_FILE=usb.overlay -DOVERLAY_CONFIG=overlay-usb.conf west build --pristine -b nrf5340dk/nrf5340/cpuapp -- -DEXTRA_DTC_OVERLAY_FILE=usb.overlay -DOVERLAY_CONFIG=overlay-usb.conf
``` ```
### HCI over UART 0 connected to Virtual UART in J-Link Probe
### HCI over UART 0 connected to second Virtual UART in J-Link Probe
```sh ```sh
west build --pristine -b nrf5340dk/nrf5340/cpuapp west build --pristine -b nrf5340dk/nrf5340/cpuapp
``` ```
### HCI over UART 1 connected to Virtual UART in J-Link Probe - HCI over second Virtual port / UART 0
- Boot banner on Arduino Header UART (P1.01) / UART 1
### HCI over UART 1 connected to first Virtual UART in J-Link Probe as well as Arduino Headers
```sh ```sh
west build --pristine -b nrf5340dk/nrf5340/cpuapp west build --pristine -b nrf5340dk/nrf5340/cpuapp -- -DEXTRA_DTC_OVERLAY_FILE=uart1.overlay
``` ```
_HCI over UART 1 and timesync not tested._ - No Boot Banner on Arduino Header UART
## nRF5340 Audio DK ## nRF5340 Audio DK
The first UART (UART1, P1.04, P1.05) is only available via test points (TP60, TP61, ...)
The second UART (UART2, P1.08, P1.09) is connected to the Arduino headers.
### Pinout
Signal direction as seen from the nRF5340.
| PIN | Arduino | MCU | Direction |
|----------|---------|-------|-----------|
| TX | D0 | P1.09 | out |
| RX | D1 | P1.08 | in |
| RTS | D7 | P1.11 | out |
| CTS | D8 | P1.10 | in |
| Time Sync| D10 | P1.01 | out |
### HCI over USB CDC ### HCI over USB CDC
```sh ```sh
@@ -47,7 +86,7 @@ west build --pristine -b nrf5340_audio_dk/nrf5340/cpuapp -- -DEXTRA_DTC_OVERLAY_
### HCI over UART 0 connected to Virtual UART in J-Link Probe ### HCI over UART 0 connected to Virtual UART in J-Link Probe
```sh ```sh
west build --pristine -b nrf5340_audio_dk_nrf5340_cpuapp west build --pristine -b nrf5340_audio_dk/nrf5340/cpuapp
``` ```
### HCI over UART 1 connected to Virtual UART in J-Link Probe as well as Arduino Headers ### HCI over UART 1 connected to Virtual UART in J-Link Probe as well as Arduino Headers
@@ -64,22 +103,4 @@ west build --pristine -b nrf5340_audio_dk/nrf5340/cpuapp -- -DEXTRA_DTC_OVERLAY_
To use UART 1 via Arduino headers, the virtual UART of the J-Link probe needs to be disabled, e.g. with the JLink Configuration Tool. To use UART 1 via Arduino headers, the virtual UART of the J-Link probe needs to be disabled, e.g. with the JLink Configuration Tool.
### UART 1 Pinout
Signal direction as seen from the nRF5340.
| PIN | Arduino | MCU | Direction |
|----------|---------|-------|-----------|
| TX | D0 | P1.09 | out |
| RX | D1 | P1.08 | in |
| RTS | D7 | P1.11 | out |
| CTS | D8 | P1.10 | in |
### Time Sync Pinout
For time sync, Arduino header D10 is used, which uses different MCU pins on the Audio vs. the regular DK.
| Board | Time sync MCU Pin |
|------------------|-------------------|
| nRF5340 Audio DK | P1.01 |
| nRF5340 DK | P1.06 |