DEPRECATED: Updated Linux drivers for the ATWILC1000/ATWILC3000 products are located at https://github.com/linux4microchip/linux/tree/master/drivers/net/wireless/microchip/wilc1000. To simplify development, the legacy Linux4WILC was merged into the Linux4Microchip repo where driver development continues (Please refer latest ATWILC1000/ATWILC 3000 Wi-Fi Link Controller Linux User Guide) Driver code for Microchip ATWILC Wireless Devices (ATWILC1000 & ATWILC3000)
I see the below SPI DMA timeout when the driver gets loaded automatically during bootup. What appears to be happening is that wilc_spi_init() on the first attempt to read WILC_SPI_PROTOCOL_OFFSET is triggering the timeout. If I load the driver manually after the system is booted up, this SPI DMA timeout does not occur.
Regardless of when the driver gets loaded, CRC is turned off. Is that OK or does that indicated a deeper problem?
I see the below SPI DMA timeout when the driver gets loaded automatically during bootup. What appears to be happening is that
wilc_spi_init()
on the first attempt to readWILC_SPI_PROTOCOL_OFFSET
is triggering the timeout. If I load the driver manually after the system is booted up, this SPI DMA timeout does not occur.Regardless of when the driver gets loaded, CRC is turned off. Is that OK or does that indicated a deeper problem?