自定义BBB上的GPIO无法访问

你好 -
我们正在调试基于BBB RevC的新设计，我们已经淘汰了eMMC。
我分配了几个已经分配给eMMC数据线的GPIO，我无法操纵它们。
在BBB上，我可以在/boot/uEnv.txt中禁用eMMC覆盖，然后我可以访问我的gpios并进行响应。
在我的自定义板上（没有eMMC设计）我无法做到这一点。
当我在/boot/uEnv.txt中禁用eMMC覆盖时，该板突然无法启动。
我一直未能成功地使用引脚复用器将引脚模式更改为GPIO，我将在前面承认我可能没有采用正确的方法，但是config-pin命令适用于UART1。
我正在使用最新的debian拉伸物联网图像
debian @ beaglebone：〜$ uname
Linux beaglebone 4.14.67-ti-r73＃1 SMP PREEMPT 8月30日星期四00:08:52 UTC 2018 ARMv7l GNU / Linux
我需要分别控制gpio32，gpio34，gpio35和gpio36（分别为P8_25，P8_05，P8_06，P8_23。）这些都是MMC1_DATx引脚。
再次 - 如果我在具有相同内核的BBB上禁用/boot/uEnv.txt中的eMMC覆盖，我至少可以操纵gpio32（我没有费心去尝试其他的）。
但是，如果我将相同的uSD卡粘贴到我的自定义板上，突然它将无法启动，唯一的变化就是禁用eMMC覆盖。
在此先感谢您的帮助和建议
这是我的uEnv.txt文件：
debian @ beaglebone：〜$ cat /boot/uEnv.txt
#Docs：http：//elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
uname_r = 67年4月14日-TI-R73
＃UUID =
＃DTB =
### U-Boot叠加###
###文档：http：//elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays
### Master Enable
enable_uboot_overlays = 1
###
###覆盖eeprom的斗篷
＃uboot_overlay_addr0 = / LIB /固件/ .dtbo
＃uboot_overlay_addr1 = / LIB /固件/ .dtbo
＃uboot_overlay_addr2 = / LIB /固件/ .dtbo
＃uboot_overlay_addr3 = / LIB /固件/ .dtbo
###
###其他定制斗篷
uboot_overlay_addr4 = / LIB /固件/ BB-SPIDEV0-00A0.dtbo
uboot_overlay_addr5 = / LIB /固件/ BB-SPIDEV1-00A0.dtbo
＃uboot_overlay_addr6 = / LIB /固件/ BB-UART1-00A0.dtbo
＃uboot_overlay_addr7 = / LIB /固件/ .dtbo
###
### Custom Cape
＃dtb_overlay = / LIB /固件/ .dtbo
###
###禁用虚拟斗篷的自动加载（emmc / video / wireless / adc）
disable_uboot_overlay_emmc = 1
disable_uboot_overlay_video = 1
disable_uboot_overlay_audio = 1
＃disable_uboot_overlay_wireless = 1
＃disable_uboot_overlay_adc = 1
###
### PRUSS OPTIONS
### pru_rproc（4.4.x-ti内核）
＃uboot_overlay_pru = / LIB /固件/ AM335X-PRU-RPROC-4-4-TI-00A0.dtbo
### pru_rproc（4.14.x-ti kernel）
uboot_overlay_pru = / LIB /固件/ AM335X-PRU-RPROC-4-14-TI-00A0.dtbo
### pru_uio（4.4.x-ti，4.14.x-ti＆amp; mainline / bone kernel）
＃uboot_overlay_pru = / LIB /固件/ AM335X-PRU-UIO-00A0.dtbo
###
### Cape Universal启用
enable_uboot_cape_universal = 1
###
### Debug：禁用Cape的uboot autoload
＃disable_uboot_overlay_addr0 = 1
＃disable_uboot_overlay_addr1 = 1
＃disable_uboot_overlay_addr2 = 1
＃disable_uboot_overlay_addr3 = 1
###
### U-Boot fdt tweaks ...（60000 = 384KB）
＃uboot_fdt_buffer = 0x60000
### U-Boot叠加###
cmdline = coherent_pool = 1M net.ifnames = 0 quiet
＃如果出现edid真实故障，请取消注释下一行：
#cmdline = coherent_pool = 1M net.ifnames = 0 quiet video = HDMI-A-1：1024x768 @ 60e
＃在只读根文件系统之上使用overlayfs：
#cmdline = coherent_pool = 1M net.ifnames = 0 quiet overlayroot = tmpfs
## enable通用eMMC Flasher：
##确保安装了这些工具：dosfstools rsync
＃CMDLINE = INIT = /选择/脚本/工具/的eMMC / init-eMMC-flasher-v3.sh



