• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 645 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC2650STK: off chip oad process.

aditya sharma
Prodigy 70 points
Part Number: CC2650STK
Other Parts Discussed in Thread: CC2650, BLE-STACK

i am not able to generate the superhex file that is the merge image of all three images which are bim.hex  app.hex and stack.hex.m using ble stack 2.2.2 and ccs 7.4.

suggest methe postbuild process.

one more issue is after getting the .bin file in my android phone .how do i import it to the sensortag android app to send it over the air.

  • 0
    Prodigy 70 points

    Part Number: CC2650STK

    hello

    my objective is to upgrade firmware for cc2650 sensortag using off chip OAD procedure.

    i am following the steps as mentioned in the Sensor tag User Guide (http://processors.wiki.ti.com/index.php/CC2650_SensorTag_User's_Guide) but unable to proceed in the process. 

    my steps are as follows.

    1. i have imported the following projects and builded them in order.

    bim_extflash

    sensortag_cc2650stk_stack

    sensortag_cc2650stk_app.

    i am able to locate the .hex and .out files for the respective projects.till now i have done no change in the postbuild steps in the properties of the projects.

    now as per the use guide document its required to generate a superhex file containing images for all three files. for this it has been described a python script that need to be written in the postbuild steps area and i hve done the same.but i m unable to find the output file that will be generated.

    i m following this text from the user guide,

    Building SensorTag Super Hex File

    To create a single, “super hex” SensorTag firmware file consisting of the BIM_extflash, Application & Stack images, the individual hex files for the respective projects need to be merged into one file. As hex files use an open standard, any merge tool can be used provided it supports the appropriate hex standard. TI uses the IntelHex python tools which assumes each hex file in the Intel Extended hex format. To confirm that the resulting hex file in the Intel format, each line should begin with a colon ‘:’.

    To merge the files, the procedure as documented in the BLE SW Developer Guide (SWRU393) can be used. When the BIM is used, the Application image should start at flash address 0x1000. Refer to the “Working with Hex Files” section. Example procedure to generate a sensortag_super.hex super file:

    $ C:\Python27\Scripts>python hexmerge.py -o sensortag_super.hex -r 0000:1FFFF sensortag_cc2650stk_app.hex:0000:1EFFF sensortag_cc2650stk_stack.hex bim_extflash.hex:0000:1FFFF --overlap=error

    Where “sensortag_cc2650stk_app.hex” is the application; “sensortag_cc2650stk_stack.hex“ is the protocol stack; and “bim_extflash.hex” is the BIM input hex files. Note that the names of the input hex files may differ. Use the actual App, Stack & BIM_extflash hex files generated by the respective build environment.

     hexmerge .py i have downloaded from internet and the output file sensortag_super.hex ,i am not finding location.

    moreover .in context of thr user guide they have provided the usage of oadimage tool.and that too m not getting.

    please do provide me the solution for how to generate the final .bin file that i can use for oad update from the android app.

    thanks .

  • 0
    TI__Mastermind 33460 points
    Hello,

    Please download BLE-Stack 2.2.2 and follow the steps in the OAD User's Guide from the docs folder of the SDK install. The sensortag update process should be similar to that of simple BLE peripheral.

    The Guide in that SDK is updated to be more helpful.
  • 0 in reply to Sean2
    Prodigy 70 points
    hello sean,
    thanks for answering.i already have the BLE-Stack 2.2.2 and using the same user guide.still m not getting the output supermerge.hex.
    please do solve my problem and suggest some solution.
  • 0 in reply to Sean2
    Prodigy 70 points
    I m not able to generate the supermerge.hex and not able to locate the . bin files generated for the individual projects as a result of the post build process
  • 0 in reply to aditya sharma
    TI__Mastermind 33460 points

    Hello,

    Using the unmodified sensortag project from the SDK with CCS I was able to produce the OAD binary.

    The OAD image tool is included in the project and will generate the OAD binary automatically

    The file highlighted in the red box below is the one that should be passed into BTool as per section 5.6.2 of the OAD User's Guide.

    You should be able to follow the rest of the guide from here to perform an OAD. If you are using the mobile app, I do not have an android device available but iOS you are able to e-mail yourself the binary that you are trying to OAD and open the e-mail attachment in the TI SensorTag app.

    If you need to generate a "super hex" where we include the app, the stack, and the BIM, you can add the following to your project in CCS

    ${TOOLS_BLE}/oad/oad_image_tool.exe <workspace_path>\bim_extflash\FlashOnly_ST\bim_extflash.hex ${WORKSPACE_LOC}/ ${WORKSPACE_LOC}/${ProjName}/${ConfigName}/${ProjName}.hex -t offchip -i production --imgVer 0 -ob ${WORKSPACE_LOC}/${ProjName}/${ConfigName}/${ProjName}_oad_super.bin -m 0x1000 --r 0x1000

    Where workspace path is the path to your CCS workspace. Similar steps can be taken in IAR. Please note that production images are **not** for over the air update (they include BIM which cannot be updated) but instead are intended for flash programming the device during production.