This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2652R: Improving OAD distributor (host_test)

Part Number: CC2652R

Hello team,

We were able to Add BLE OAD to an Existing Project by following instructions from the tutorial. Now we're working on improving the OAD distributor side (launchpad running host_test project and btool). It'd be great if anyone can share tutorials or where we can start with. Below are a couple of ideas we have:

1. If we already have a device equipped with CC2652 running a different project. Can we add host_test functionality into its project? (UART port to communicate with btool is still available).

2. Is it possible that we use our laptop as a host(OAD distributor) without the launchpad and btool? (similar to running OAD app on Android or iOS)

Thank you!

  • Hey Dat,

    1. If we already have a device equipped with CC2652 running a different project. Can we add host_test functionality into its project? (UART port to communicate with btool is still available).

    I would say it depends on if the "different project" is a BLE5-Stack project or not. You can add host_test functionality to any Bluetooth LE project. What I would start researching is adding the NPI to your custom project. Here's a link to our User's Guide on the NPI: https://software-dl.ti.com/simplelink/esd/simplelink_cc13xx_cc26xx_sdk/6.10.00.29/exports/docs/ble5stack/ble_user_guide/html/ble-stack-common/npi-index.html. I would take a look at the code host_test uses and you can integrate the NPI to your example.

    2. Is it possible that we use our laptop as a host(OAD distributor) without the launchpad and btool? (similar to running OAD app on Android or iOS)

    This should be possible, yes. For example, our SimpleLink Starter mobile app works as an OAD distributor. The key things to be aware of when making an OAD distributor is to make sure you are validating the image that is being sent (i.e. check for an OAD image header and any CRC issues). If the image is not valid, you will not  be able to perform a successful OAD. I am unfortunately only able to comment at a high level at this time and can't dive into too much detail on #2.