Your fix looks make sense to me.
The same fix is required for 3.3.1.
Hope someone from Broadcom can review and merge it.
I believe the DCT_SECURITY_SECTION is being used since we are writing to config section that needs to be secured with in DCT.
I don't get it.
So wiced_dct_read_wifi_config_section() read from DCT_WIFI_CONFIG_SECTION
and wiced_dct_write_wifi_config_section() write to DCT_SECURITY_SECTION.
How can it work?
Vik86, go and look at the corresponding read function. Then perhaps you'd like to reconsider your answer.
Andy, with in waf.c you are right the sections might be placed wrong, this is used within bootloader since its related to wiced application framework. But the api's that you need to refer are in
here you have the option to point to any section of dct to read/write.
I don't have a problem any more. the code on MY machine has been fixed. But you've published the source, and I rather thought it would help others using your chips if the fix made its way back into the next version of the SDK, so that nobody else has the problem in future.