Looking at those files I see that the wl1835 utilizes the MMC1 pins. I want to try and keep the MMC1 for the eMMC and only use the MMC2.
Does the Beaglebone Black support this from a HW point of view? I have not found any example of someone using the MMC2 bus. Cheers, Danny P.S. Thank you Robert for all your effort and time you put into the Beaglebone project! On Monday, December 7, 2015 at 10:53:47 AM UTC-6, RobertCNelson wrote: > > > > On Mon, Dec 7, 2015 at 10:41 AM, <[email protected] <javascript:>> > wrote: > >> Hi Ya'll, >> >> >> I am trying to interface a LSR TIWi-BLE wifi card with my Beaglebone >> Black. I would like to keep the on board eMMC functional so I cannot use >> MMC1. >> >> Looking at the Sitara datasheet and the Beaglebone black schematic it >> seems that all 6 wires needed for 4 bit SDIO SDIO are available on the >> header. >> >> MMC2_CLK -> 8.18 >> MMC2_CMD -> 9.15 (also attached to another input, would need to remove >> R160?) >> MMC2_DAT0 -> 8.12 >> MMC2_DAT1 -> 8.11 >> MMC2_DAT2 -> 8.16 >> MMC2_DAT3 -> 8.15 >> >> Do I just need to write an overlay to enable these pins for mmc function >> in the cape manager? >> > > the mmc layer in v4.1.x wasn't happy as an overlay, take a look at the > wl1835mod cape/board example: > > > https://github.com/beagleboard/linux/blob/4.1/arch/arm/boot/dts/am335x-boneblack-wl1835mod.dts > > https://github.com/beagleboard/linux/blob/4.1/arch/arm/boot/dts/am335x-boneblack-wl1835mod-cape.dtsi > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
