Errors in DMESG log after changes in device tree

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:


To address the boot errors you’re encountering after disabling the SDHC1 controller and SPI CS line in the device tree, you will need to modify the Torizon OS image to prevent the initialization of these components. Here are the steps you can follow:

  1. Identify Initialization Blocks:

    • Review the boot code and initialization scripts in the Torizon OS image to locate the sections responsible for initializing the SDHC1 controller and SPI CS line. This might involve looking into the kernel configuration or startup scripts that handle hardware initialization.
  2. Modify the Boot Code:

    • Edit the relevant source code or configuration files to ensure that the system does not attempt to initialize these components. This could involve:
      • Commenting out or removing the initialization code for the SDHC1 controller and SPI CS line.
      • Adjusting the conditions under which these components are initialized based on their status in the device tree.
  3. Rebuild the OS Image:

    • After making the necessary changes, rebuild the Torizon OS image to apply the modifications. This process typically involves using the Yocto Project build system to compile the modified source code into a new OS image.
  4. Test the Changes:

    • Boot the modified OS image and check the dmesg log for any remaining errors related to the disabled components. Ensure that the system no longer attempts to initialize the SDHC1 controller and SPI CS line.
  5. Documentation and Support:

    • Consult the Torizon OS documentation or support resources for specific guidance on modifying the boot code and rebuilding the OS image, as this process may vary based on the version and configuration of Torizon OS you are using.

By following these steps, you should be able to prevent the system from attempting to initialize the disabled components, thus eliminating the associated boot errors.

Please, also check if these links can help you solve your problem:

Custom image 5.7.2 with overlay.