You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The logging system has a useful feature where a timestamp is prepended each log message.
This works well on single core MCU's, but in some situations you want to investigate multi-core applications. E.g. both cores crash, and you need to figure ut what took place first.
Suggest adding a config of type CONFIG_LOG_TIMESTAMP_SYNC. This will ensure that e.g. a LOG_DBG which is called on each core at the same point in time gets the same timestamp.
I realise that this is may well be far from trivial, as well as platform specific. @nordic-krch
The text was updated successfully, but these errors were encountered:
The logging system has a useful feature where a timestamp is prepended each log message.
This works well on single core MCU's, but in some situations you want to investigate multi-core applications. E.g. both cores crash, and you need to figure ut what took place first.
Suggest adding a config of type CONFIG_LOG_TIMESTAMP_SYNC. This will ensure that e.g. a LOG_DBG which is called on each core at the same point in time gets the same timestamp.
I realise that this is may well be far from trivial, as well as platform specific.
@nordic-krch
The text was updated successfully, but these errors were encountered: