radio test NCS nrf52820 and nrf21540

RE: radio test NCS nrf52820 and nrf21540

Muhammad Usman — Thu, 11 Aug 2022 15:08:43 GMT

Thank you so much!

RE: radio test NCS nrf52820 and nrf21540

Vidar Berg — Thu, 11 Aug 2022 13:48:56 GMT

I'm happy to help. So lets hope it's just a soldering issue and that you won't run into the same problem on other boards.

RE: radio test NCS nrf52820 and nrf21540

Muhammad Usman — Thu, 11 Aug 2022 08:57:37 GMT

Thank you so much for the response!

Yes, it might be a bad solder joint!

PCB design is exactly the same but with fresh PCB not with the failing board.

Again Thank you for your time and concern!

RE: radio test NCS nrf52820 and nrf21540

Vidar Berg — Thu, 11 Aug 2022 08:42:09 GMT

Hi,

Thanks for confirming. This clearly suggests that there is a problem with the crystal on this board. But what I don't understand is how it seemingly worked fine with the nRF5 SDK. Could there be a bad solder joint that causes the problem to become a bit intermittent?

[quote user="Muhammad Usman"]I tested the same custom board by soldering the nrf52833 instead of nrf52820 IC.[/quote]

The same as in same PCB design, or did you actually replace the nRF52820 with a nRF52833 IC on the failing board?

RE: radio test NCS nrf52820 and nrf21540

Muhammad Usman — Wed, 10 Aug 2022 12:42:28 GMT

Sorry, that was not worked with the peripheral_uart example. I tested with RTT viewer showing me this

RE: radio test NCS nrf52820 and nrf21540

Muhammad Usman — Wed, 10 Aug 2022 12:37:04 GMT

Hi ,Vidar Berg,

Thank you for your wonderful support! I just tested another custom board that only has the nrf52820 sodered without soldering the nrf21540 IC . This board is working fine for the uart_perpherial example. Can it be issue with the nrf21540?

Although, the same board/PCB I tested with nrf52833+nrf21540 worked fine with the same components stuffed.

Any expert opinion about that? again thank you for your time and help!

RE: radio test NCS nrf52820 and nrf21540

Vidar Berg — Wed, 10 Aug 2022 12:32:54 GMT

No problem! Could you try the same with the peripheral_uart example that worked earlier? It would be good to know what the startup time is.

Edit: I guess I misread your previous response. I thought it worked with peripheral_uart but failed with another application. Are you able to debug the application to confirm that it hangs in the while loop?

RE: radio test NCS nrf52820 and nrf21540

Muhammad Usman — Wed, 10 Aug 2022 12:30:50 GMT

Hi,

Again thank you so much for the support and response! I just tried as per your latest instructions. Same behavior not showing the clock startup time.

Thanks & Regards,

RE: radio test NCS nrf52820 and nrf21540

Vidar Berg — Wed, 10 Aug 2022 11:33:06 GMT

Please run the snippet before bt_enable() as you will not be able to access the CLOCK register after this function call. If you attempt to write to the CLOCK registers afterwards, you will get a fault exception due to the memory sandboxing enabled by the MPSL.

But use the snippet below instead this time:

	NRF_TIMER1->BITMODE = TIMER_BITMODE_BITMODE_32Bit << TIMER_BITMODE_BITMODE_Pos;
	NRF_TIMER1->TASKS_CLEAR = 1;
	NRF_CLOCK->EVENTS_HFCLKSTARTED = 0;
	NRF_TIMER1->TASKS_START = 1;
	NRF_CLOCK->TASKS_HFCLKSTART = 1;
	while(NRF_CLOCK->EVENTS_HFCLKSTARTED == 0);
	NRF_TIMER1->TASKS_CAPTURE[0] = 1;

	printk("HF Clock has started. Startup time: %d uS\n", NRF_TIMER1->CC[0]);

It measures the crystal's ramp up time.

RE: radio test NCS nrf52820 and nrf21540

Muhammad Usman — Wed, 10 Aug 2022 09:57:44 GMT

Hi,

Again thank you so much for the support and response! I just tried as per your instructions. Now the controller is not rebooting.

But when I tested it with the central_peripheral app (nrf52833DK). It is unable to connect and send and receive messages. And not printing the "HF Clock has started" message. means it stuck before that.

Thanks in advance!

RE: radio test NCS nrf52820 and nrf21540

