Hi Nick,

Do to lack of resources we have backlogged this for now.

It seems possible, but I have still not found any working example.

-Danny

On Sun, Jan 3, 2016 at 8:38 PM, <[email protected]> wrote:

> Hey Danny,
>
> How did you go with this?
>
> I am looking at doing the exact same thing, any results yet?
>
> Cheers
>
> NP
>
> On Tuesday, 8 December 2015 03:41:55 UTC+11, [email protected] 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?
>>
>> I'm currently waiting for the device to begin testing, but I am surprised
>> to see that I could not find any resources or documentation of someone
>> interfacing with a 4 bit SDIO device on MMC2 while maintaining eMMC func on
>> MMC1
>>
>> Would love to hear if anyone has accomplished this already and how they
>> went about solving this problem.
>>
>> Cheers,
>> Danny Salzman
>>
> --
> For more options, visit http://beagleboard.org/discuss
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__beagleboard.org_discuss&d=CwMFaQ&c=cebXj8esxOo4m4Cl4YJe9I0vxXvmHhari4dCzmlv0WM&r=g17UCjL4dIN4JkyLUjxfRKJUAENw20oXhGMliao5bY4&m=rJoInbw9cuF8pQIWBeCv1fE4P9y39AQ-5B4HBPbqJec&s=ynQ53WwsaPaJJkMozS-uu4G06s1Spq3xBEs-7Lixs_k&e=>
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/RjL2gU2EvC0/unsubscribe
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_topic_beagleboard_RjL2gU2EvC0_unsubscribe&d=CwMFaQ&c=cebXj8esxOo4m4Cl4YJe9I0vxXvmHhari4dCzmlv0WM&r=g17UCjL4dIN4JkyLUjxfRKJUAENw20oXhGMliao5bY4&m=rJoInbw9cuF8pQIWBeCv1fE4P9y39AQ-5B4HBPbqJec&s=Rx-n57f0trd7h7X3x0X8ISiiTNm2LnKDfOsAm76ygC0&e=>
> .
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> For more options, visit https://groups.google.com/d/optout
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout&d=CwMFaQ&c=cebXj8esxOo4m4Cl4YJe9I0vxXvmHhari4dCzmlv0WM&r=g17UCjL4dIN4JkyLUjxfRKJUAENw20oXhGMliao5bY4&m=rJoInbw9cuF8pQIWBeCv1fE4P9y39AQ-5B4HBPbqJec&s=G-Wg3rBqoaovVNj8S-aQJtO4ZKFgy-CjHAkmoFkTge8&e=>
> .
>

-- 
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.

Reply via email to