Please also share the results of these questions.
From the pinmux results you shared, it seems the pins are configured for ETH0 rather than GPIO.
If you want to control them manually, please configure them as GPIO through pinmux spreadsheet first.
Yes I tried.. that is what mdio_gpio node refers that .. from spreadsheet we configured and applied the patch. still no response .. do i need to check any H/W related one..??
I just need to know how you confirmed that it is configured to ETHO not gpio..
The following steps I shared on 24/Nov(i.e. MDIO and MDC as GPIO in Jetson orion AGX dev Kit - #17 by KevinFFF) is to control the GPIO from register directly. You should configure it as GPIO rather than other functions.
I just check the first bit of the pinmux register reading you shared.
You can check the TRM document for details.
No, the bit 10 should not be set if you want to use them as GPIO, the patch is required.
HI Kevin,
Is there any way to calculate the dev mem address of particular GPIO. Any formula available??
Hi Kevin,
Is it possible to provide commands to toggle below GPIO’s
- GPIO number 486 from GPIOCHIP-0
- GPIO number 27 from the GPIO header
It will great to validate what we are doing is correct or not .. as for these two I can probe and check.
You have to look up in TRM document.
Please refer to Calculating/Getting register adresses of gpio pins - #10 by KevinFFF for details.
I’m not clear the exact pins you want to check.
There’s no 486 from the result of gpioinfo.
Do you mean PAC.00?
gpio-486 (PAC.00 |
Please try to check the TRM document and I have an example above for PM.05.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.