Flash data has not been read on SET_CONFIG_PARAMETERS_REQ when SecMem is disabled, thus remanent data is lost

Disabled SecMem requires the host to set a MAC address. When the Ap Task starts and no valid MAC has yet been set (which is common without SecMem), the flash contents are not read. Consequently, if, as shown in the SetConfig example, a sequence of packets is sent like:

• SET_MAC_ADDR_REQ/CNF
• SET_CONFIG_PARAMETERS_REQ/CNF
• CHANNEL_INIT_REQ/CNF

Then the remanent data will not have been read during SET_CONFIG_PARAMETERS_REQ, resetting the remanent data to all defaults (i.e. the contents of the SET_CONFIG_PARAMETERS packet).

Different packet sequence as workaround:

• SET_MAC_ADDR_REQ/CNF
• CHANNEL_INIT_REQ/CNF
• SET_CONFIG_PARAMETERS_REQ/CNF
• CHANNEL_INIT_REQ/CNF

Here, of course, host application has to distinguish between the two CHANNEL_INIT_REQ/CNF packets in its state machine