Part Number: WL1837MOD
Hi,
Does the WL1837MOD have a device ID or some other identifying information that I can access over the SDIO and UART ports in order to test these interfaces prior to running the full software stack?
Thanks - Jason
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.
Part Number: WL1837MOD
Hi,
Does the WL1837MOD have a device ID or some other identifying information that I can access over the SDIO and UART ports in order to test these interfaces prior to running the full software stack?
Thanks - Jason
Jason,
I am assuming you are running Linux . If yes, you may rely on WiLink8 SDIO driver and MMC/SDIO stack to detect the SoC.
If properly detected , you should see message similar to following during boot up"
"mmc1: new high speed SDIO card at address 0001"
Regards
Saurabh
Currently our Linux boot hangs with no information about what is not working (it booted fine before we added support for this device). Therefore I would like to be able to debug the HW interface using simple reads and writes.
Thanks - Jason
Jason ,
I don't believe we have a document detailing WiLink8 SoC registers and expected values. As a first step you will need to ensure that the SoC is powering up ok. Pls refer to power up sequence in the datasheet : https://www.ti.com/lit/ds/symlink/wl1837mod.pdf
Also , you may use RTTT tool on Windows PC to test WLAN IP on the SoC using RS-232 interface :https://www.ti.com/lit/ds/symlink/wl1837mod.pdf
Regards
Saurabh
Thank you. I have decided that I should be able to monitor the SD CMD/CLK /DATA lines during Linux boot in order to determine if the HW interface is operating properly. So far it looks like the expected CMD sequence and tuning occur, so we are looking closer into whether the OS image has all the necessary ingredients.
Regards - Jason