> For the complete documentation index, see [llms.txt](https://dev.solid-run.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.solid-run.com/amd/ryzen-p100/com-som/amd-p100-com-express-type-6-hardware-documents/amd-p100-com-express-type-6-ic-power-dissipation-heatmap.md).

# AMD P100 COM Express Type 6 - IC Power Dissipation Heatmap

Interactive IC power dissipation heatmap for the AMD Ryzen AI Embedded P100 COM Express Type 6 module. Select power limit, memory, SSD and options to see heat sources and heat-sensitive parts.

Per-IC power dissipation of the AMD Ryzen AI Embedded P100 COM Express Type 6 module, colored by power density (log scale).

Use the **CPU Power Limit**, **LPCAMM2 module power**, **M.2 SSD power**, **Peripheral activity** and **Assembly options fitted** controls; the map, the totals and the heat-sensitive parts table follow the selection.\
Board 95 × 95 mm · 32 modelled parts top / 46 bottom · total estimated dissipation ≈ 87.4 W at the 54 W limit with an 8 W LPCAMM2 module, a 9 W SSD, datasheet maximum activity and all options fitted

{% @bios-viewer/bios-viewer url="<https://www.solid-run.com/power-heatmap/p100-com6-heatmap-v2.html>" %}

[Open the heatmap in a full browser window](https://www.solid-run.com/power-heatmap/p100-com6-heatmap-v2.html)

{% hint style="info" %}
**NOTE:**

* The CPU Power Limit selector covers 15 - 54 W (configurable TDP, default 28 W), in 1 W steps. The APU dissipation is modelled as equal to the selected sustained power limit. The automotive P122a and P132a parts have narrower ranges, as stated on the heatmap page.
* LPCAMM2 module power (3 - 8 W) and M.2 SSD power (0 - 9 W) are selectable inputs, not module data. Their heat is carried by the module or card and is drawn over its outline.
* Peripheral activity selects datasheet maximum or typical dissipation for the peripheral parts. Assembly options fitted adds or removes the optional parts (2.5GbE Ethernet, SATA bridge, LVDS display bridge, TPM 2.0, board temperature sensor, AMD debug header buffers, 156.25 MHz oscillator).
* Components that are not modelled (most passives, connectors) are shown as faint outlines. Hover a part to see its dissipation, the basis of the estimate and its datasheet thermal resistance.
* The BOTTOM side is an X-ray view from above and is not mirrored: it has the same orientation as the TOP side.
* The heat spread view is relative (1 = maximum of the selected view) and is not a temperature. By default it excludes the APU, the LPCAMM2 module and the SSD, which have their own heat paths (heatsink or spreader, module, card).
  {% endhint %}

{% hint style="warning" %}
**Estimate, not a thermal measurement.** Dissipation values are estimated from datasheet data and engineering assumptions at the selected settings, on the real placement and board stackup. No heatsink, heat spreader, airflow, enclosure or ambient temperature is modelled. Use this page for design guidance only, and validate thermal performance in the target system.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dev.solid-run.com/amd/ryzen-p100/com-som/amd-p100-com-express-type-6-hardware-documents/amd-p100-com-express-type-6-ic-power-dissipation-heatmap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
