01
Temperature curve
The Pi starts near 56.8°C, rises above the 80°C region during sustained CPU load, and reaches 85.1°C before cooling quickly after the load stops.
Raspberry Pi 5 observability
Raspberry Pi 5 thermal dashboard for a CPU stress run.
An interactive Plotly dashboard showing temperature, firmware throttling flags, and cooldown behavior from a 10-minute four-core Raspberry Pi 5 load test.
Raspberry Pi 5
ARM64 Linux
Thermal flags
Plotly dashboard
Samples
694
Temperature and firmware flag observations.
Stress interval
10 minutes
Four-core CPU load followed by cooldown.
Baseline
56.8°C
Recorded before the load phase.
Peak
85.1°C
Observed near the end of the stress interval.
Power flags
No undervoltage
Thermal behavior, not a recorded power-supply event.
What it shows
Thermal behavior is easier to reason about when the firmware flags are visible.
The dashboard combines a temperature timeline with Raspberry Pi firmware throttling bitmasks. This makes the result more useful than a single peak temperature: it shows when the board crossed alert thresholds, when history bits latched, and when current throttling was actually captured.
02
Firmware protection flags
The plotted get_throttled states show soft-temperature, frequency-capping, and throttling history instead of treating the run as just a raw sensor trace.
03
Power-supply separation
No current or historical undervoltage bits were observed, so the recorded protection behavior is thermal in this run.
Interactive view
Explore the rendered dashboard.
Hover or tap inside the chart for exact values. The embedded dashboard keeps its own controls, zoom behavior, range slider, data tables, and export button.
The embedded asset is noindexed so search engines prefer this article URL.
Open dashboard in a separate page
Interpretation
The important signal is the plateau, not just the maximum temperature.
During the stress interval, the Pi enters the high-temperature region and records firmware protection history. Current Arm-frequency capping and current throttling were captured for 11 seconds. After the load ends, current flags clear while historical flags remain latched, which is expected for this class of firmware reporting.
Practical takeaway
The board handled the run, but sustained CPU work reached a firmware-controlled thermal plateau. For long-running Raspberry Pi workloads, this is the point where cooling, enclosure airflow, and workload scheduling become operational concerns.
Related work