Direct test mode for DK nRF5340 :: Illegal value 0x21001238 written to register 66 (MSP_NS) ignored

[KVo]

Hi,

I am using nRF 5340DK borad, trying to flash Direct test mode sample "nordic,nrf5340-dk-nrf5340-cpunet". My aim is the enable direct test mode on the nrF board in order to test Constant tone extension features of BT 5.1 specs.

I downlaoded the direct test mode code from examples samples , it compiled successfully but when zephyr.elf file is downloaded to nRF 5340DK board it gives this error

Illegal value 0x21001238 written to register 66 (MSP_NS) ignored

Can you suggest alternative way to flash right firmware to test.

Can Nordic support team or someone please upload possibly the DTM firmware .elf or .hex or .bin file with your working setup.

Please also find attached snapshots for your reference. Can you please guide how can i get DTM on nRF 5340 or some issue in my setup will be appreciated.

thanks

[Amanda Hsieh]

Hi, 

The support staff is reduced during the summer holidays, and you may experience delayed answers.

I see the same issue on Segger, but our segger expert is on vacation. I will contact him when he is back in the office. 

I would suggest you use west to build and program the DTM sample. You could open command prompt from the tool manager:

Locate under  NCS\v1.6.0\nrf\samples\bluetooth\direct_test_mode and execute:

west build -b nrf5340dk_nrf5340_cpunet && west flash --recover

Locate under NCS\v1.6.0\nrf\samples\nrf5340\empty_app_core
west build -b nrf5340dk_nrf5340_cpuapp && west flash --recover

Then, you could test the DTM now. 

-Amanda 

[KVo]

Hi Amanda,

I tried exact steps as you mentioned and also were successfull, firstly i had to install nrf command tools and set correct environment paths manually.

Flasing of both steps was success : attached PIC

but still DTM commands are not working, can you help please. Are USB pins correctly configured in default project as nRF5340 DK board , can it be issue ?? How can i check

on Board i see following

TXD P.020 andP1.01

RXD P.022 and P1.00

are these pins same in the default program ?

thanks

[KVo]

Hi,

Thanks for explanation, I will try it again with --recover option if it works.

But atleast for now i have working solution.

Is it possible, some how to get solution also using the Segger embedded studio, which previously gave register 66 error.

perhaps if can also find solution for it too , would be also helpful.

thnaks

[Amanda Hsieh]

Hi,

KVo said:

Is it possible, some how to get solution also using the Segger embedded studio, which previously gave register 66 error.

Our segger expert is working on it. Please give us time. I will update the solution in the case. Sorry for any inconvenience. 

-Amanda H. 

[chcnuhk]

Hi Amanda,

As from above, you suggest using 'west' to build the code and download to nRF5340-DK board.

 would suggest you use west to build and program the DTM sample. You could open command prompt from the tool manager:

Locate under  NCS\v1.6.0\nrf\samples\bluetooth\direct_test_mode and execute:

west build -b nrf5340dk_nrf5340_cpunet && west flash --recover

Locate under NCS\v1.6.0\nrf\samples\nrf5340\empty_app_core
west build -b nrf5340dk_nrf5340_cpuapp && west flash --recover

Then, you could test the DTM now. 

Do you have experience on DTM code when using Segger Embedded Studio for both code?

BR, Charles

[Amanda Hsieh]

Hi Charles, 

There is the known issue while programming netcore with SES. Therefore, I suggest to use west build and flash for the DTM example in this post.  

Regards, 
Amanda 

[chcnuhk]

Hi Amanda,

I follow your suggestion but fail.

Locate under  NCS\v1.6.0\nrf\samples\bluetooth\direct_test_mode and execute:

west build -b nrf5340dk_nrf5340_cpunet && west flash --recover

Below is my procedure.

in toolchain, run git-cmd.cmd to enter DOS prompt.

Then, locate direct test mode.

Then execute below:

west build -b nrf5340dk_nrf5340_cpunet && west flash --recover

It fails and have below screen shot. Do you have any suggestion to me?

[chcnuhk]

Then, i try another Application code.

locate empty_app_core

Then execute below:

west build -b nrf5340dk_nrf5340_cpuapp && west flash --recover

It seems it can compile the code but fail to download it with below screen shot. Do you have any suggestion or comment to me?

BR, Charles

[Amanda Hsieh]

The error message in the first figure indicates that please check the board connection with PC.

The error log in the second figure, it seems you flash to network. 

Please create a new support case for your own issue. 

-Amanda

[TBing]

Hi I am experiencing similar problems:

• I am using the nRF5340DK board.
• I am using nRFConnect SDK v1.7.0.
• I have built and flashed the FW accordingly to Amanda´s instructions.
• I am able to connect to the DTM FW using RealTerm.
• I am not able to use the nRF Connect (Windows) Direct Test Mode Application to perform DTM operations.

When inspecting the enumeration of the virtual COM ports done by Windows, I noticed that the order is not as indicated by Amanda:

As you can see in the above screenshot the port that must be used (JLinkCDC1) is not the first COMx port.

I have two questions:

1) Is this arbitrary enumeration the reason why the "nRF Connect (Windows) Direct Test Mode Application" work for some but not  for others.

2) I have seen indications in another related support case, that kprint messages has to be removed - is this correct? (nRF Connect Direct Test Mode application doesn't work with nRF5340 - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com))

Regards Tonny

[Amanda Hsieh]

Hi Tonny, 

TBing said:

I am not able to use the nRF Connect (Windows) Direct Test Mode Application to perform DTM operations.

You need a second DK(nRF52 DK or nRF52840 DK) which is controlled by the DTM app in nRF Connect and then connect the terminal to nRF53 running NCS DTM example and manually send commands to it through the terminal. Please find instructions here: DTM Requirements .

TBing said:

1) Is this arbitrary enumeration the reason why the "nRF Connect (Windows) Direct Test Mode Application" work for some but not  for others.

While testing with the nRF Connect DTM app for Desktop, it doesn't need to connect the terminal of the second DK (nRF52 DK or nRF52840 DK). 

TBing said:

2) I have seen indications in another related support case, that kprint messages has to be removed - is this correct?

The nRF Connect for Desktop - DTM app only supports nRF52 DK or nRF52840 DK instead of nRF5340 now. I would not suggest to do that.  

If you have further questions or need assistance, please create a new support case for your own. 

Regards,
Amanda

[TBing]

Hi Amanda, sorry but I dont "get it".

Amanda wrote:
You need a second DK(nRF52 DK or nRF52840 DK) which is controlled by the DTM app in nRF Connect and then connect the terminal to nRF53 running NCS DTM example and manually send commands to it through the terminal. Please find instructions here: DTM Requirements .

I guess that the idea here is that e.g. the additional board could then be instructed to do some TX operation via the APP and the nRF5340 manually instructed to do a RX test? But, I could do that with a board from any vendor. Why is it not possible to control/test the nRF5340 from the APP?

You must understand that your customers expect to use the APP to verify the DTM FW provided by the SDK.

Once this has been verified, the actual DTM test is conducted using a real HW BLE analyzer.