Hi there,
Please see the video for a full run down: https://www.youtube.com/watch?v=nIeIUMutBlU
Basically, I have a perfect and verified design that's been in the works for nearly a year now using the Nordic nRF52810. We did a pre-production run, moving to the BMD-330 module which supposedly has a 52810 inside. This was to save on compliance certification and assembly costs. However, upon testing the boards, none of the Bluetooth related code is working on the chip - in fact, not only does the code "not work", it is causing the chip to hard-fault.
I am using Segger Embedded Studio, and just the basic Nordic SDK Code for the BLE UART Example (all BLE examples have this behaviour, but).
I know this question may be better redirected at Rigado themselves, but any help I can get through here would be greatly appreciated. You can see in the video, the code doesn't even reach the line to turn an LED on because it is crashing. Tracing through the debugger, this is the line of code causing the crash:
(in "nrf_sdm.h")
When this line of code is executed, the device is stuck in an infinite loop between these three lines of assembly code (I determined this from the disassembly window):
I know this is a very deep-rooted problem, but maybe it's something to do with clock sources or the SoftDevice API, and perhaps the Rigado module needs something to be disabled/enabled in the SDK setup code to work properly. Any help with this would be really appreciated - I love the support this forum gives, and I couldn't have made it this far through the development without the help I've received. Now, I just need this one last phase of support to help get the item to production - which is a great thing for Nordic, Rigado, and the future of our partnership with you guys.
Thank you!
