radio test NCS nrf52820 and nrf21540

[Muhammad Usman]

Hi All!

I am using NCS v2.0.0 and nrf52820 custom board and an example to test is radio test . I tested that example with nrf52833DK , code is executing/ printing messages on UART. But when I tested the same code by selecting the nrf52833_52820 then it was unable to run/ execute the code fully as it was with nrf52833. can you please help me in this regard?

Only this message on UART , after that no response when loaded program for nrf52820

But when i loaded the program for nrf52833 the program run properly as you can see the output it moves forward not stuck at the point where nrf52820.

Thanks in advance!

[Vidar Berg]

Hello,

Does your custom have the exact same UART pinout as the DK? I see you are able to receive messages so the TX pin must be correct, but it's not clear if the nRF is receiving your command input.

Ideally you should define new board files for your custom board (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/app_boards.html#custom-boards) and use that when building the sample. 'nrf52833dk_nrf52820' is not meant to be run on an actual 52820 IC.

Best regards,

Vidar

[Muhammad Usman]

Hello Vidar Berg 

Thank you so much for the response! Yes, UART pins are the same as that of DK. As receiving the messages. As you can see that nrf52820 stuck before the "clock has started" the message which was displayed by the nrf52833DK. 

Thank you for the link, I will follow it to find the issue and will update you further on this to configure the board according to the custom board configuration!

Thanks & Regards,

Muhammad Usman

[Vidar Berg]

Hello, 

I see. The problem might be related to the 32MHz crystal then. The «clock has started» message is printed when the HFXO has started. Or do the BLE examples work on your board?

[Muhammad Usman]

Hi Vidar Berg 

Thank you for the response! I just tried NCS (Uart_pheripheral and central) on a custom board(nrf52820 as peripheral) and nrf52833DK as central.

Nrf52820 is rebooting continuously with the following messages.

But when I tried the same example with nrf5 SDK it worked well! In this example, central was nrf52833DK, and peripheral was nrf52820 custom board. Both connected and communicated successfully!

Can you please help me in this regard where is the issue?

Thanks & regards,

Muhammad Usman

[Muhammad Usman]

Hi Vidar Berg !

I tried the same testing as mentioned above with MDBT50-DB-20. It worked fine with NCS (Uart_pheripheral and central) although communication was slow but it worked well! So what do you suggest where the problem is and how can we solve it?

Thanks & Regards,

Muhammad Usman 

[Muhammad Usman]

Hi Vidar Berg !

One more important observation, I tested the same custom board by soldering the nrf52833 instead of nrf52820 IC. And it's working well with  NCS (Uart_pheripheral and central) example as described above.

Now is it possible for you to diagnose the issue? I have created the three scenarios.

Thanks in advance!

[Vidar Berg]

Hi,

Interesting observations. It is probably not a crystal issue as you are able to use the board with the nRF5 SDK based example.

When you tested on MDBT50-DB-20, what board did you build for?

[Muhammad Usman]

Hi,

Thank you, nrf52833Dk_nrf52820.

thanks,

[Vidar Berg]

I'm quite surprised you consistently get the the spinlock assert when running the FW on your custom board, but not on the Rayac module.

Please try to build the UART peripheral sample with CONFIG_SPIN_VALIDATE=n and see if it still ends up crashing.