nRF53 Direct Test Mode Question

[gfgf2400a]

Hi,

I followed https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/direct_test_mode/README.html to work with nRF5340 DK PCA10095. I am using latest nRF connect v2.3.0 with no change of board "nrf5340dk_nrf5340_cpunet".

Because nrf5340dk_nrf5340_cpunet.overlay, ncs,dtm-uart is uart0 therefore I connect FTDI TTL-232R-3V3 to nRF5340 UART0 pins.

UART0		FTDI
TX	P0.20	RX	Yellow
RX	P0.21	TX	Orange
RTS	P0.18	CTS	Brown
CTS	P0.16	RTS	Green
GND		GND	Black

In prj.conf:

# Configure assertions

CONFIG_ASSERT=y

CONFIG_ASSERT_NO_COND_INFO=y

CONFIG_ASSERT_NO_MSG_INFO=y

CONFIG_HW_STACK_PROTECTION=y

# Uart driver

CONFIG_SERIAL=y

CONFIG_CONSOLE=y

CONFIG_UART_CONSOLE=y

CONFIG_LOG=y

CONFIG_LOG_PRINTK=y

CONFIG_USE_SEGGER_RTT=n

CONFIG_LOG_BACKEND_RTT=n

CONFIG_LOG_BACKEND_UART=y

# Use necessary peripherals

CONFIG_NRFX_TIMER0=y

CONFIG_NRFX_TIMER1=y

CONFIG_NRFX_TIMER2=y

It seems the example uart0 device tree is not configured correctly for this board and main.c !device_is_ready(uart) is true as shown in below screenshot. I used Teraterm with baudrate 19200 and I had no activity. Please let me know what could be the problem here. Thanks.

[Jared]

Hi,

Can you share your build folder?

regards

Jared 

[gfgf2400a]

I double checked uart0 pins from GPIO port 0 for application core remote_shell. I saw zephyr boot string *** Booting Zephyr OS build v3.2.99-ncs2 ***. However, uart0 is not ready due to z_device_is_ready() uart0 dev->state->init_res is 32 while expecting 0 in below images.

UART0		FTDI
TX	P0.20	RX	Yellow
RX	P0.22	TX	Orange
RTS	P0.19	CTS	Brown
CTS	P0.21	RTS	Green
GND		GND	Black

From z_device_is_ready() uart0 dev->state->init_res is 32 while expecting 0

[Jared]

Hi Dennis,

I'm sorry for the late reply, 

I've been out of office,

Just to be clear I understand what you're trying to do:

Are you trying to get the debug logs out to UART instead of RTT when you run the DTM sample on your nRF5340 board?

Have you been able to run`and test the unmodified sample?

regards

Jared 

[gfgf2400a]

Hi Jared,

Yes, I am attempting to use the UART interface because that is the only interface for us to do radio direct test mode on our custom PCBA. I can't use RTT. My thought was UART versus RTT is just a minor configuration. Please let me know if this is not the case.

Thanks,

Dennis

[Jared]

Dennis,

I see, I don't think this is trivial as the UART peripheral for the netcore is already in use for the DTM commands.

regards

Jared 

[gfgf2400a]

Thanks for the clarifications, Jared. Since the radio direct test mode is a board level test, I could use SWD pins on my breakout boards for RTT. My first thought by reading main.c in application was UART was for the user interface. Now, I am seeing UART on the application is for interfacing to the network core. I will switch to RTT.

Thanks,

Dennis

[gfgf2400a]

Jared,

I switched to RTT and running on NRF5340 DK PCA10095. The only connections I have are J2 and J3. However, I still have UART device is not ready error. RTT trace:

Connected via RTT with settings mem-address:auto

SEGGER J-Link V7.82 - Real time terminal output
J-Link OB-nRF5340-NordicSemi compiled Dec 3 2021 15:46:49 V1.0, SN=1050031422
Process: JLink.exe
[00:00:00.000,793] <inf> ipc_uart: IPC service instance opened
[00:00:00.100,982] <err> ipc_uart: IPC endpoint bond timeout
*** Booting Zephyr OS build v3.2.99-ncs2 ***
Starting Direct Test Mode example
UART device not ready

[Jared]

Did you build the sample unmodified this time?

I tried flashing the unmodified sample to my nRF5340 development kit with the latest NCS v2.3.0 and was able to run it and view it on RTT:

regards

Jared 

[gfgf2400a]

Jared,

I flashed the unmodified to nRF5340 DK PCA10095 and viewed from Visual Studio Code RTT terminal. I don't think viewing from J-Link RTT viewer should make any difference but I will try it.

Thanks,