• State Resolved
  • Locked Locked
  • Replies 13 replies
  • Subscribers 54 subscribers
  • Views 270 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

LP-EM-CC2340R5: Failed to download program over OAD

Manomukil T
Prodigy 40 points
Part Number: LP-EM-CC2340R5
Other Parts Discussed in Thread: UNIFLASH

Hi Team,

I tried implementing OAD-onchip on the LP-EM-CC2340R5 board. I loaded the mcuboot program, the basic_persistent program and the basic_ble_oad_onchip program onto the board. It boots correctly into the basic_ble_oad_onchip program as well. We tried OAD via 2 methods.

1. Using Simplelink Connect App

2. Using Btool

But both the methods are giving error. As soon as I attempt an OAD, the board resets and boots into the peristent app (Device name "persistent_app" appears in the simpleconnect app). After that we get a OAD failed error in both the methods. I have attached the screenshots of the error we get below.

                                                             

Thank you.

  • 0
    TI__Mastermind 25423 points

    Hi,

    Thank you for reaching out. We will look into this and get back to you as soon as possible. In the meantime, could you provide the SDK version you are using as well as the SimpleLink Connect application version (along with Android version)? Can you also confirm if the MCUBoot image has been flashed as well?

    Best Regards,

    Jan

  • 0 in reply to Jan
    Prodigy 40 points

    Hi,

    I am using the Simplelink v7.2 SDK. The Simplelink Connect app version is v1.2.2 and the Android version is Android 12. I have also flashed the MCUBoot image as well. 

    Regards,

    Manomukil T

  • 0 in reply to Manomukil T
    TI__Intellectual 2940 points

    Hello Manomukil,

    Could you please be so kind as to give us more details on how you loaded the three programs (using uniflash, ccs).

    If you are using uniflash, could you specify the name of the three images being loaded (mcuboot.hex, basic_persistent.bin, and basic_ble_oad_onchip.bin)?

    I am trying to reproduce your issue with no success so far, so it would be great to have more information about your configuration.

    Best regards,

    David.

  • 0 in reply to David
    Prodigy 40 points

    Hey David.

    I have attached the screenshot of the Uniflash window loading the session which I used to flash all the three programs below.

    Regards,

    Manomukil T

  • 0 in reply to Manomukil T
    TI__Intellectual 2940 points

    Hello Manomukil,

    Thanks for the information provided.

    I am working on replicating the issue, please bear with me, I will try to have an answer for tomorrow.

    Best regards,

    David.

  • 0 in reply to David
    TI__Intellectual 2940 points

    Hello Manomukil,

    I will kindly ask you to help me with the following:

    1. Please share with me the three files you are using, as mine a slightly different in size and I would like to double check that.
    2. Try again flashing the device after manually erasing the flash using Uniflash.
    3. If you have another board, I would also ask you to try to reproduce it again there. In addition, is this happening all the time?

    Best regards,

    David.

  • 0 in reply to David
    Prodigy 40 points

    Hi David,

    PFB the files attached below:

    TI_bin_files.zip

    This issue is happening all the time. I have two boards and on both boards I am getting this issue. 

    Regards,

    Manomukil T

  • 0 in reply to Manomukil T
    TI__Intellectual 2940 points

    Hello Manomukil,

    Please help me with the following questions:

    1. Did you erase the device before flashing again?
    2. Was a connection and a successful OAD ever possible with the devices (before it went wrong) or has it never worked fine before?

    I flashed two devices with the provided files and a OAD is successful. I repeated the OAD several times as well for each device.

    Config in Uniflash:

    After flashing device and establishing connection:

      

    During firmware update (tested with both -v1 and -v2):

    After firmware update (Basic BLE project still running with respective -v1 and -v2 versions executing):

       

    Best regards,

    David.

  • 0 in reply to David
    Prodigy 40 points

    Hi David,

    I tried erasing and then flashing as well, its still throwing the same error. Also a problem I faced is at the default Address Mode in the project(public address),its not letting me connect to the board. So I changed the setting to RPA with Public ID. There it lets me connect to the board, but then throws the OAD errors I mentioned.

    Regards,

    Manomukil T 

  • 0 in reply to Manomukil T
    Guru 734975 points

    When you see OAD failure, no matter from Btool or App, the application might already be erase from flash and it's normal to see "persistent_app" appears in the simpleconnect app. When you get such OAD status, I suppose you can only use simpleconnect app to connect to persistent_app to do OAD again.

  • 0 in reply to Manomukil T
    TI__Intellectual 2940 points

    Hello Manomukil,

    Please help me with a couple of things:

    1. Look for the public address value. To do this, please connect your board, go to Uniflash - Memory and search for the 6-byte long value stored in a special register with address: 0x4E000058. Let me know what the value is.                                                                                
    2. When you change the settings to RPA with Public ID, did you do it in both basic_persistent and basic_ble_oad_onchip projects? If not, please modify it in both sources and try again.

    Best regards,

    David.

  • 0 in reply to David
    Prodigy 40 points

    Hi David, 

    Like you and YiKai Chen mentioned, I made both the projects RPA with Public ID and I attempted. As soon as I got the same error in the basic_ble_project, I switched to the persistent app and was successfully able to do an OAD. I however have 2 questions:

    1. Is it always the case that OAD can be done by these 2 stages of me manually connecting every time? Is there a one click solution for this?

    2. Why can't I connect to the application when the projects are in Public Address Mode?

    And wrt your question regarding the value at the 0x4E000058, all the values are showing 0. 

    Regards,

    Manomukil T

  • 0 in reply to Manomukil T
    TI__Intellectual 2940 points

    Hello Manomukil,

    This is a hardware error seen in the first batch of devices. The Public Address (PA) value should not be 0x00, that is why you can only connect when configured with RPA and not PA. This is most probably causing other issues, so I kindly ask you to contact your closest TI representative (he can contact me if needed to solve this issue as soon as possible).

    Apologies for the inconvenience.

    Best regards,

    David.