以下为原文

        Hello -
We’re debugging a new design based on the BBB RevC where we’ve eliminated the eMMC.  I assigned several GPIOs that would have been allocated to the eMMC data lines and I cannot manipulate them.  On a BBB, I can disable the eMMC overlay in /boot/uEnv.txt and I get access to my gpios and they respond.  On my custom board (designed with no eMMC) I am unable to do this.  When I disable the eMMC overlay in /boot/uEnv.txt the board suddenly will not boot.  I’ve been unsuccessful in using the pin mux to change the pin modes to GPIO and I will admit up front I’m probably not be doing the right way but the config-pin commands worked for UART1.
I am using the latest debian stretch IoT image
      debian@beaglebone:~$ uname      Linux beaglebone 4.14.67-ti-r73 #1 SMP PREEMPT Thu Aug 30 00:08:52 UTC 2018 armv7l GNU/LinuxI need to control gpio32, gpio34, gpio35 and gpio36 (P8_25, P8_05, P8_06, P8_23 respectively.)  These are all MMC1_DATx pins.
Again - if I disable the eMMC overlay in /boot/uEnv.txt on a BBB with the same kernel I can at least manipulate gpio32 (I haven’t bothered to try the others).  However, if I stick that same uSD card into my custom board, suddenly it won’t boot and the only change has been to disable the eMMC overlay.
Thanks in advance for your help and suggestions
Here is my uEnv.txt file:
debian@beaglebone:~$ cat /boot/uEnv.txt#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0uname_r=4.14.67-ti-r73#uuid=#dtb=###U-Boot Overlays######Documentation: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays###Master Enableenable_uboot_overlays=1######Overide capes with eeprom#uboot_overlay_addr0=/lib/firmware/.dtbo#uboot_overlay_addr1=/lib/firmware/.dtbo#uboot_overlay_addr2=/lib/firmware/.dtbo#uboot_overlay_addr3=/lib/firmware/.dtbo######Additional custom capesuboot_overlay_addr4=/lib/firmware/BB-SPIDEV0-00A0.dtbouboot_overlay_addr5=/lib/firmware/BB-SPIDEV1-00A0.dtbo#uboot_overlay_addr6=/lib/firmware/BB-UART1-00A0.dtbo#uboot_overlay_addr7=/lib/firmware/.dtbo######Custom Cape#dtb_overlay=/lib/firmware/.dtbo######Disable auto loading of virtual capes (emmc/video/wireless/adc)disable_uboot_overlay_emmc=1disable_uboot_overlay_video=1disable_uboot_overlay_audio=1#disable_uboot_overlay_wireless=1#disable_uboot_overlay_adc=1######PRUSS OPTIONS###pru_rproc (4.4.x-ti kernel)#uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo###pru_rproc (4.14.x-ti kernel)uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo###pru_uio (4.4.x-ti, 4.14.x-ti & mainline/bone kernel)#uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo######Cape Universal Enableenable_uboot_cape_universal=1######Debug: disable uboot autoload of Cape#disable_uboot_overlay_addr0=1#disable_uboot_overlay_addr1=1#disable_uboot_overlay_addr2=1#disable_uboot_overlay_addr3=1######U-Boot fdt tweaks... (60000 = 384KB)#uboot_fdt_buffer=0x60000###U-Boot Overlays###cmdline=coherent_pool=1M net.ifnames=0 quiet#In the event of edid real failures, uncomment this next line:#cmdline=coherent_pool=1M net.ifnames=0 quiet video=HDMI-A-1:1024x768@60e#Use an overlayfs on top of a read-only root filesystem:#cmdline=coherent_pool=1M net.ifnames=0 quiet overlayroot=tmpfs##enable Generic eMMC Flasher:##make sure, these tools are installed: dosfstools rsync#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

0