HI,
I build project direct_test_mode and empty_app_core and connect to PC softwarre DTM v2.
If build from ncs v1.9.1, it connect ok to show standby. but if build from ncs v2.2.0, DTM show NG.
Can you help me to verify it? something wrong?
HI,
I build project direct_test_mode and empty_app_core and connect to PC softwarre DTM v2.
If build from ncs v1.9.1, it connect ok to show standby. but if build from ncs v2.2.0, DTM show NG.
Can you help me to verify it? something wrong?
Hi,
Which nRF device are you compiling for?
Does DTM work in nRF connect for desktop application?
Kind regards,
Håkon
Hi,
1) HW is nRF5340-DK, UART is RX(P1.00), TX(P1.01)
2) I just test with nRF connect for Desktop still fail in ncs v2.2.0 image
Hi,
1) for ncs v2.2.0, I build direct_test_mode project, but I can not find RPC image in directory \direct_test_mode\child_image. Should I build following project to program mcu?
2) If I want to use ncs v1.9.1 first, my HW use P0.25 and P0.26, and have 4 antennas.
The origin overlay is:
Can I just change to
Is it ok?
Hi,
Felix Shih said:1) for ncs v2.2.0, I build direct_test_mode project, but I can not find RPC image in directory \direct_test_mode\child_image. Should I build following project to program mcu?
It is called "remote_shell" in your build-catalog.
Here's how the partition_manager_report looks for direct_test_mode in ncs v2.2.0:
flash_primary (0x40000 - 256kB): +----------------------------------+ | 0x1000000: app (0x40000 - 256kB) | +----------------------------------+ sram_primary (0x10000 - 64kB): +-------------------------------------------+ | 0x21000000: sram_primary (0x10000 - 64kB) | +-------------------------------------------+ CPUAPP flash_primary (0x100000 - 1024kB): +---------------------------------------+ +---0x0: app (0x100000 - 1024kB)--------+ | 0x0: remote_shell (0x100000 - 1024kB) | +---------------------------------------+ CPUAPP otp (0x2fc - 764B): +------------------------------+ | 0xff8100: otp (0x2fc - 764B) | +------------------------------+ CPUAPP sram_primary (0x80000 - 512kB): +-----------------------------------------------+ | 0x20000000: sram_primary (0x70000 - 448kB) | | 0x20070000: rpmsg_nrf53_sram (0x10000 - 64kB) | +-----------------------------------------------+
Felix Shih said:2) If I want to use ncs v1.9.1 first, my HW use P0.25 and P0.26, and have 4 antennas.
The origin overlay is:
That is possible, as per the documentation, which states that atleast one must be provided:
Kind regards,
Håkon
Hi,
I build DTM with ncs v1.9.1, and I only see P0.25 pin has a pulse, P0.26 is always low. Is it correct?
If it is wrong, how to fix?
DTM v2 setting:
UART monitor:
Hi,
Q1: Does it behave like this in ncs v2.2.0 at your end as well?
You can disable the remote_shell, and use empty_app_core (as previous) by setting this:
CONFIG_NCS_SAMPLE_REMOTE_SHELL_CHILD_IMAGE=n
Q2: Also, if you try to switch the GPIOs, dtm_antenna_1_pin =26 and _2_pin=25, does the issue follow the GPIO?
Kind regards,
Håkon
Hi,
Can you show me how to modify overlay file to use P0.25, P0.26?
It use the different format than ncs v1.9.1, and I will try it in the office tomorrow. Thanks!
Hi,
Can you show me how to modify overlay file to use P0.25, P0.26?
It use the different format than ncs v1.9.1, and I will try it in the office tomorrow. Thanks!