Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I'm using the 94390 as a slave to another microprocessor and am using SPI to control it. I started with the spi_slave app snippet and have successfully gotten the microprocessor to turn the LEDs on and off via SPI commands. I have extended the SPI slave registers to pass commands/data, e.g. ssid, password, and these work fine too. However, after I call wwd_wifi_join / wiced_network_up, the 94390 no longer responds to any SPI traffic. Is there anything particular about these functions that would cause the spi (SPI2) to stop functioning? Btw, I am using SDK 3.1.2.
Within 4390 there is an MCU and the 4390 radio, when you do wwd_wifi_join / wiced_network_up. The Host MCU talks to the 4390 radio over SPI and hence you see that the SPI is not functional anymore. Would suggest you to try with SDIO, that way MCU interfaces with 4390 using SDIO internally.