Can you also post the content list of /boot/overlays directory on raspbian
toggle quoted messageShow quoted text
On Tue, Nov 17, 2020 at 4:29 PM Chuck Kamas <chuckkamas@...> wrote:
Thanks for taking the time to respond. I thought of that too. My custom
Yocto build has the line to turn on the sdio in it:
dtoverlay=sdio,poll_once=offI have attached the entire file: config.txt.yocto
However, the Rasbian image does not have any mention of the dtoverlay
for the sdio. Curious. See config.txt attached.
Thanks for the help!
On 11/17/20 12:08 AM, Khem Raj wrote:
On Mon, Nov 16, 2020 at 11:43 PM chuck kamas via
Hi all,what does /boot/config.txt look like on raspbian and yocto built images
I have been spinning my wheels for two days trying to discover how to
enable MMC1 on a CM3. This is the one on GPIO22-27. I can boot Rasbian
on the CM3 and it inits the MMC1 and its pins just fine. I can
read/write to my SD card from it etc. However, when I build yocto it
leaves the GPIOS22-27 in gpio mode and does not set them to MMC1 mode.
I have tried changing the device tree as described here:
That compiles and add the .dtbo to my build, but still the GPIOS are not
set to MMC1 mode.
cat /sys/kernel/debug/pinctrl/*gpio*/pinmux-pinsI have looked at:
Pinmux settings per pin
Format: pin (name): mux_owner gpio_owner hog?
pin 22 (gpio22): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 23 (gpio23): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 24 (gpio24): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 25 (gpio25): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 26 (gpio26): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 27 (gpio27): (MUX UNCLAIMED) (GPIO UNCLAIMED)
Any ideas of where to look next to turn on the sdio would be appreciated!