CC2745R7-Q1: OAD Guide for Key_node project

Part Number: CC2745R7-Q1

I am continuing the discussion from the previous thread regarding adding OAD support to the Channel Sounding car_node and key_node projects.

I need further clarification on how to add OAD support to the existing key_node projects, rather than how to perform an OAD update using an already OAD-enabled project.

Specifically, I need guidance on the following:

1. Generating the .bin files for the key_node projects

   I have two versions of the key_node project (V1 and V2). I need to understand what changes are required in each project to make it OAD-compatible and how the corresponding .bin images should be generated.

2. Adding the OAD Reset Service to key_node

   The current key_node project does not contain the OAD Reset Service / OAD Start-Reset characteristic.

   I need guidance on how this should be integrated into the existing key_node application and how its callback should be implemented.

3. Reset characteristic functionality

   My understanding is that, for on-chip OAD, the currently running application cannot overwrite itself. Therefore, when the reset characteristic is updated, the application needs to invalidate/switch the current application image and reset the device so that the persistent application can take over the OAD process.

   I need clarification on the expected implementation for this in the key_node application, specifically:

   • Which flash region should be invalidated/erased?

   • Which API/mechanism should be used to invalidate the application image?

   • How should the device jump to the persistent application after the reset characteristic is written?

   • Is this functionality already implemented in an existing TI example that I should port into key_node?

4. Flash layout and linker configuration

   I also need guidance on how the existing key_node linker configuration should be modified to accommodate:

   • MCUboot

   • Persistent application

   • Key_node application

   • Any required image metadata / secondary region

   I want to understand the required memory layout and linker changes rather than simply flashing the pre-built OAD example images.

The OAD guide shared in the previous discussion explains how to use OAD once the required images and infrastructure are already available. My question is specifically about the development/integration process required to add OAD functionality to the existing key_node project.

In other words, I am looking for guidance on how to convert the existing key_node project into an OAD-capable project, including the required project structure, linker configuration, OAD Reset Service integration, image generation, and flash layout for both key_node V1 and V2.

Regards

Vaibhav