Hi,
there is a comment at the beginig of the ccfg_app.c file:
// // ===> READ THIS BEFORE MODIFYING THIS FILE // // // ===> READ THIS BEFORE MODIFYING THIS FILE // // // ===> READ THIS BEFORE MODIFYING THIS FILE // // The customer configuration area (ccfg section) is located at the end of the // flash and reflect the hw configuration of the device. it is very important // that it remains align with the version of driverlib you are using. // all BLE project except sensor tag use the same configuration. // Keeping the "#include <startup_files/ccfg.c>" guarantee that your project using // driverlib and the ccfg area will be align. // you can modify it if you want, the recommend way will be to remove the // bellow include, copy the content of the <startup_files/ccfg.c> file in this // file and rebuild. // ==> KEEP IN MIND that if you do so, be sure that any further update of the // driverlib must be align with your modified version of ccfg area.
There is also a comment in ccfg.c file:
// This file is part of the CoreSDK release and future releases may have // important modifications and new fields added without notice.
Current projects with OAD use CCFG from BIM (so CCFG came from the SDK on witch the device manufacturing FW is build).
Taking into account that CCFG "format" could be changed within future's SDK, how should be project with OAD capability implemented in order devices with bootloader based on today's SDK to work after upgrade of user app. in the future, with upgrade FW based on future SDK (with different CCFG "format")?
