Part Number: CC3220SF
Dear TI,
I have an application running on CC3220MODASF device on a custom PCB. Up to now it was mainly used in development environments with easy access to the devices. The devices seem to work fine most of the time, but they still show some instability when running a long time (they are suddenly unresponsive, and need a reset). For some cases (e.g. no internet or lost server connection) I have already used (softy configured) Watchdog timer that will reset the device after a while, but apparently there are still some states/cases where the device stops functioning/crashes.
The main problem is that I don't know the reason that they are unresponsive. One reason could be a memory leakage that causes the device to run out of memory, causing it to be unresponsive. This is something that I should be able to analyze with the "Runtime Object View" tool on CCS even for shorter periods of time. I have planned to do this, but I would also like to analyze the last executions/ (UART) print statements of the device in order to check what it was doing to find the cause of the crash. However, this can only be done if I connect a debugging device before the application is actually crashed. In practice this is not feasible because the 'crashes' are too infrequent, so I am looking for alternatives. I have already looked into logging via MQTT, but the problem is that it would rely on an internet connection in order to log.
The most stable way that I can think of right now, is storing the logs into a persistent file on the device itself. This way I can take the crashed device and read out all the data (still have to figure out how that would be possible though) from the device storage. There is currently no (extra) external storage attached to the device on the custom PCB, so the only option is to do logging via the NWP on the SFLASH in that case. However, I am a bit afraid that the (most important) last few logs might not be writable to the device before it crashes. In that case there is no benefit to use this method at all.
I could not find a document/example that would tackle this problem or showing the possibilities to store the (UART) log print statements for monitoring/after-analysis, therefore I am asking on the forum what is the best suggested solutions are to tackle this problem.
Best regards,
MJ