WL1835MOD: Custom board with WL1835MOD will not come up

Did, you verify the pin muxes in the DTS files?

Thanks

Yes they should be fine because the connection to the WL1835 is identical to that of the BBBW and the same image brings it up fine. But can you please clarify how that would affect the UART_DBG_BT line from being pulled high at startup? My understanding from the documentation is that this is the default configuration on power up and that line should immediately go high after power up without any interaction from the host processor/loading of the dts files. Is this incorrect?

Hi , BT_UART_DBG shutdown and after power state is PU : www.ti.com/.../wl1835mod.pdf .

Saurabh

Saurabh,

Yes and so can you give some reasons why BT_UART_DBG would not be pulled high after power up? We have nothing connected to this pin except for a test point. All I/O signals are being level shifted properly to 1.8V and both VBAT and VIO are stable and the correct voltage.

Dan

Dan ,
- Probably wl8 did not boot up properly in operational mode
- where do you exactly see the failure ? do you see kernel detect sdio card during system boot ?
- you had mentioned it times out - can you pls elaborate

Saurabh

We determined that the device in question was damaged.  Can enabling the chip without an antenna attached damage it?

Now WIFI comes up normally but bluetooth does not.  We see the following in the system logs:

May 23 17:19:58 beaglebone bb-wl18xx-bluetooth[2186]: Initialization timed out.

Interestingly the bluetooth gets enabled about 4 seconds into the kernel loading and stays enabled from then on (and doesn't get pulsed at any point), but using the same linux image on the Beaglebone black we notice that bluetooth isn't enabled until much later and usually right at the same time as the WIFI

Saurabh,

BT still not working per previous post:

May 23 17:19:58 beaglebone bb-wl18xx-bluetooth[2186]: Initialization timed out.

Interestingly the bluetooth gets enabled about 4 seconds into the kernel loading and stays enabled from then on (and doesn't get pulsed at any point), but using the same linux image on the Beaglebone black we notice that bluetooth isn't enabled until much later and usually right at the same time as the WIFI

Which kernel version and file system are you using? 

Thanks

Debian 9.5.  It does look like the issue is that somehow the chips are getting damaged in the circuit.  Is it possible to share privately our schematic with you?

Daniel,

I am going to loop in our hardware team, and they will reach out on this post to look at your schematic.

BR,

Vince 

Hi Daniel,

You may email your design files here for review: wifi-dualmodebt-hw-reviews@list.ti.com

Thanks,

Alexis

Alexis,

Great - email sent.

Thanks,

Dan