nRF52 DK board Bluetooth working

RE: nRF52 DK board Bluetooth working

Karl Ylvisaker — Wed, 03 Jan 2024 10:57:58 GMT

Hello,

I am glad to read that you have got the replacement board working as intended! :) So it does indeed look to be a hardware issue with the first board.
If you would like help to troubleshoot the faulty board you can open a separate ticket for this, so that we may advise you on which checks to perform (though if the board has been damaged by overvoltage or ESD then it can be hard to pinpoint the exact issue since the behavior could be erratic, and so it is not certain that we'll get to the bottom of the issue if this is the case).

Best regards,
Karl

RE: nRF52 DK board Bluetooth working

Timothy — Tue, 02 Jan 2024 13:57:13 GMT

this can be closed. It must be the original nRF52 DK board must have a hardware issue. The replacement board is working fine.

RE: nRF52 DK board Bluetooth working

Timothy — Tue, 02 Jan 2024 13:57:02 GMT

this can be closed. It must be the original nRF52 DK board must have a hardware issue. The replacement board is working fine.

RE: nRF52 DK board Bluetooth working

Øyvind — Wed, 27 Dec 2023 09:53:52 GMT

Hello,

We are severely understaffed this week because of the Christmas holidays, and Karl will have to get back to you on this next week. Sorry for the inconvenience.

Kind regards,
Øyvind

RE: nRF52 DK board Bluetooth working

Timothy — Fri, 22 Dec 2023 15:09:49 GMT

Karl

I heave received a new nRF52840 DK board and it is working with Bluetooth and cental_UART again. I believe it is a hardware problem. Is there any way to fix or reset the original nRF52 DK board so it will work. I will continue with the nRF52840 DK board but just wondering if the nRF52 DK board is slvagable.

RE: nRF52 DK board Bluetooth working

Karl Ylvisaker — Tue, 19 Dec 2023 16:09:21 GMT

[quote user="tjm1"]Karl the only thing that could be related was we had bad storms and a power outage. I also did think it was a hardware issue so I ordered another nRF52 DK board but I will not be able to test it until I get back. I did check my changes with the original peripheral_uart. I only added a few "printk" statements. I did not change any of the actual code.[/quote]

The fact that you have not modified the peripheral_uart sample before this happened also points in the direction of the hardware being the issue.
Testing on another board that has not faced the same operational conditions / potential damage is a great step as well. I look forward to hearing your results of this test!

[quote user="tjm1"]Karl Have a merry Christmas. If you get the Hallmark channel in Norway there is a very good new Christmas called "My Norwegian Holiday". It takes place in Bergen. beautiful scenery and a nice story.[/quote]

Thank you for saying so!
Bergen is a great place, but I am located a bit further north - luckily also with beautiful scenery! :D

Best regards,
Karl

RE: nRF52 DK board Bluetooth working

Timothy — Tue, 19 Dec 2023 15:54:01 GMT

Karl Have a merry Christmas. If you get the Hallmark channel in Norway there is a very good new Christmas called "My Norwegian Holiday". It takes place in Bergen. beautiful scenery and a nice story.

RE: nRF52 DK board Bluetooth working

Timothy — Tue, 19 Dec 2023 15:50:42 GMT

Karl the only thing that could be related was we had bad storms and a power outage. I also did think it was a hardware issue so I ordered another nRF52 DK board but I will not be able to test it until I get back. I did check my changes with the original peripheral_uart. I only added a few "printk" statements. I did not change any of the actual code.

RE: nRF52 DK board Bluetooth working

Karl Ylvisaker — Tue, 19 Dec 2023 15:46:47 GMT

[quote user="tjm1"]Karl Thanks for the quick response.[/quote]

No problem at all, I am happy to help! :)

[quote user="tjm1"]yes, this has been running for weeks and it stopped working with the EDAEDLK error when I made no modifications. I have reprogrammed it several times. The issue never goes away.[/quote]

If the problem persists through a reprogramming of the unmodified sample then it points in the direction of there being a hardware issue, but I do not immediately see a way for a deadlock in the bt_enable to be caused by the hardware.
Has there been any changes or damage to the hardware since the issue started occurring?

[quote user="tjm1"]I will; be away on vacation the rest of the week.[/quote]

No worries, we will continue this whenever you get a chance. I will also be out of office next week due to the national holiday here in Norway, but I will help you when I get back from holiday after new years.

Best regards,
Karl

RE: nRF52 DK board Bluetooth working

Timothy — Tue, 19 Dec 2023 15:14:57 GMT

Karl Thanks for the quick response. I believe the only modification I added was some print statements but I will reload the original untouched and try again. yes, this has been running for weeks and it stopped working with the EDAEDLK error when I made no modifications. I have reprogrammed it several times. The issue never goes away.

I will; be away on vacation the rest of the week. When I come back I will reload the original and start over again. Thanks for your help.

RE: nRF52 DK board Bluetooth working

Karl Ylvisaker — Tue, 19 Dec 2023 15:08:58 GMT

Hello,

[quote user=""]This has been connecting and transferring text strings back and forth for a few weeks. It stooped working and now all I get is the 4 leds lit in the error function. I added some print statements so I can see where it failed. I have included the printout below. It fails on the third step when it calls bt_enable(NULL). The error message is EDEADLK (-45). any idea what this means and how I can get the board working again? It was running flawlessly for a few weeks.[/quote]

Are you saying that you were running the unmodified peripheral UART example fine for weeks, and then without making any modifications to the application it stopped working with the EDEADLK error upon every boot, do I understand this correctly?
If I do understand it correctly: does the issue go away for some time if you reprogram the device?
If I do not understand it correctly: please elaborate on the changes you have made to the sample, and which changes you made most recently when this error started to appear.

Best regards,
Karl