mirror of
https://github.com/espressif/esp-idf.git
synced 2025-09-26 02:00:26 +00:00
esp32: SEGGER SystemView Tracing Support
Implements support for system level traces compatible with SEGGER SystemView tool on top of ESP32 application tracing module. That kind of traces can help to analyse program's behaviour. SystemView can show timeline of tasks/ISRs execution, context switches, statistics related to the CPUs' load distribution etc. Also this commit adds useful feature to ESP32 application tracing module: - Trace data buffering is implemented to handle temporary peaks of events load
This commit is contained in:
@@ -780,9 +780,9 @@ static void prvCheckForValidListAndQueue( void )
|
||||
/* Check that the list from which active timers are referenced, and the
|
||||
queue used to communicate with the timer service, have been
|
||||
initialised. */
|
||||
|
||||
|
||||
/* Erm, yes, this is a problem. We can't lock until the lock is initialized, and we can't initialize the lock
|
||||
atomically because we don't have a lock yet... I'm pretty sure doubly-initializing a lock on 2 cpus
|
||||
atomically because we don't have a lock yet... I'm pretty sure doubly-initializing a lock on 2 cpus
|
||||
is no problem in the current implementation, but this is not a nice way to solve things. ToDo - improve. */
|
||||
|
||||
if( xTimerQueue == NULL ) vPortCPUInitializeMutex( &xTimerMux );
|
||||
|
Reference in New Issue
Block a user