Vidar Berg — Wed, 10 Aug 2022 07:39:28 GMT

Hi,

Thanks for the log. The assert shown here indicates that the HF crystal is not running when it should. As a test, please try to add the code below right before the call to bt_enable(); and let me know if the program is able to exit the while loop.

	NRF_CLOCK->EVENTS_HFCLKSTARTED = 0;
	NRF_CLOCK->TASKS_HFCLKSTART = 1;
	while(NRF_CLOCK->EVENTS_HFCLKSTARTED == 0);

	printk("HF Clock has started\n");

RE: radio test NCS nrf52820 and nrf21540

Muhammad Usman — Tue, 09 Aug 2022 20:19:05 GMT

Hi @Vidar Berg,

Thank you for the response! I attached the file.

RTT log
00> [00:00:00.046,508] <err> os: Current thread: 0x200020b0 (unknown)
00> [00:00:02.353,424] <err> fatal_error: Resetting system
00> [00:00:00.018,[00:00:00.018,585] <inf> fs_nvs: alloc wra: 0, fd0
00> [00:00:00.018,585] <inf> fs_nvs: data wra: 0, 20
00> [00:00:00.018,798] <inf> sdc_hci_driver: SoftDevice Controller build revision: 
00>                                          33 78 2a 18 20 f5 61 61  a6 8b 77 60 62 83 39 2a |3x*. .aa ..w`b.9*
00>                                          7c f1 14 e4                                      ||...             
00> [00:00:00.025,970] <inf> bt_hci_core: No ID address. App must call settings_load()
00> [00:00:00.026,000] <inf> peripheral_uart: Bluetooth initialized
00> [00:00:00.039,916] <err> mpsl_init: MPSL ASSERT: 112, 2152
00> [00:00:00.039,916] <err> os: ***** HARD FAULT *****
00> [00:00:00.039,947] <err> os:   Fault escalation (see below)
00> [00:00:00.039,947] <err> os: ARCH_EXCEPT with reason 3
00> 
00> [00:00:00.039,978] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000006  r2/a3:  0x00000005
00> [00:00:00.039,978] <err> os: r3/a4:  0x20001a78 r12/ip:  0x20005fc1 r14/lr:  0x00020e7b[0m
00> [00:00:00.040,008] <err> os:  xpsr:  0x41000018
00> [00:00:00.040,039] <err> os: Faulting instruction address (r15/pc): 0x00020e88
00> [00:00:00.040,039] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
00> [00:00:00.040,069] <err> os: Fault during interrupt handling
00> 
00> [00:00:00.040,100] <err> os: Current thread: 0x200020b0 (unknown)
00> [00:00:01.178,741] <err> fatal_error: Resetting system[0m
00> [00:00:00.[00:00:00.018,798] <inf> fs_nvs: alloc wra: 0, fd0
00> [00:00:00.018,798] <inf> fs_nvs: data wra: 0, 20
00> [00:00:00.019,012] <inf> sdc_hci_driver: SoftDevice Controller build revision: 
00>                                          33 78 2a 18 20 f5 61 61  a6 8b 77 60 62 83 39 2a |3x*. .aa ..w`b.9*
00>                                          7c f1 14 e4                                      ||...             
00> [00:00:00.026,153] <inf> bt_hci_core: No ID address. App must call settings_load()
00> [00:00:00.026,214] <inf> peripheral_uart: Bluetooth initialized
00> [00:00:00.037,139] <err> mpsl_init: MPSL ASSERT: 112, 2152
00> [00:00:00.037,139] <err> os: ***** HARD FAULT *****
00> [00:00:00.037,170] <err> os:   Fault escalation (see below)
00> [00:00:00.037,170] <err> os: ARCH_EXCEPT with reason 3
00> 
00> [00:00:00.037,200] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000006  r2/a3:  0x00000005
00> [00:00:00.037,231] <err> os: r3/a4:  0x20001a78 r12/ip:  0x20005fc1 r14/lr:  0x00020e7b
00> [00:00:00.037,231] <err> os:  xpsr:  0x41000018
00> [00:00:00.037,261] <err> os: Faulting instruction address (r15/pc): 0x00020e88
00> [00:00:00.037,261] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
00> [00:00:00.037,292] <err> os: Fault during interrupt handling
00> 
00> [00:00:00.037,322] <err> os: Current thread: 0x200020b0 (unknown)
00> [00:00:01.178,405] <err> fatal_error: Resetting system
00> [00:00:00.[00:00:00.018,676] <inf> fs_nvs: alloc wra: 0, fd0
00> [00:00:00.018,707] <inf> fs_nvs: data wra: 0, 20
00> [00:00:00.018,890] <inf> sdc_hci_driver: SoftDevice Controller build revision: 
00>                                          33 78 2a 18 20 f5 61 61  a6 8b 77 60 62 83 39 2a |3x*. .aa ..w`b.9*
00>                                          7c f1 14 e4                                      ||...             
00> [00:00:00.026,123] <inf> bt_hci_core: No ID address. App must call settings_load()
00> [00:00:00.026,153] <inf> peripheral_uart: Bluetooth initialized
00> [00:00:00.036,529] <err> mpsl_init: MPSL ASSERT: 112, 2152
00> [00:00:00.036,560] <err> os: ***** HARD FAULT *****
00> [00:00:00.036,560] <err> os:   Fault escalation (see below)
00> [00:00:00.036,590] <err> os: ARCH_EXCEPT with reason 3
00> 
00> [00:00:00.036,621] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000006  r2/a3:  0x00000005
00> [00:00:00.036,621] <err> os: r3/a4:  0x20001a78 r12/ip:  0x20005fc1 r14/lr:  0x00020e7b
00> [00:00:00.036,651] <err> os:  xpsr:  0x41000018
00> [00:00:00.036,651] <err> os: Faulting instruction address (r15/pc): 0x00020e88
00> [00:00:00.036,682] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
00> [00:00:00.036,712] <err> os: Fault during interrupt handling
00> 
00> [00:00:00.036,712] <err> os: Current thread: 0x200020b0 (unknown)
00> [00:00:01.178,771] <err> fatal_error: Resetting system
00> [00:00:00.018,[00:00:00.018,676] <inf> fs_nvs: alloc wra: 0, fd0
00> [00:00:00.018,707] <inf> fs_nvs: data wra: 0, 20
00> [00:00:00.018,890] <inf> sdc_hci_driver: SoftDevice Controller build revision: 
00>                                          33 78 2a 18 20 f5 61 61  a6 8b 77 60 62 83 39 2a |3x*. .aa ..w`b.9*
00>                                          7c f1 14 e4                                      ||...             
00> [00:00:00.026,123] <inf> bt_hci_core: No ID address. App must call settings_load()
00> [00:00:00.026,153] <inf> peripheral_uart: Bluetooth initialized
00> [00:00:00.041,809] <err> mpsl_init: MPSL ASSERT: 112, 2152
00> [00:00:00.041,809] <err> os: ***** HARD FAULT *****
00> [00:00:00.041,839] <err> os:   Fault escalation (see below)
00> [00:00:00.041,839] <err> os: ARCH_EXCEPT with reason 3
00> 
00> [00:00:00.041,870] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000006  r2/a3:  0x00000005
00> [00:00:00.041,900] <err> os: r3/a4:  0x20001a78 r12/ip:  0x20005fc1 r14/lr:  0x00020e7b
00> [00:00:00.041,900] <err> os:  xpsr:  0x41000018
00> [00:00:00.041,931] <err> os: Faulting instruction address (r15/pc): 0x00020e88
00> [00:00:00.041,931] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
00> [00:00:00.041,961] <err> os: Fault during interrupt handling
00> 
00> [00:00:00.041,992] <err> os: Current thread: 0x200020b0 (unknown)
00> [00:00:01.184,265] <err> fatal_error: Resetting system
00> [00:00:00.018,[00:00:00.018,371] <inf> fs_nvs: alloc wra: 0, fd0
00> [00:00:00.018,432] <inf> fs_nvs: data wra: 0, 20
00> [00:00:00.018,585] <inf> sdc_hci_driver: SoftDevice Controller build revision: 
00>                                          33 78 2a 18 20 f5 61 61  a6 8b 77 60 62 83 39 2a |3x*. .aa ..w`b.9*
00>                                          7c f1 14 e4                                      ||...             
00> [00:00:00.025,878] <inf> bt_hci_core: No ID address. App must call settings_load()
00> [00:00:00.025,909] <inf> peripheral_uart: Bluetooth initialized
00> [00:00:00.038,360] <err> mpsl_init: MPSL ASSERT: 112, 2152
00> [00:00:00.038,360] <err> os: ***** HARD FAULT *****
00> [00:00:00.038,391] <err> os:   Fault escalation (see below)
00> [00:00:00.038,391] <err> os: ARCH_EXCEPT with reason 3
00> 
00> [00:00:00.038,421] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000006  r2/a3:  0x00000005
00> [00:00:00.038,452] <err> os: r3/a4:  0x20001a78 r12/ip:  0x20005ef1 r14/lr:  0x00020e7b[0m
00> [00:00:00.038,482] <err> os:  xpsr:  0x41000018
00> [00:00:00.038,482] <err> os: Faulting instruction address (r15/pc): 0x00020e88
00> [00:00:00.038,513] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
00> [00:00:00.038,513] <err> os: Fault during interrupt handling
00> 
00> [00:00:00.038,543] <err> os: Current thread: 0x200020b0 (unknown)
00> [00:00:01.180,725] <err> fatal_error: Resetting system
00> [00:00:00.01[00:00:00.018,798] <inf> fs_nvs: alloc wra: 0, fd0
00> [00:00:00.018,798] <inf> fs_nvs: data wra: 0, 20
00> [00:00:00.019,012] <inf> sdc_hci_driver: SoftDevice Controller build revision: 
00>                                          33 78 2a 18 20 f5 61 61  a6 8b 77 60 62 83 39 2a |3x*. .aa ..w`b.9*
00>                                          7c f1 14 e4                                      ||...             
00> [00:00:00.026,123] <inf> bt_hci_core: No ID address. App must call settings_load()
00> [00:00:00.026,123] <inf> peripheral_uart: Bluetooth initialized
00> [00:00:00.044,464] <err> mpsl_init: MPSL ASSERT: 112, 2152
00> [00:00:00.044,494] <err> os: ***** HARD FAULT *****
00> [00:00:00.044,494] <err> os:   Fault escalation (see below)
00> [00:00:00.044,525] <err> os: ARCH_EXCEPT with reason 3
00> [0m
00> [00:00:00.044,555] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000006  r2/a3:  0x00000005
00> [00:00:00.044,555] <err> os: r3/a4:  0x20001a78 r12/ip:  0x20005fc1 r14/lr:  0x00020e7b
00> [00:00:00.044,586] <err> os:  xpsr:  0x41000018
00> [00:00:00.044,586] <err> os: Faulting instruction address (r15/pc): 0x00020e88
00> [00:00:00.044,616] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
00> [00:00:00.044,616] <err> os: Fault during interrupt handling
00> 
00> [00:00:00.044,647] <err> os: Current thread: 0x200020b0 (unknown)
00> [00:00:01.185,913] <err> fatal_error: Resetting system
00> [00:00:00.[00:00:00.018,798] <inf> fs_nvs: alloc wra: 0, fd0
00> [00:00:00.018,829] <inf> fs_nvs: data wra: 0, 20
00> [00:00:00.019,012] <inf> sdc_hci_driver: SoftDevice Controller build revision: 
00>                                          33 78 2a 18 20 f5 61 61  a6 8b 77 60 62 83 39 2a |3x*. .aa ..w`b.9*
00>                                          7c f1 14 e4                                      ||...             
00> [00:00:00.026,123] <inf> bt_hci_core: No ID address. App must call settings_load()
00> [00:00:00.026,153] <inf> peripheral_uart: Bluetooth initialized
00> [00:00:00.042,968] <err> mpsl_init: MPSL ASSERT: 112, 2152
00> [00:00:00.042,968] <err> os: ***** HARD FAULT *****
00> [00:00:00.042,999] <err> os:   Fault escalation (see below)
00> [00:00:00.042,999] <err> os: ARCH_EXCEPT with reason 3
00> 
00> [00:00:00.043,029] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000006  r2/a3:  0x00000005
00> [00:00:00.043,060] <err> os: r3/a4:  0x20001a78 r12/ip:  0x20005f09 r14/lr:  0x00020e7b
00> [00:00:00.043,060] <err> os:  xpsr:  0x41000018
00> [00:00:00.043,090] <err> os: Faulting instruction address (r15/pc): 0x00020e88
00> [00:00:00.043,121] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
00> [00:00:00.043,121] <err> os: Fault during interrupt handling
00> 
00> [00:00:00.043,151] <err> os: Current thread: 0x200020b0 (unknown)
00> [00:00:01.184,844] <err> fatal_error: Resetting system
00> [00:00:00[00:00:00.018,798] <inf> fs_nvs: alloc wra: 0, fd0
00> [00:00:00.018,798] <inf> fs_nvs: data wra: 0, 20
00> [00:00:00.019,012] <inf> sdc_hci_driver: SoftDevice Controller build revision: 
00>                                          33 78 2a 18 20 f5 61 61  a6 8b 77 60 62 83 39 2a |3x*. .aa ..w`b.9*
00>                                          7c f1 14 e4                                      ||...             
00> [00:00:00.026,123] <inf> bt_hci_core: No ID address. App must call settings_load()
00> [00:00:00.026,153] <inf> peripheral_uart: Bluetooth initialized
00> [00:00:00.043,426] <err> mpsl_init: MPSL ASSERT: 112, 2152
00> [00:00:00.043,426] <err> os: ***** HARD FAULT *****
00> [00:00:00.043,457] <err> os:   Fault escalation (see below)
00> [00:00:00.043,457] <err> os: ARCH_EXCEPT with reason 3
00> [0m
00> [00:00:00.043,487] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000006  r2/a3:  0x00000005
00> [00:00:00.043,518] <err> os: r3/a4:  0x20001a78 r12/ip:  0x20005fc1 r14/lr:  0x00020e7b
00> [00:00:00.043,518] <err> os:  xpsr:  0x41000018
00> [00:00:00.043,548] <err> os: Faulting instruction address (r15/pc): 0x00020e88
00> [00:00:00.043,579] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
00> [00:00:00.043,579] <err> os: Fault during interrupt handling
00> 
00> [00:00:00.043,609] <err> os: Current thread: 0x200020b0 (unknown)

Can you please go through it.

Thanks,

RE: radio test NCS nrf52820 and nrf21540

Muhammad Usman — Mon, 08 Aug 2022 12:22:04 GMT

Hi,

I already tested on another board MDBT50-DB-20. It's working fine. If this is the case then it should not work on MDBT50-DB-20.

RE: radio test NCS nrf52820 and nrf21540

Muhammad Usman — Mon, 08 Aug 2022 12:17:23 GMT

Hi,

Thank you! i will provide it soon .This is new for me so may take some time to reply!

Again thank you!

RE: radio test NCS nrf52820 and nrf21540

PaKa — Mon, 08 Aug 2022 11:59:53 GMT

Hi, Please note that this configuration is for EMULATING the nRF52820 device while using nRF52833 HW so the code compiled is to be run on the nRF52833. If you want to compile for the nRF52820 and run on the nRF52820 then you will need to change linker files+++++.

RE: radio test NCS nrf52820 and nrf21540

Vidar Berg — Mon, 08 Aug 2022 11:50:47 GMT

Hi,

Please try to open RTT Viewer and see if the crash log is shown there.

RE: radio test NCS nrf52820 and nrf21540

Muhammad Usman — Mon, 08 Aug 2022 11:08:25 GMT

Hi,

yes, I just tested, same results. rebooting continuously.

Regards,

RE: radio test NCS nrf52820 and nrf21540

Vidar Berg — Mon, 08 Aug 2022 10:05:40 GMT

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.

RE: radio test NCS nrf52820 and nrf21540

Muhammad Usman — Mon, 08 Aug 2022 09:47:31 GMT

Hi,

Thank you, nrf52833Dk_nrf52820.

thanks,

RE: radio test NCS nrf52820 and nrf21540

Vidar Berg — Mon, 08 Aug 2022 08:30:45 GMT

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?

RE: radio test NCS nrf52820 and nrf21540

Muhammad Usman — Sat, 06 Aug 2022 11:13:40 GMT

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!

RE: radio test NCS nrf52820 and nrf21540

Muhammad Usman — Fri, 05 Aug 2022 20:06:59 GMT

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

RE: radio test NCS nrf52820 and nrf21540

Muhammad Usman — Fri, 05 Aug 2022 18:33:31 GMT

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

RE: radio test NCS nrf52820 and nrf21540

Vidar Berg — Fri, 05 Aug 2022 16:00:22 GMT

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?

RE: radio test NCS nrf52820 and nrf21540

Muhammad Usman — Fri, 05 Aug 2022 15:09:00 GMT

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