RE: peripheral uart sample: connecting causes permanent halting on background threads

droidecahedron — Thu, 10 Nov 2022 17:11:57 GMT

Thank you for reaching out Naeem,

My application no longer has this issue on SDK2.0.2

I do not have access to an nRF52840.

Our organization is pushing a product with nRF52833 and it is table stakes to use the 52833, so that is the platform the development needs to go on.

If it is any insight, when the bug was occurring, I noticed that immediately within the entry of the background thread, context switching would occur, which makes me wonder if in the new SDK some IRQ is throttling things.

Would be somewhere in ncs/version/zephyr/arch/arm/core/aarch32/swap.c/arch_swap(unsigned int) function.

RE: peripheral uart sample: connecting causes permanent halting on background threads

Naeem Maroof — Thu, 10 Nov 2022 16:39:49 GMT

Hi Johnny,

Thank you for contacting DevZone at NordicSemi.

So basically, you wanted to add a thread to peripheral uart sample.

I started with peripheral uart example in NCS 2.1.2, 2.1.1, and 2.1.0 and it did not work properly on 52833DK (DK was rebooting).

However, the same example in NCS 2.1.2, 2.1.1, and 2.1.0 worked properly on 52840DK without any modification.

Also, the same example in NCS 2.0.2 and 2.0.0 worked well on 52833DK. (There could be several reasons of a sample not working properly in a SDK for certain DK. I might not be aware about those.)

So as a first thing, can you start with peripheral uart in 2.0.2 on 52833DK?

Or if you have 52840DK then build and flash the same example using the latest (2.1.2) nCS.

I continued with 52840DK, and was able to incorporate the thread and see all of the functionality.

In the snapshot below, you can see that the thread is functional, and I am able to connect and disconnect and reconnect with the device. All of the LEDS were functioning properly as desired.

So, can you try your project with nCS 2.0.2, or on 52840DK?

Let me know accordingly.

(P.S: I have limited 52833 availability)

Regards,

Naeem