• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 529 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2640R2F: Debugging Field Issues on CC2640R2F

Rahul Jose31
Prodigy 70 points

Part Number: CC2640R2F

I have been looking at all the debugging techniques available on the CC2640R2F and most seem to assume that a debugger is connected to the device. Is there any way to debug crashes detected in the field. Both for issues possibly within the stack as well as for issues caused due to defects in the application.

Is the inbuilt Non Volatile memory used for storing any kind of logs/core files etc?

  • 0
    TI__Guru** 105180 points
    Hello,

    Although we do not provide any examples of storing error or other diagnostic information, you can use the Simple NV (SNV) APIs to store custom data to NVM. Also, one way of implementing a panic logging mechanism is described in this post:
    e2e.ti.com/.../1982253

    Refer to the Flash Memory section of the BLE SW User's Guide in the SDK for more info on SNV usage.

    Best wishes
  • 0 in reply to JXS
    Prodigy 70 points
    Hi,
    Thanks for the response, what I wanted to understand is any diagnostic information stored by default by the TI/RTOS kernel or the BLE Stack without any additional code within the application program. Which can be later passed on to the TI team for additional debugging of core components. Ex - a core file which is generated etc.
    Regards,
    Rahul Jose
  • 0 in reply to Rahul Jose31
    TI__Mastermind 20480 points

    Rahul Jose31 said:
    Thanks for the response, what I wanted to understand is any diagnostic information stored by default by the TI/RTOS kernel or the BLE Stack without any additional code within the application program. Which can be later passed on to the TI team for additional debugging of core components. Ex - a core file which is generated etc.

    No, nothing is logged into any NV storage. Having an attached debugger is pretty much the preferred way to examine your code.