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)
Recently ran into a problem after migrating to 3.1.0 from 2.4.1
When WICED_DISABLE_MCU_POWERSAVE is defined, power-cycling the board will bring it into a state shown below:
Starting WICED v3.1.0
Platform BCM943362WCD4 initialised
Started ThreadX v5.6
Initialising NetX v5.7_sp1
Creating Packet pools
Could not set AMPDU parameters
Error 2 while starting WICED!
The application used is snip/apsta (same behaviour on other applications)
I am not sure whether this is related to platform restructuring in 3.1.0, and whether this is intentional/intended behaviour. My suspicion comes from the following statement in WICED/WWD/internal/chips/43362A2/wwd_ap.c:
"For SDK 3.0, and beyond, each chip will need it's own function for setting AMPDU parameters."
Any ideas, tips, or pointers to better understand the problem and why it's behaving this way is greatly appreciated.
Just adding a cross-reference to this thread: Are interrupts ever disabled by WICED? where using the WICED_DISABLE_MCU_POWERSAVE macro was suggested. I've tested the macro and confirmed the same behaviour described here -- radio fails to initialize properly following a power-reset when this macro is defined. Tests were performed using BCM943362WCD4, WICED 3.1.2, and "snip.apsta-BCM943362WCD4 download".