Forums » Software Development »
Using GPIO command on UBoot command line...is there any pin mapping between HPS pin # and GPIO pin #?
Added by Austin Franklin 1 day ago
Hi,
I have the CriticalLink UBoot image on a terminal program. There is the GPIO set/clear/toggle command. It wants a pin number. I have a logic analyzer on HPS GPIO 53 (pin 26 on the MitySOM connector). After UBoot comes up, that pin is high...not sure why...but anyway, I want to be able to set it high and low using the GPIO command. What would I use for pin # for the GPIO command? I of course tried 53, and it still stays high. I'm guessing one of two things. The UBoot image uses HPS GPIO 53 for something, so choose another pin or reconfigure UBoot...or there is some pin mapping involved. I noticed there is a Linux pin mapping...so I tried that, maps to 222...but the GPIO command told me that wasn't right...
Any help appreciated.
Best Regards,
Austin
Replies (1)
RE: Using GPIO command on UBoot command line...is there any pin mapping between HPS pin # and GPIO pin #? - Added by Austin Franklin about 2 hours ago
From Dan at CL (Thanks Dan!)
Our reference project has the following HPS IO set as GPIO:
- GPIO40 — edge pin 264 — SDMMC_D4/USB0_D4/HPS_GPIO40
- GPIO41 — edge pin 266 — SDMMC_D5/USB0_D5/HPS_GPIO41
- GPIO48 — edge pin 38 — TRACE_CLK/HPS_GPIO48
- GPIO49 — edge pin 34 — TRACE_D0/SPIS0_CLK/HPS_GPIO49
- GPIO50 — edge pin 32 — TRACE_D1/SPIS0_MOSI/HPS_GPIO50
- GPIO37 — edge pin 252 — SDMMC_PWREN/USB0_D1/HPS_GPIO37
- GPIO28 — edge pin 253 — HPS_GPIO28,BOOTSEL2/NAND_WE
And, these work using the UBoot "gpio toggle xx" command line command.
