A new feature modemtrace has been added to LTE v2. When this is set to true, where is the modem trace data saved, and how can it be retrieved?
Additionally, is there a feature that allows logs to be saved in Chester’s non-volatile memory and retrieved remotely via the Hardwario Cloud?
Hello David,
I try to respond basics; I would like to ask @Karel to correct me or add something.
The modemtrace config parameter in the APP MCU will enable modemtrace functionality in the LTE MCU. It has to be configurable because it is more battery-heavy. Once it is enabled, we need (the same or another one) J-Link connected to the LTE, and AFAIK, the trace is read over RTT.
There is support in HARDWARIO CLI to store this logs on your computer, they can be later viewed by Wireshark.
Right now there is no functionality of saving modemtrace to flash, it is really a lot of data.
Modemtrace is really our internal way of troubleshooting different networks and weird behaviors.
Thank you, Martin.
Once I enable the modemtrace config parameter and connect a second J-Link to the LTE device, what command should I use in the HARDWARIO CLI to start recording the modem trace?
Regarding recording logs to flash, I wasn’t referring to modemtrace, but rather to other diagnostic data such as temperature, battery voltage, network connectivity status, and counts of data sent or commands received per day. Ideally, these would be recorded periodically—every hour, day, etc.—using a ring buffer approach to keep only the last x hours, days, or weeks of data.
If there’s any sample code or guidance on implementing this using LittleFS, I’d really appreciate it if you could share it.
@Karel can you please help David with that CLI command for modemtrace?
As far as I know we did not implemented any (circullar) logging to FLASH (FCB (Zephyr flash circular buffer) /LittleFS).