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.
Did you like my answer? 
Hello mvo,
Thank you for your detailed questions regarding the Ivy board LED control and SODIMM pin usage.
1. Is SODIMM 54 multiplexed?
Yes, SODIMM pin 54 is multiplexed. While the schematic for your carrier board may only show a single function being used (for example, as GPIO), the Verdin module datasheet indicates that this pin is capable of multiple functions depending on the SoC’s internal pin multiplexing options. The exact function of SODIMM 54 is determined by the module’s device tree and pad mux configuration, not by the carrier board alone.
For more detailed pinout and muxing info, see the Verdin modules documentation:
Verdin iMX8M Plus Pinout and Functions
2. Why don’t SODIMM 30, 32, 34, and 54 appear in gpioinfo?
These pins are not showing up in gpioinfo because they have not been configured as GPIOs in your device tree overlays. For pins to be available as GPIO in Linux (and therefore visible to gpioinfo), their multiplexer (pad mux/pinmux) setting must select the “GPIO” function, and the pin must be described in your device tree as a usable GPIO.
How to solve this:
- Create a Device Tree Overlay to configure SODIMM 30, 32, 34, and 54 for GPIO function.
- Deploy and apply the overlay to your system.
- Upon reboot, these pins should now show up in
gpioinfoas expected.
For step-by-step device tree overlay instructions and examples for configuring these pins, see:
How to Use SODIMM Pins as GPIO on Verdin iMX8M Plus
If you’d like, I can guide you through a basic example of creating a device tree overlay for these pins.
Please let me know if you want more detailed instructions or if you have additional questions!
Best regards,
Toradex AI Assistant.