• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 1881 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.

CC2640R2F: CC2640R2F OAD Offchip with btool

Steffen Rentz
Intellectual 370 points
Part Number: CC2640R2F
Other Parts Discussed in Thread: CC2650, CC2640, BLE-STACK

Hi Community,

I downloaded the latest version of the sdk (simplelink_cc2640r2_sdk_1_50_00_58) and tried to test OAD Offchip on a CC2640R2F customer hardware.

For this I ported the sample project “simple_peripheral_oad_offchip” on the customer hardware and started an OAD download with btool as central device.

However, I get an error “OAD Exchange MTU Failed”. and then “OAD Download Not Successful”.

Does anyone know how to solve this issue?

Regards

Steffen

  • 0
    Guru 86745 points
    Hi Steffen,

    The SDK v1.50 Off-Chip OAD example program works using 2 CC2640R2F Launchpads. The other Launchpad programmed with host test hex file for BTool. Have you done that?

    -kel
  • 0 in reply to Markel Robregado
    Intellectual 370 points
    Hi kel,

    I wasn't using CC2640R2F Launchpads. My setup was a CC2640R2F custom hardware as peripheral device and a CC2650 SmartRF06 board with host test hex for btool.

    Regards

    Steffen
  • 0 in reply to Steffen Rentz
    Guru 86745 points
    Hi Steffen,

    Normally, it is recommended to use Btool and host test hex file from SDK v1.50. I am not sure there will be no problem if you use CC2650 SmartRF06 board with host test. Wait for a TI Engineer to help.

    -kel
  • 0 in reply to Markel Robregado
    TI__Mastermind 39620 points
    Steffen,

    Can you try with two CC2640R2F LaunchPads? We typically recommend that when custom hardware is involved, to start off with the LaunchPads to remove any unknown dependencies that may inhibit functionality.

    In your process, did you upload BIM first as well?
    software-dl.ti.com/.../oad.html
  • 0 in reply to Evan W
    Intellectual 370 points
    Hi Evan,

    we do not have CC2640R2F Launchpads. We would prefer if we can use the existing hardware.
    Can you say if the current sdk also supports OAD with the CC2650 SmartRF06 Board?

    Regards,

    Steffen
  • 0 in reply to Steffen Rentz
    TI__Mastermind 39620 points
    Steffen,

    We only support On-chip OAD with Smart RF06. Off chip is only on sensor tag and the launchpad because it requires external flash that's not provided on Smart RF 06.
  • 0 in reply to Evan W
    Intellectual 370 points

    Hi Evan,

    I think there was a misunderstanding. We want to use the SmartRF06 as the OAD downloader not as the target.

    Our OAD target is a custom hardware based on the SensorTag and has an external flash.

    When the CC2640 was used on the custom hardware OAD Offchip was working with the SmartRF06 & btool as OAD downloader.

    But after replacing the CC2640 with CC2640R2 (and porting the firmware following this guide dev.ti.com/.../cc2640-to-cc2640r2.html) OAD Offchip was not working any more.

  • 0 in reply to Steffen Rentz
    TI__Mastermind 39620 points
    Steffen,

    You're right, this was my mistake. My apologies. Your description was helpful though and i think i know the issue.

    In CC2640R2F/BLE-Stack 3.1.0 there was a compatability break with OAD between Legacy(CC2640) and current gen devices. This included a new header format, BIM, enhanced boundary checking and the ability to update stack and app separately.

    Since you are using SDK v1.50.00.58, you are by default, using BLE-Stack 3.01.01. In Migration guide BLE-Stack 3.00.01 to BLE-Stack3.01.00 we talk about how this has been updated and people need to refer to the Over the Air Download Page:
    dev.ti.com/.../blestack3.00.01-to-blestack3.01.00.html

    Specifically, you should read Off-Chip OAD for CC2640R2F:
    dev.ti.com/.../oad_offchip.html

    Therefore, you may need to make some changes to your OAD profile according to these new descriptions.
  • 0 in reply to Steffen Rentz
    Guru 86745 points
    Hi Steffen,

    I have implemented OAD at custom CC2640R2F Board. Depending on your application you can use either On-Chip OAD or Off-Chip OAD.

    The SDK v1.50 OAD example program works with 2 CC2640R2F Launchpad one is Target and the other is Downloader that works with BTool from SDK v1.50. I have tried it many times it works.

    Lets say you have another Target a custom CC2640R2F Board. The OAD Example Program will still work with it you just need to modify the board file for your custom CC2640R2F Board. So, you will be able to do OAD using a Downloader CC2640R2F Launchpad. It will work without problems.

    From my reading a custom board with CC2640 can be replaced with CC2640R2F mcu and still work.

    From my experience using BTool and host test hex file from older SDKs has problems doing OAD to CC2640R2F board programmed with example program from latest SDK such as SDK v1.50. So using SmartRF06 as OAD downloader might not work for your custom CC2640R2F board.

    -kel