• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 844 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.

Linux/WL1837MOD: WL1837 SW integration in Linux guidelines

Guillaume Henri
Expert 4376 points

Part Number: WL1837MOD
Other Parts Discussed in Thread: WL1837

Tool/software: Linux

Hi champs,

My customer is developing a system based on microprocessor + WL1837 + LAN using Linux/Yocto solution. Boards have been already manufactured, after having validated kernel and Ethernet functionalities the customer is now starting to work on WL1837 wifi and BT aspects. The WL1837 is connected to the microprocessor (which is not TI and not a standard microprocessor) through Wifi SDIO / BT UART / WLAN_EN / BT_EN interfaces . For the moment, after having checked http://processors.wiki.ti.com/index.php/WL18xx_Platform_Integration_Guide page, other WL18xx/linux integration links and tried to integrate Wilink SW module within Linux, the customer could still could not see any signals activity on SDIO interface when activating wifi connection.

http://processors.wiki.ti.com/index.php/WL18xx_Platform_Integration_Guide integration guide assumes that the microprocessor is an AM335x machine. Is there any more precise and generic microprocessor document detailing WL1837 SW integration in Linux?

Is there also any guidelines detailing  what steps should be followed for WL1837 start up?

Thank you!

Best regards,

Guillaume

  • 0
    TI__Mastermind 35795 points
    Hi Guillaume,
    In one of the other posts you mentioned wireless interface comes up but stops working after 300 secs : e2e.ti.com/.../2876783

    Is it the same issue ? If yes, then seems like wireless interface is coming up ok but getting disabled . May be system is going in a state where it suspends/disable mmc/sdio or de-asserts GPIOs . Did customer refer to dts files of reference EVMs to port MMC/wlcore related mods :github.com/.../am335x-evm.dts

    Saurabh
  • 0 in reply to S
    TI__Expert 4376 points
    Hi Saurabh,

    Thanks for your answer

    This issue is different from the one refering to the wifi stop after 300sec. In this specific post, the SDIO pins never toggle and then it sounds like there is either a pin assignment or linux module integration issue. The customer seem to have checked the github.com link but as it is mentionned it is AM335x EVM specific. Isn't there any document detailing the same kind of precedure and aspects but not microprocessor dependant ?

    Thank you!

    BR,
    Guillaume
  • 0 in reply to Guillaume Henri
    TI__Mastermind 20285 points
    Hi Guillaume,

    The procedure of bringing up a wilink8 module is similar between TI hosts (Like the am335x) or other (like the imx6 for example) and is mainly dependent on the host mmc controller and how it is set up with regards to device tree initialization etc.

    See for example one integration page describing an IMX6 Sabre board:
    processors.wiki.ti.com/.../WL18xx_First_Time_Getting_Started_Guide_(IMX6)

    If the module is connected correctly to the host sdio bus, the board device tree is set correctly with all the relvant signals (sdio, wlan_enable, wlan_irq) and wlan_enable is powering the wl18xx modules, it should first be detected/enumerated by the linux mmc-core on the sdio bus when the kernel boot, even without having the load/start the wl18xx related modules .
    If that doesn't happen then something is not set correctly in either his device-tree settings or his hardware connection of the module.

    It is hard to give any more guidelines without detailed info about the exact setup and relevant kernel logs etc.

    Best Regards,
    Eyal