Mirrors_Framework/nuttx
1
0
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2026-05-27 11:26:12 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

sched: add trace points during system startup and board initialization

Browse Source 
Add trace points to record transitions of g_nx_initstate and to mark
board early/late initialization boundaries. Also add trace marks for
RESET and PANIC to improve boot-time diagnostics and failure analysis.

Add OSINIT_RESET to indicate system is in reset process.

Signed-off-by: yukangzhi <yukangzhi@xiaomi.com>
This commit is contained in:
yukangzhi
2025-05-06 18:10:22 +08:00
committed by Xiang Xiao
parent 6ccc2fc7c8
commit 890f2e4625
6 changed files with 56 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Documentation/debugging/tasktraceuser.rst
+38
View File
@@ -357,3 +357,41 @@ If no command parameters are specified, display the current filter settings as t
11
15
System Startup and Board Initialization Trace
=============================================
NuttX has trace points during system startup and board initialization.
These trace points include:
- System startup phases (e.g., BOOT, TASKLISTS, MEMORY, HARDWARE, OSREADY, IDLELOOP)
- Entry and exit of board_early_initialize() and board_late_initialize()
- System RESET and PANIC events
This information helps analyze the boot process and locate issues related to board initialization or early system failures.
How to capture startup and board initialization trace
-----------------------------------------------------
1. **Ensure trace-related kernel configs are enabled** (see configuration section above).
2. **Boot the system normally**; the trace driver will automatically record these early trace points.
3. After boot, export the trace data with:
.. code-block::
nsh> trace dump boot_trace.txt
4. Open boot_trace.txt in Trace Compass. You will see the timeline of each phase, board early/late init boundaries, and RESET/PANIC events.
Common trace events during the startup
--------------------------------------
- ``sched_trace_mark("BOOT")`` : Entering BOOT phase
- ``sched_trace_mark("TASKLISTS")`` : Initializing task lists
- ``sched_trace_mark("MEMORY")`` : Memory manager available
- ``sched_trace_mark("HARDWARE")`` : Hardware resources initialized
- ``sched_trace_mark("OSREADY")`` : Multitasking ready
- ``sched_trace_mark("IDLELOOP")`` : Entering idle loop
- ``boards_trace_begin/end()`` : Entry/exit of board_early_initialize/board_late_initialize
- ``sched_trace_mark("RESET")`` : System reset
- ``sched_trace_mark("PANIC")`` : System panic
**Tip:** If you need to analyze boot or board initialization issues, always export and review the boot phase trace data first. This can help you quickly locate the problematic stage.