SPI slave unresponsive after calling wiced_network_up on BCM94390

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Anonymous
Not applicable

Hi,

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.

Regards,

Hugh

0 Likes
1 Reply
VikramR_26
Employee
Employee
25 sign-ins 10 sign-ins 10 comments on KBA

Hey Hugh,

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.

Let us know if you have some luck.

hth

vik86

0 Likes