• State Answer Suggested
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 467 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.

CC2652R7: On-Chip OAD debugging methods

Jermyn Lau
Prodigy 90 points
Part Number: CC2652R7

Tool/software:

Hi, 

I am using CC2652R7, currently implementing BLE on-chip OAD function to my project, I tried to follow this to add the on-chip OAD function(Bluetooth Low Energy Enhanced Over the Air Download (OAD) Advanced — CC13XX CC26XX SimpleLink Academy)

After that I can use the SimpleLink Connect app and open the OAD interface, but when I tried to update the firmware using the provided image, it is stuck at 0% progress like this.

Could you help me that what could I do to debug my firmware, any examples that I can follow? Thank you so much.

Best,

Jermyn

  • 0
    TI__Genius 15535 points

    Hello Jermyn,

    Thanks for reaching out!

    What SDK version are you using? May I ask if you have followed all the steps from the OAD SLA or is there any that was not clear how to execute? From where are you getting the BIM file, could you try using the bim_oonchip.hex file from the SDK (\examples\nortos\CC26X2R1_LAUNCHXL\bim\hexfiles\bim_onchip\Release)?

    BR,

    David.

  • 0 in reply to David
    Prodigy 90 points

    Hi David, 

    1) For my firmware program I built on simplelink_cc13xx_cc26xx_sdk_7_40_00_77, for persistent_app and bim_on-chip are all from simplelink_cc13xx_cc26xx_sdk_7_40_00_77.

    2) And I followed the OAD SLA step by step and here is how I flashed my program:

    3) And may I know is there any resource for debugging on-chip OAD?

    4) And I noticed that there is a tiny blue question mark appears on each file/folder icon, but there is no error after I built the program. May I know is this also a problem and how to solve it?

    Thank you,

    Jermyn

  • 0 in reply to Jermyn Lau
    TI__Genius 15535 points

    Hello Jermyn,

    1. Could you please try directly with the bim_onchip.hex file from the SDK (\examples\nortos\CC26X2R1_LAUNCHXL\bim\hexfiles\bim_onchip\Release)?
    2. What address are you using to flash the application program? I see in the screenshot that is empty.
    3. Currently we only have the one you have already pointed out.
    4. Are you using version control (git) with CCS?

    Best Regards,

    David.

  • 0 in reply to David
    Prodigy 90 points

    Hi,

    1) I did use the file u have mentioned, but why u recommend file from CC26X2R1_LAUNCHXL but not from LP_CC2652R7. I have tried the bim_onship.hex from both, but still stuck in 0% progress.

    2)Should be 0x00000000 by default? We built our firmware based on the simple_peripheral example.

    3)Got it, thanks a lot.

    4)Yes, so will this affect anything?

    And I also tried with the multi_role example and it also stuck.

    Thank you so much.

    Best,

    Jermyn

  • 0 in reply to Jermyn Lau
    TI__Genius 15535 points

    Hello Jermyn,

    1. Apologies, my mistake, please use the hex file corresponding to the device.
    2. Alright, got it.
    3. The files are probably not being committed and therefore unknown. If you commit, would they disappear?

    Are you using the image with v2 version compileed from your project? You should be able to see the _v2.bin file inside the Release folder and load it as a local file from the SimpleLink app.

    BR,

    David.

  • 0 in reply to David
    Prodigy 90 points

    Hi,

    After I read the source code from github(https://github.com/TexasInstruments/simplelink-connect-fw-bins/tree/main/CC2652R7/8_30_00_51_eng), it shows only .bin files for IAR, but I am using CCS to develop my firmware, is this the reason that the OAD didn't process? 

    \

    and I found the .bin files for CCS in this:

    But in the simplelink connect app, I can only choose from the .bin files for IAR:

    May I know if this is the reason that the OAD process is stuck? Thank you so much.

    Best,

    Jermyn

  • 0 in reply to David
    Prodigy 90 points

    Hi David, could you help with the latest question I posted? Thank you so much.

  • 0 in reply to Jermyn Lau
    TI__Genius 15535 points

    Hello Jermyn,

    Apologies for the delay. Could you please use the non-iar version or load your own application bin file. You can find it in the Release folder after building the bim_on project. Then you can send it to your phone and have it loaded directly to the app instead of selecting a device and a file.

    Please let me know how it goes.

    BR,

    David

  • 0 in reply to David
    Prodigy 90 points

    Hi David,

    When I flashed the .bin files from the ccs after I built, it doesn't work and said 'service not found' or sometimes said 'OAD service reset failed':

    (I set the address of persistent app as 0x86000 because this text:)

    I also found that sometime after 'OAD service reset failed', the firmware is change to persistent app, then I disconnect and reconnect the deviceagain, I can continue to use OAD update to updated to the desired firmware, this behavior is wired, the whole process should not be split like this.

    But it works well when I used the .hex and .bin files directly from this (simplelink-connect-fw-bins/CC2652R7/7_10_00_98_eng/simple_peripheral_oad_onchip_LP_CC2652R7_tirtos7_ticlang_oad-v1.0.0.bin at main · TexasInstruments/simplelink-connect-fw-bins · GitHub):

    May I know is there any differences between the files on the website and from the example?

    Best regards,

    Jermyn