Other Parts Discussed in Thread: CC2651P3, , , LAUNCHXL-CC26X2R1
This thread share two ways to evaluate OAD with the LP_CC2651P3 or LP_CC2651R3SIPA. The instructions can also be used with custom designs for a CC2651R3 or CC2651P3 or CC2651R3SIPA. This thread only discuss BLE based OAD.
Option 1: Evaluate OAD using project_zero
In that case, the evaluation can be done similarly to what is done with the LAUNCHXL-CC26X2R1. Just make sure to remember to flash a compatible BIM on the device (i.e. built or pre-built for the device you are using). Additional details can be found here.
Option 2: Enable OAD on the simple_peripheral example
This option consists in following the steps described for the LAUNCHXL-CC26X2R1 in this SimpleLink Academy lab.
Here are a few remarks to help:
- Section «Project Changes»
- (Step 1) The linker command file to use is: C:\ti\simplelink_cc13xx_cc26xx_sdk_6_20_00_29\examples\rtos\LP_CC2651P3\ble5stack\project_zero\tirtos7\ticlang\cc13x1_cc26x1_app_tirtos7.cmd
- (Step 5) For the first group of files, the path is <SDK>\source\ti\ble5stack_flash\profiles\oad\cc26xx. If it was not clear, I recommend having these files in a newly created OAD folder.
- (Step 6) The path to be added is rather ${COM_TI_SIMPLELINK_CC13XX_CC26XX_SDK_INSTALL_DIR}/source/ti/ble5stack_flash but this path is already there so no action needed
- Section «Code Changes»
- (Step 1) The changes have to be done in simple_peripheral.c.
- The function SimplePeripheral_processConnEvt() (called multi_role_processConnEvt() in the guide) already exists and should be modified rather than re-declared
- (Step 1) The changes have to be done in simple_peripheral.c.
To save you some time, you can leverage the files I have obtained when following these steps with simplelink_cc13xx_cc26xx_sdk_6_20_00_29:
- simple_peripheral.c: /cfs-file/__key/communityserver-discussions-components-files/538/0882.simple_5F00_peripheral.c
- simple_peripheral.syscfg: /cfs-file/__key/communityserver-discussions-components-files/538/4863.simple_5F00_peripheral.syscfg
- Files obtained when modifying the project configurations:
I hope this will help,
Best regards,