Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
The error you’re encountering is likely due to a syntax issue in the fsl,pins property within fragment@1. Specifically, the way the pin configurations are written might be causing the Device Tree Compiler (DTC) to fail parsing the input tree.
Let’s take a closer look at the problematic section:
fragment@1 {
target-path = "/soc/pin-controller@30330000";
__overlay__ {
pinctrl_my_pins: my_pins {
fsl,pins = <
MX8MP_IOMUXC_SAI5_RXC__GPIO3_IO20 0x1c0, /* SODIMM_19 */
MX8MP_IOMUXC_SAI3_RXFS__GPIO4_IO28 0x1c0, /* SODIMM_21 */
MX8MP_IOMUXC_SAI3_RXC__GPIO4_IO29 0x1c0 /* SODIMM_256 */
>;
};
};
};
The issue might be with the comma at the end of the second line within the fsl,pins property. In Device Tree syntax, the comma is not required and might be causing the syntax error.
Try removing the comma and see if it resolves the issue:
fragment@1 {
target-path = "/soc/pin-controller@30330000";
__overlay__ {
pinctrl_my_pins: my_pins {
fsl,pins = <
MX8MP_IOMUXC_SAI5_RXC__GPIO3_IO20 0x1c0 /* SODIMM_19 */
MX8MP_IOMUXC_SAI3_RXFS__GPIO4_IO28 0x1c0 /* SODIMM_21 */
MX8MP_IOMUXC_SAI3_RXC__GPIO4_IO29 0x1c0 /* SODIMM_256 */
>;
};
};
};
If the issue persists, ensure that the target-path and the node names are correct and match the actual paths and names in your base device tree files. Additionally, verify that the MX8MP_IOMUXC_* macros are correctly defined and available in your include files.
If you continue to face issues, please provide more details about the exact error message and the context in which you’re applying the overlay.
Please, also check if these links can help you solve your problem: