Wi-Fi Combo Forum Discussions

Hello,

I was running a unit on WICED-SDK-3.7.0 but after upgrading WICED to 5.0.0 I face some problems running it,

however I see a difference in the DCT section as mentioned below .I saw also other discussion about an offset in DCT_APP_SECTION. , which I supppose is creating a problem

/* OLD DCT section */

typedef enum

{

    DCT_APP_SECTION,

    DCT_SECURITY_SECTION,

    DCT_MFG_INFO_SECTION,

    DCT_WIFI_CONFIG_SECTION,

    DCT_INTERNAL_SECTION, /* Do not use in apps */

    DCT_ETHERNET_CONFIG_SECTION,

    DCT_NETWORK_CONFIG_SECTION,

    DCT_BT_CONFIG_SECTION,

    DCT_P2P_CONFIG_SECTION,

    DCT_OTA2_CONFIG_SECTION,

    DCT_VERSION_SECTION, /* Do not use in apps */

} dct_section_t;

/* NEW DCT section */

typedef enum

{

    DCT_APP_SECTION,

   DCT_HK_INFO_SECTION,

    DCT_SECURITY_SECTION,

    DCT_MFG_INFO_SECTION,

    DCT_WIFI_CONFIG_SECTION,

    DCT_INTERNAL_SECTION, /* Do not use in apps */

    DCT_ETHERNET_CONFIG_SECTION,

    DCT_NETWORK_CONFIG_SECTION,

    DCT_BT_CONFIG_SECTION,

    DCT_P2P_CONFIG_SECTION,

    DCT_OTA2_CONFIG_SECTION,

    DCT_VERSION_SECTION, /* Do not use in apps */

    DCT_MISC_SECTION,

} dct_section_t;

Is there a  best practice for saving my old configuration before the update and restore it after ( due to differences in DCT )?

Also, I found this morning a new version of WICED (5.0.1) with this modifications :

   * [all WiFi] Speed up DCT reads by keeping track of current DCT verification

   * [all WiFi] Updated DCT padding to be multiple of 8-bytes for backward compatibility in OTA2

It is amendment can solve my problem ?