CC2640R2F: OAD file missing?

Hi Niklas,

It's not a pretty process, but you'll have to port from CC2650/40 to CC2640R2F (BLE-Stack 2.2.1 -> BLE-Stack 3.0.0), then from BLE-Stack 3.0.0 -> BLE-Stack 3.0.1, and then finally BLE-Stack 3.0.1 -> BLE-Stack 3.1.0.

SDK 1.40 contains BLE-Stack 3.1.0 - not BLE-Stack 3.0.1. It's worth noting that BLE-Stack 3.1.0 does not have classic OAD, only enhanced. oad_target was replaced! Read about it here: software-dl.ti.com/.../oad.html

In other words, there are a great number of changes between the stacks - making porting non-trivial. However, following the guides and their errata carefully should allow you to port your project, and we're here to help as well.

Errata CC2640R2F: processors.wiki.ti.com/.../CC2640R2_Porting_Projects
Errata CC26XX: processors.wiki.ti.com/.../CC2640_Porting_Projects

Regards,
Rebel

Note: The error you're getting at the end is due to a difference between the standard configuration in later SDKs called Library configuration. Effectively this removes the boundary that existed between the Application Image and the Stack Image. You'll have to remove library configuration at some point in the porting process, you'll find the guide in the OAD section: software-dl.ti.com/.../oad_onchip.html
(Or use the oad-onchip project from the latest SDK as a base?)

Hi Rebel,

Thank you for the thorough answer so I will opt to use an OAD-project example as a base. 

I'm aiming to use Off-chip OAD and when I try to build a clean version of the base project simple_peripheral_cc2640r2lp_oad_off_chip_stack I get an error where the startup_entry symbol is undefined.

// Niklas

Hi Niklas,

Are you using Simple Peripheral Off-Chip OAD example program from SDK V1.40 BLE5? I import the example program at both CCS and IAR and I did not encounter any problems.

- kel

Hi Kel,

No, I use the BLEStack examples not the BLE5Stack examples.

// Niklas

Hi Niklas,

I import to IAR Workbench, the Simple Peripheral Off-Chip OAD Example Program from SDK v1.40 BLEStack. I build stack, then app and did not encounter any errors.

My SDK v1.40 is installed at C:\ti. If your SDK v1.40 is not installed at default c:\ti directory, that may cause build errors.

- kel

Hi Kel,

I only tried to build it with CCS. I do not have an IAR licence.

Both the SDK and CCS are installed in there default locations.

// Niklas

Niklas,

I've verified the CCS version of the project builds cleanly as well - 

It may be worth reinstalling the SDK to ensure a clean build occurs, can you post a screenshot or something else showing exactly what the issue is?

Regards,

Rebel