- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.