• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 41 subscribers
  • Views 2332 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

WL1831 - USB to SDIO Bridge

1886332
Expert 1325 points

Hi,

I am looking for a solution USB to SDIO Bridge and could not find in TI's information.

Can someone please share data on this?

Thanks.

  • 0
    TI__Guru* 85400 points

    Hi,

    I suggest that you check this on the Sitara forum.

    Regards,
    Gigi Joseph.

  • 0 in reply to Joseph Gigi
    Prodigy 110 points

    (I'm going to own that this is two years old...but necro-ing a thread that's germane...it's valid...)

    How can this be a valid suggestion, Gigi?  They were asking for a generic solution to tie a WiLink to a USB dongle, not docking the thing to a Sitara.  

    One of the unique things that you bring to the table is a proper Industrial solution for 802.11s.
    One of the other unique things that you bring to the table is multi-role such that I can do a MeshAP, a Meshpoint, dual ESSIDs for a mini AP, and the like.

    But...not all can use the SDIO interface.  Some are left working with nothing more than USB (Hint: X86 embedded solutions trend to NOT have MMC controllers on their SoC...but they *DO* happen to have USBs...LOTS of them.)

    One of my customers are lucky in that they are using Sitara.
    One of my other customers are unlucky in that they kind-of need the USB type functionality.  If only the driver could properly work with a USB to MMC/SDIO bridge...there could be an answer.

    I've one device that's very, very suboptimal that semi-sort-of does USB.  It's got a host of issues.

    I'd really, really like to have something that works with a VUB300, a Cypress Arroyo or similar.  Simple.  Linux supports those devices.  It tries to hotplug the WiLink via the SDIO interface rules...FAILS.  Current code expects to have OpenFirmware FDT data entries for the driver.  Hack around it some, giving it a binky in the form of a periodic (as in timer subsystem) check for a possible interrupt and the silly device resets itself and I get a -104 error from the MMC/SDIO layer underneath.  I'm moderately sure I can muddle through this on my own...does the team care to help give a bit of a hand for someone doing something slightly un-planned for...or is it something I'll have to cobble other answers to because it won't work without the OOB interrupt source correctly?