AnsweredAssumed Answered

Is there a clash between the connectivity framework and FlexNVM?

Question asked by Stephen Langstaff on Sep 13, 2019
Latest reply on Sep 23, 2019 by Estephania Martinez

I'm looking at using the connectivity framework for some development on KW36, with FlexNVM used for some EEPROM emulation.


It appears from the KW36 reference manual that when the memory is partitioned for FlexNVM use then the EEPROM backup pages will be allocated from the top of DFLASH. Will this clash with the memory used for the hardwareParameters data structure?


Also, the OTAP boot loader documentation states that:

The OTAP Bootloader does not overwrite the last flash sector which contains the hardware-dependent data

If FlexNVM is in use then would the bootloader need to protect an area larger than the last flash sector?


Is the connectivity framework going to be updated to be aware of FlexNVM when partitioned for EEPROM emulation?