Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Based on the context provided, it seems like the custom device tree is not being utilized as expected. Here are some potential areas to investigate and verify:
-
Device Tree Compilation: Ensure that the custom device tree files are being compiled correctly. Check the build logs for any errors or warnings related to device tree compilation. It’s crucial to confirm that the custom device tree is being included in the final image.
-
Bootloader Configuration: Verify that the bootloader is configured to load the correct DTB file. If the bootloader is not loading the new DTB, the system will default to the original device tree. You can check the boot logs to see which device tree is being loaded.
-
File Paths and Naming: Double-check the paths and filenames in the
SRC_URIanddo_configuresteps to ensure they are correct. Make sure the files are being copied to the right locations in the build output. -
Build Process Verification: After building, confirm that the correct DTB is being loaded at boot time. This can be done by reviewing the boot logs to see which device tree is being loaded.
-
Integration Steps: Review the integration steps to ensure that the custom device tree is being referenced correctly in the kernel configuration and that there are no conflicting configurations in other layers.
-
Device Tree Inclusion: Ensure that the custom device tree file
gpio_verdin_plus.dtsis correctly included in the main device tree fileverdin_plus.dts. The inclusion should be properly referenced and not commented out or missing.
By focusing on these areas, you should be able to identify where the integration process might be failing and ensure that the custom GPIO names are recognized by the system.
Please, also check if these links can help you solve your problem: