• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 639 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:

CC1352P: OFF chip OAD for CC1352P sensor code

CCS/CC2652P: CC2652P

Tanuja Gudaje
Prodigy 210 points

Part Number: CC2652P

Tool/software: Code Composer Studio

Hi Anil,

I am also working the OAD update but I am facing issue while updating on SimpleLink Starter APK.

It is returning status as "TI EOAD client waiting for the MTU update ", I did not understand this status.

while debug I am suspecting on External memory erase because on boot time I am getting "OAD failed to open" statement.

What could be the issue?

Please update if any Idea on this issue>

Kind Regards,

Tanuja

  • 0
    TI__Expert 5345 points

    Tanuja,

    I will assign someone to help you. 

    In the meantime, can you please provide more details? 

    • What TI device and SDK are you using? Are you using a LaunchPad?
    • What are the steps to reproduce this issue?

    Thanks,

    Luis

  • 0 in reply to Luis M
    Prodigy 210 points

    Hello Luis,

    I am using "CC2652P" TI device and "simplelink_cc13x2_26x2_sdk_4_10_00_78" SDK on custom board.

    But for the debugging purpose I check with launchpad also.

    With LaunchPad th OAD is updating psuccessfully.

    Steps to reproduce the issue;

    > SimpleLink starter APK for installed on the Android device(Smart Phone).

    > cc13x2p2lp_bim_offchip and simple_peripheral_oad_offchip_CC13X2P_2_LAUNCHXL_tirtos_ccs flashed on to the custom board.

    > Open the SimpleLink Starter APK from the Android device

    > Once you connect with custom board start OAD service.

    > Here the status is coming as TI EOAD client waiting for the MTU update.

    Please update if any solution to resolve this issue.

    Kind Regards,

    Tanuja

  • 0 in reply to Tanuja Gudaje
    TI__Genius 17265 points

    Hi Tanuja,

    Since you do not see this issue on our launchpads, it is likely something related to your custom hardware. Have you reviewed the section of the BLE5-Stack User's Guide discussing custom hardware? I would first go through that to ensure that you've followed all necessary steps, especially those pertaining to the board file modifications.

    You can find this section at the link below or at TI resource explorer->software->cc13x2 2x2 SDK->Documents->BLE5-Stack->BLE5-Stack User's Guide->Running the SDK on custom hardware

    https://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_4_20_01_04/docs/ble5stack/ble_user_guide/html/cc13x2_26x2/custom-hardware-cc13x2_26x2.html

    Best Regards,
    Alec

  • 0 in reply to Alec May
    TI__Genius 17265 points

    Hi Tanuja,

    Were you able to resolve this issue?

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Prodigy 210 points

    Hellio Alec,

    No I am not able to resolve it still.

    One more point I want to clear is-

    We are using CY15B104QI FRAM of 4MBits for Custom board.

    And in the LAUNCHPAD it is MX25R80535F of 8Mbits.

    Is FRAM capable of performing OAD?

    If yes, does the current driver support? If it doesn't support, please point us the modifications to be done accordingly.
    We are able to read and write some data to the FRAM in our application but could not able to do OAD Process.
    As per debugging to source code, it is not able to erase the external flash before taking copy of current binary as factory image from internal memory.
    If you need any inputs for this, please let me know.
    Its too critical now, please let us know the solution asap.
    Kind Regards,
    Tanuja
  • 0 in reply to Tanuja Gudaje
    TI__Genius 17265 points

    Hi Tanuja,

    I am trying to find someone to comment on your custom hardware questions, but in the meantime, could you try performing the OAD while using Btool as the OAD client rather than a smartphone? This will help eliminate the possibility that it is an issue with the mobile app.

    Best Regards,
    Alec