LAUNCHXL-CC26X2R1: Some issue about Persistent_app and NVS.

Hi Nick,

Thank you for reaching out. I have a few questions that may help  us resolve this as soon as possible. Can you provide the SDK version that the customer is using? Can you clarify in general terms what the customer is trying to accomplish with the NVS? I have found this E2E thread that may contain some helpful information. Can you check it and let me know if it is helpful? https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/807526/cc2642r-oad-persist-snv-pages

Best Regards,

Jan

Hi Jan,

Thanks for your quick response.

SDK is simplelink_cc13xx_cc26xx_sdk_7_10_00_98.

The purpose for customer is to change it to the AB partition, and read and write one sector NVS for A/B use. BIM should also be able to read and write this area (one byte is enough) to start the A/B partition.

Thanks and Regards,

Nick

Hi Nick,

Got it. I think that makes sense. Can you check if the E2E threads provided in my previous response are helpful for their request?

Best Regards,

Jan

Hi Jan,

Customer said that the E2E threads provided are not helpful for their request.

Thanks and Regards,

Nick

Hi Nick,

The Internal Flash Memory Layout section of the user's guide may be helpful here. Each image should have access to the NV. You can access the NV from any image. I would use a single NV page and reference the same page in your images.

Best Regards,

Jan