Ajay
Ajay
Hi @davidtekin37, From the logs, it seems the FW start is not received by the Host. Could you please probe the IRQ line from the WILC board? FW sends the...
Hi @dragon-123456 , From the shared description, it looks like the first SDIO command itself was failed. The driver module is loaded successfully. The purpose to keep "chip_en" high is...
I think bind/unbinding the driver should have solved this. This issue could be related to WILC device not initialized properly. I suspect there might be a problem with SD DAT[0-3]...
As you have confirmed that the failure happens for sdio_memcpy_fromio() issue so it might be good to check the host document to configure the SDIO node in the Device tree....
Hi @schb9 , Please verify with latest WILC v15.6 [driver](https://github.com/linux4microchip/linux/tree/linux-5.10-mchp/drivers/net/wireless/microchip) and [FW.](https://github.com/linux4wilc/firmware/releases/tag/wilc_linux_15_6). If you still face an issue then please open sales force ticket for this issue with more logs....
Apart from SPI pins connection, the WILC's RESET_N and CHIP_EN pins should be connected with host GPIO's for the power-up sequence. Assuming the SPI is correctly configured, this failure could...
It looks like the first SPI command from the host to the WILC has failed. First, check if the SPI bus communication is working fine. Either validate the Device Tree...
Hi @mmader87, We have recently added a [fix](https://github.com/linux4microchip/linux/commit/32e7037bd862187cc63369763240df5f4f167e0e#diff-343e667ba1215443fa4244a050fa766d84aebbc11f5365962bf1b851c73cb00e) for a similar issue in the latest WILCv15.6 [driver](https://github.com/linux4microchip/linux/tree/linux-5.10-mchp/drivers/net/wireless/microchip/wilc1000) In case you are still observing this issue, please try with the latest...
Hi @jbaker0428, It's very common to get different results for BT scan and totally depends on the availability of devices in the surrounding. The best way to confirm would be...
Good to know that the wilc3000 advertisement(as peripheral) worked for you. The scan mode didn't find the phone because it was not configured in advertisement mode. I missed to mention...