- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I rather think that wiced_dct_write_wifi_config_section should write the WIFI section, not the DCT section... As a GIT-style diff this is the fix:
diff --git a/WICED/internal/waf.c b/WICED/internal/waf.c
index 72e37bc..12b07b8 100644
--- a/WICED/internal/waf.c
+++ b/WICED/internal/waf.c
@@ -163,7 +163,7 @@ wiced_result_t wiced_dct_read_wifi_config_section( platform_dct_wifi_config_t* w
wiced_result_t wiced_dct_write_wifi_config_section( const platform_dct_wifi_config_t* wifi_config_dct )
{
- return wiced_dct_write( wifi_config_dct, DCT_SECURITY_SECTION, 0, sizeof( *wifi_config_dct ) );
+ return wiced_dct_write( wifi_config_dct, DCT_WIFI_CONFIG_SECTION, 0, sizeof( *wifi_config_dct ) );
}
I found it in 3.1.2, so it's probably been there for ages.
- Tags:
- bug sdk 3.3.1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I believe the DCT_SECURITY_SECTION is being used since we are writing to config section that needs to be secured with in DCT.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Vik86, go and look at the corresponding read function. Then perhaps you'd like to reconsider your answer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
include/wiced_framework.h
wiced_dct_read_lock
wiced_dct_read_unlock
wiced_dct_write
here you have the option to point to any section of dct to read/write.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.