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 you are experiencing issues with setting a specific GPIO line using gpiod commands on your custom board. Here are a few potential reasons and steps to troubleshoot the issue:
-
Device Tree Configuration: Ensure that the GPIO pin you are trying to control is correctly configured in the device tree. If the pin is not muxed as a GPIO in the device tree, it will not function as expected. You may need to create or modify a device tree overlay to ensure the pin is set up correctly.
-
Pin Multiplexing: Verify that the pin is not being used by another function or peripheral. If the pin is multiplexed with another function, it may not be available as a GPIO. Check the pin’s configuration in the device tree and ensure it is set to GPIO mode.
-
Hardware Connections: Double-check the hardware connections on your custom board. Ensure that the pin is correctly connected and there are no hardware issues preventing it from functioning as a GPIO.
-
Permissions and Access: Make sure that the Docker container has the necessary permissions to access the GPIO lines. You have already provided access to the GPIO banks, but ensure that there are no additional permission issues.
-
Kernel Configuration: Check if the kernel configuration includes support for the GPIO you are trying to use. The
CONFIG_POWER_RESET_GPIOor similar configurations might be necessary depending on your specific use case.
If these steps do not resolve the issue, it might be helpful to review the device tree and kernel configuration in more detail or consult with Toradex support for further assistance.
Please, also check if these links can help you solve your problem:
Device Tree Customization/ Device Tree Overlays to Enable/multiplex GPIO.