• State Resolved
  • Locked Locked
  • Replies 15 replies
  • Subscribers 52 subscribers
  • Views 536 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.

Original question:

LAUNCHXL-CC26X2R1: Simplelink CC26X2 - React Native OAD

CC2652R7: OAD not accepting .bin file

Kenneth Thomas
Prodigy 250 points
Part Number: CC2652R7
Other Parts Discussed in Thread: UNIFLASH

Hello, 

So recently, I've been trying to utilize OAD in the SimpleLink Starter App to send over a .bin file to my microcontroller. Each time I send over a file it tells me that it was successful and it rebooted however nothing new is displayed, the old example is run. This all changed when I flashed over the project_zero_unsecure_app.hex found in C:\ti\simplelink_cc13xx_cc26xx_sdk_7_10_01_24\examples\rtos\LP_CC2652R7\ble5stack\hexfiles. Basically whatever the hex file is using allows for the image to be updated and executed.

I initially started off by using the SLA's BLE Enhanced OAD Fundamentals lab. I went through it and when I tried flashing the files for on-chip (bim, persistant app, and simple peripheral) using Uniflash I wasn't able to get Btool to work so I found a forum here that said to flash persistant via ccs, the project bin via uniflash, and bim via css to get it work properly. However when I looked at the FW Download the "Select FW File" was grayed out making it unable to be selected. Then I did the same thing but this time with project zero (I read somewhere that it is a off-chip example but I've been treating it as a on-chip example) and the "Select FW File" was red allowing me to select a file and start the OAD but whenever it rebooted it reverted to the original version. The last thing that I test was using hex file in the first paragraph, this time it worked as intended the "Select FW File" was red, the transfer was successful and on the reboot the new image was executed.

So, my question is how to I edit the project_zero example so that one, I don't need to flash the files using ccs and uniflash together (either just using one to flash all three or preferably having one file to flash). Second so that I am able to flash over the .bin file using OAD.

Thanks,
Kenneth Thomas

  • 0
    TI__Mastermind 42250 points

    Hi Kenneth,

    Thank you for reaching out! We will look into this and get back to you as soon as possible. In the meantime, could you verify if you see the same behavior when trying to perform OAD updates using host_test + btool as the distributor? I would like to see if the issue happens with several distributors or not.

    Best Regards,

    Jan

  • 0
    TI__Genius 15575 points

    Hello Kenneth,

    Can you confirm as well that you have followed the BLE Enhanced OAD Advanced lab for Task 2 specific to Add On-Chip OAD to Multi Role and used the software projects mentioned in BLE Enhanced OAD Fundamentals lab (Persistent App and Boot Image Loader (BIM))? Did it work for you with the multi role project following those steps?

    Best regards,

    David.

  • 0 in reply to Jan
    Prodigy 250 points

    When I tried to perform OAD updates using host_test + btool as the distributor, I ran into a problem where I would have to flash the persistent app via ccs, then project zero/simple peripheral via uniflash, then bim via css in this order for the oad to work with btool. But when it is flashed this way then it is able to perform an update.

  • 0 in reply to David
    Prodigy 250 points

    No when I try to reset the OAD into the persistent app, it never shows up again in the SimpleLink Starter App.

  • 0
    Prodigy 250 points

    So update: I was able to get to get project zero to accept .bin files by switching the bim to the off chip version. However, now my SimpleLink Starter app is stuck only showing only the EOAD start/reset option. I can't tell if the multi-role or simple-peripheral is working with the app because the app is stuck showing the EOAD start/reset option. I'm using and iPhone 12 running iOS 16.6.1. I can get it to work with bTool.

  • 0 in reply to Kenneth Thomas
    TI__Genius 15575 points

    Hello Kenneth,

    I am working on reproducing the issue. Could you please share more details on the steps you followed to do this with project zero? Using the BLE Enhanced OAD Advanced lab for example or are you using the example out of the box without modifications?

    Could you also show how you are flashing the .hex and .bin files using Uniflash?

    Best regards,

    David.

  • 0 in reply to David
    Prodigy 250 points

    I'm using the BLE Enhanced OAD Advanced lab (on-chip example), and using the my iPhone with the SimpleLink Starter App as the distributor. When trying to flash the three files (BIM on-chip, persistent app, and the mutil-role project) I had to flash persistant via ccs, the project bin via uniflash, and bim via css and in this order to get it work properly with btool. 

  • 0 in reply to Kenneth Thomas
    TI__Genius 15575 points

    Hello Kenneth,

    Is it possible for you to share the .hex and .bin files for me to try to reproduce the error? I would like to check if I can flash the files as I am currently doing it successfully with Uniflash.

    Best regards,

    David.

  • 0 in reply to David
    Prodigy 250 points

    Yeah of course, they are from the resource explorer, but if you would like me to send them to you how should I go about doing that?

  • 0 in reply to Kenneth Thomas
    TI__Genius 15575 points

    Hello Kenneth,

    Are you using the bim_onchip.hex file from <SDK_INSTALL_DIR>\examples\nortos\<BOARD_NAME>\bim\hexfiles\? and are the other files also the same?

    I think it is possible to attach a .zip.

    Please let me know.

    David.

  • 0 in reply to David
    Prodigy 250 points

    SimplePer.zip

    These are the files, I used both the one found in the sdk and the resource explorer, neither worked.

  • 0 in reply to Kenneth Thomas
    TI__Genius 15575 points

    Hello Kenneth,

    I have been able to successfully flash the cc2652R7 device with the files you have sent me.

     

    As well as to establish a connection and a fw update.

    Please help me with the following questions:

    1. Are you using the correct load address (0x38000) for the persistent app?
    2. Are you able to flash the files or do you get any errors within uniflash? if this is the case, what are the errors?
    3. If you can flash the device correctly, do you get any warning messages at the console (yellow color) or just the SUCCESS one (green color)?
    4. Have you modified anything on the Settings & Utilities section? (Program Load or CCFG options for example?)

    Best regards,

    David.

  • 0 in reply to David
    Prodigy 250 points

    Hey David,

    1. Yeah I was using the correct load address.
    2. Yeah I was able to flash the files without any errors.
    3. I get a [SUCCESS] Program Load completed successfully.
    4. 

    Thanks again,
    Kenneth

  • 0 in reply to Kenneth Thomas
    TI__Genius 15575 points

    Hello Kenneth,

    1. What Uniflash version do you have (8.4)? Can you try to re-install it just to make sure as well?
    2. Do you have another board to try flashing the same files following the same procedure?

    Regards,

    David.

  • 0 in reply to David
    Prodigy 250 points

    Yeah, I think it's because I'm using the IOS version of the app, it's all good though we decided to use the off-chip version anyway.

    Thanks for your help David!