nRF5340 DTM connection in Zephyr environment

RE: nRF5340 DTM connection in Zephyr environment

tgoos — Fri, 01 Dec 2023 12:59:43 GMT

Hi,

I had added the flag in all the possible places:

- boards/nrf5340dk_nrf5340_cpunet.conf

- child_image/remote_shell/prj.conf

- prj.conf

But it seems that I was using wrong file when flashing (merged.hex instead of merged_domains.hex). Now the DTM image in our custom board is communicating nicely.

Thanks for your help!

RE: nRF5340 DTM connection in Zephyr environment

Hung Bui — Fri, 01 Dec 2023 12:36:58 GMT

Hi,

Where did you put the CONFIG_NFCT_PINS_AS_GPIOS=y to ?

As I mentioned, the application core (which run remote shell) handles the UART part. So you need to set that to the remote shell application, not the DTM firmware itself.
Please try adding CONFIG_NFCT_PINS_AS_GPIOS=y into \child_image\remote_shell\prj.conf

If that doesn't help, please try to test blinky on your board if you can't modify the DK hardware.

RE: nRF5340 DTM connection in Zephyr environment

tgoos — Fri, 01 Dec 2023 11:14:04 GMT

Hi Hung,

Thanks for your response.

I tried the blinky example with led0 set to P0.03 in nrf5340dk_nrf5340_cpuapp.overlay:

/ {
        leds {
                compatible = "gpio-leds";
                led0: led_0 {
                        gpios = <&gpio0 3 GPIO_ACTIVE_LOW>;
                        label = "Green LED 0";
                };
        };
};

but the pin P0.03 seems to be idle (0V) all the time.

I may have found the root cause for this problem from ticket:
devzone.nordicsemi.com/.../nrf5340-use-nfc-pins-as-gpio-input

My nRF5340DK doesn't have the HW modification, so next week I'll ask our HW engineers to help me out with this and see if it helps.

Although, that doesn't explain why this is not working in our custom hardware.

RE: nRF5340 DTM connection in Zephyr environment

Hung Bui — Fri, 01 Dec 2023 09:19:18 GMT

Hi Teemu,
I'm taking over the ticket from Håkon.

If you do some simple test for example blinking the pin P0.03 as a normal GPIO pin, like in blinky sample, do you see any problem ?
If that works you can try the UART sample

After that you should try the remote IPC shell sample.

The DTM basically is a DTM firmware running on netcore and the remote shell running on app core. The output from the DTM firmware on the netcore is output to the remote shell and then to UART.

RE: nRF5340 DTM connection in Zephyr environment

tgoos — Fri, 24 Nov 2023 08:00:51 GMT

Hi Elfving,

I hope you are alright now.

I have an additional problem related to this. I'm now able to run the nRF Connect Desktop -> DTM app with nRF5340dk using different gpios, but unfortunately the ones that are in my custom board cause problems. Some similarities with this one: devzone.nordicsemi.com/.../nrf5340-dtm-serial-pin-modification-unsuccessful

My setup is:
P0.26 as UART RX
P0.03 as UART TX

UART RX is fine, but P0.03 as UART TX doesn't seem to operate correctly.

This is the NFCT dedicated pin, so using ncs v2.5.0 environment I've added:

&uicr {
    nfct-pins-as-gpios;
};

in the devicetree (assumed the child_image is the correct place, but tested the cpunet side too), but this doesn't solve the problem.
If I switch the wire and the devicetree setting to for example P0.09, the DTM app is connected and running smoothly.

Runnin the test with TX GPIO P0.09 (and P0.26 RX) in DTM app using TTL232R-3V3 serial connection:

09:45:50.320 No firmware defined for selected device
09:45:50.320 Please make sure the device has been programmed with a supported firmware
09:45:50.325 Device selected successfully
09:45:59.292 Running device setup
09:45:59.371 Starting test
09:46:06.390 Transmitter test finished successfully

After changing TX to P0.03:

09:47:52.951 No firmware defined for selected device
09:47:52.952 Please make sure the device has been programmed with a supported firmware
09:47:52.959 Device selected successfully
09:47:56.551 Running device setup
09:47:57.554 DTM setup reset command failed
09:47:57.554 Can not communicate with the device. Make sure it is not in use by another application and that it has a Direct Test Mode compatible firmware.

Is there now something else that I have to take into account in addition to nfct-pins-as-gpios -setting?
I've also tried the CONFIG_NFCT_PINS_AS_GPIOS=y, but get the compilation warning about deprecation.

RE: nRF5340 DTM connection in Zephyr environment

Elfving — Fri, 17 Nov 2023 14:51:14 GMT

Hello Teemu, and so sorry about the wait. I've been sick for a while.

I just had a look at this today, and found that I also had issues getting it to work with minicom for some reason.

I'm so glad you found a way around it. Have a good week-end!

Regards,

Elfving

RE: nRF5340 DTM connection in Zephyr environment

tgoos — Fri, 17 Nov 2023 10:10:55 GMT

Hi,

I've tested this with the nRF Connect for Desktop v4.2.1 -> Direct Test Mode app and was successful using the cpuapp uart: /dev/ttyACM1.

So the problem was probably that I assumed the cpunet (/dev/ttACM0) to be the one to use.

RE: nRF5340 DTM connection in Zephyr environment

tgoos — Mon, 06 Nov 2023 08:47:39 GMT

Thanks Elfving,

I have created an updated environment in a virtual ubuntu but with latest Zephyr (v3.5.0) and nRF Connect SDK v. 2.5.0

The result seems to be the same. So I must be doing something wrong.

RE: nRF5340 DTM connection in Zephyr environment

Elfving — Fri, 03 Nov 2023 14:08:31 GMT

Hello Teemu,

I will have to get back to you on this next week.

Regards,

Elfving