Colibri IMX6ULL SODIMM_99 pin issues in u-boot

[ToradexAI]

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

Did you like my answer?

---

Hello Simon,

It seems like you’re experiencing an issue with controlling the GPIO1_14 (SODIMM_99) pin in U-Boot on the Colibri iMX6ULL module. Given that the pin works correctly under the Linux OS, it suggests that the hardware is functioning properly and the issue is likely related to U-Boot configuration or initialization.

Here are a few steps you can take to troubleshoot and potentially resolve the issue:

1. Check Pin Multiplexing in U-Boot:
   Ensure that the pin is correctly configured as a GPIO in U-Boot. You can check the pin multiplexing settings in the U-Boot device tree files (imx6ull-colibri.dtsi, imx6ull-colibri-u-boot.dtsi, etc.). Look for the pin configuration and ensure it is set as a GPIO and not being used by another peripheral.

2. Check U-Boot GPIO Initialization:
   Verify that the GPIO subsystem is properly initialized in U-Boot. Sometimes, GPIOs might not be correctly initialized, leading to issues in setting or clearing them.

3. Check for Conflicting Configurations:
   Ensure that there are no conflicting configurations in the U-Boot device tree or board-specific files that might be affecting the GPIO1_14 pin.

4. Test with a Minimal U-Boot Configuration:
   Try testing with a minimal U-Boot configuration to isolate the issue. Disable any unnecessary peripherals or configurations that might be interfering with the GPIO.

5. Check U-Boot Version:
   Ensure you are using a stable and supported version of U-Boot. Sometimes, upgrading or downgrading U-Boot can resolve such issues.

6. Debugging:
   Add debug prints in the U-Boot GPIO driver code to trace the execution and see where it might be failing to set or clear the pin.

7. Compare with Working Pins:
   Compare the configuration and initialization of the problematic pin (GPIO1_14) with the other working pins (SODIMM 101, 103, 105). Look for any differences that might explain the issue.

If after these steps the issue persists, you might want to reach out to Toradex technical support for further assistance. They can provide more specific guidance and help you debug the issue in detail.

Best regards,
[Your Name]

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

Iris 2.0 LVDS setting help

Hi, Ive been running the T20 with Iris 1.1 to a 7" touch display and custom 20 pin LVDS cable. Iris 2.0 has added a 2 channel LVDS connector and I had to have a new cable made to accommodate. Now, when powering up the module, the screen slowly lights up but no graphics appear. In looking at the data sheets, I found the “Migrate Iris from 1.1 to 2.0” article https://developer.toradex.com/knowledge-base/migrate-from-iris-v11-to-v20 Here it shows to add the following code, but being new to CE, …

Device tree customization to support leds and buttons in imx6ull

Hello, I am trying to customize the default Device Tree in order to support LEDs and button handling from sys/class/leds and also receive button when pressed via GPIO polling, or interrupt including also debounce. I have tried modifiying the imx6ull-colibri-aster.dts, to include the SODIMM numbers related to it, but there are still some SODIMM pins I cannot find. This is my dts file so far: /* * Copyright 2017 Toradex AG * * This program is free software; you can redistribute it and/or mo…

Flashing RootFS from u-boot on Colibri IMX6ULL.