Skip to content

feat(ui): add dual-core task monitor in status bar and CPU info in device screen#2563

Open
r13xr13 wants to merge 1 commit into
BruceDevices:mainfrom
r13xr13:feat/dual-core-task-monitor
Open

feat(ui): add dual-core task monitor in status bar and CPU info in device screen#2563
r13xr13 wants to merge 1 commit into
BruceDevices:mainfrom
r13xr13:feat/dual-core-task-monitor

Conversation

@r13xr13

@r13xr13 r13xr13 commented Jun 18, 2026

Copy link
Copy Markdown

Summary

Two additions for visibility into the device runtime state:

Live core task counts in status bardrawDualCoreInfo() displays C0:N C1:N on the status bar, updated on each frame draw. Shows how many FreeRTOS tasks are running on each core at any moment.

CPU info in device screen — Device info now shows chip model, revision, core count, frequency, and core affinity breakdown (which tasks run on which core).

Changes

  • display.cpp: Add drawDualCoreInfo() function called from status bar
  • utils.cpp: Add CPU section in showDeviceInfo() with model/rev/cores/freq/affinity

Testing

  • Verified counts update in real time as tasks are created/destroyed
  • Works on single-core (C5) and dual-core (all Xtensa) configurations
  • Minimal overhead — uxTaskGetSystemState() call per frame draw

…vice screen

drawDualCoreInfo() displays live C0:C1 task counts on the status bar, updated on each frame. Device info screen now shows CPU model, revision, core count, frequency, and core affinity breakdown.

@Ninja-jr Ninja-jr left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have you tried this on a real physical device with a small screen?

I can almost guarantee it will look messy. The idea is good but has a big flaw...uses precious resources and redraw way too often.

@r13xr13

r13xr13 commented Jun 26, 2026

Copy link
Copy Markdown
Author

Have you tried this on a real physical device with a small screen?

I can almost guarantee it will look messy. The idea is good but has a big flaw...uses precious resources and redraw way too often.

image

@Ninja-jr

Copy link
Copy Markdown
Contributor

Ok I stand corrected. Looks ok.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants