How to memory debug the nrf52840 application?

[RitD]

How do I do memory debugging in the nrf52840 in the runtime, or trace the RAM in run time, also how do I do the profiling of the memory in the run time. How do I find out all the possible bugs that the system can lead into in the future because of the same application.

How do I get the execution profile, or the synchronisation of the threads in the application?
How do I get the complete understanding of how the running process looks like in the SOC while running the SDK application?
What is the surefire way to make sure that the application won't fail?

[Simonr]

Hi

I'm not sure I know what you mean by "memory debugging", but please check out this guide which explains all the basics of the debugging process on the nRF51 and 52 series.

To find possible bugs that an application might have in the future is very hard, and it's just a matter of testing all thinkable corner cases while debugging to see if you run into any issues. What SDK are you using for your application? The nRF5 SDK or the nRFConnect SDK? In the documentation of both there should be a good explanation of how it works and how it will run on an nRF52.

The best way to make sure that an application won't fail is thorough work and testing, and a clear understandable application code that makes it easy to find where issues might take root. 

Best regards,

Simon