I have a complicated project using SAMD21J18A MCU and BTLC1000-ZR BLE module.
My project uses EEPROM, via the ASF EEPROM emulation, for some non Bluetooth related parameters.
I just updated my project to ASF3.40 to get BluSDK6.2 which promises NVM storage of BLE bonding info so it does not forget the bonding every time the power cycles.
However I am having trouble getting this to work.
BluSDK6.2 uses the PDS (persistent data storage) service (rather than the EEPROM emulation service) to store the bonding info in the NVM(flash).
However when I updated my project using the ASF Wizzard the PDS files were not included in the project.
To try to get it to work I downloaded the ASF3.40 stand alone download and copied the PDS files into my project.
Now it compiles OK but PDS will not initialise successfully.
I have set the EEPROM fuses to allocate the maximum 16K of flash space to EEPROM.
So can the PDS and EEPROM emulation services co-exist?
If so how can I configure it so they share the available EEPROM emulation space in flash?
Or is there some trick I am missing to get this to work?
Thanks for any guidance you can give.