Hi, I’m the Toradex AI Assistant.
I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.
Let me address your questions about the Ivy Plus carrier board and TPM configuration.
TPM Support on Ivy Plus Carrier Board
The Ivy Plus carrier board includes a TPM 2.0 IC on the SPI bus, which is one of the key differences from the standard Ivy board (1). According to the datasheet, the TPM component is part number SLM9670 on SPI_1, with GPIO1 (SODIMM 206) used for chip select (2).
Device Tree Configuration Issue
Your current tcbuild.yaml references imx8mp-verdin-nonwifi-ivy.dts, but this appears to be for the standard Ivy board, not the Ivy Plus variant. The TPM error you’re seeing suggests the device tree isn’t properly configured for the Ivy Plus’s TPM hardware.
Ivy vs Ivy Plus Differences
The key differences between the two boards are (1):
| Feature | Ivy (0175XXXX) | Ivy Plus (0178XXXX) |
|---|---|---|
| TPM | Not included | Included |
| FRAM | Not included | 32KB |
| Power Supply Range | 8 to 32V | 21 to 72V |
| CAN/RS-232/RS-485 | Non-isolated | Isolated |
| Analog Input | Non-isolated | Isolated |
Device Tree File Availability
Based on the available documentation, there are preliminary schematics available for both Ivy and Ivy Plus boards (3), but the sources don’t explicitly mention separate device tree files for the Ivy Plus variant. The community forum discussions suggest users have been working with custom device trees for the Ivy boards (4).
Recommendation
Since the Ivy Plus includes additional hardware (TPM, FRAM) not present in the standard Ivy board, you may need to:
- Verify if there’s a specific device tree file for Ivy Plus in your kernel sources
- If not available, create a custom device tree overlay that properly configures the TPM and other Ivy Plus-specific components
- Ensure the TPM driver and SPI configuration are properly enabled in your device tree
The TPM error (256) typically indicates a self-test failure, which could be due to incorrect device tree configuration or missing driver support.
Best regards, Toradex AI Assistant.