CC2340R5: OAD debugging manual steps

William Cullen

Part Number: CC2340R5

Tool/software:

I have a working app that I now would like to configure for OAD. I have successfully run the OAD onchip example. When looking at the debugging process, it seems I have to manually adjust the debugging info just to run the code. When I'm developing I can be flipping into debug every minute or so and I don't see how to develop if I'm configuring every time. What is the typical approach here? Can I configure the code to run without the bootloader to develop/debug and then switch back for testing? Should I just keep on developing without OAD and worry about OAD at the end? It seems like this process has gotten difficult and I hope to find some approach that is efficient.

10 months ago

0 Alex Fager 10 months ago

TI__Genius 12371 points

Hello William Cullen,

I wanted to ask if you have referenced with OAD SLA already? Bluetooth Low Energy Enhanced Over the Air Download (OAD) Fundamentals (ti.com). It has some great information on getting started with OAD.
For a bit deeper info we can reference the OAD section available in the SDK: BLE-Stack OAD Profile — SimpleLink CC23xx SDK BLE5-Stack User's Guide 3.03.01.00 documentation

Thanks,
Alex F

0 William Cullen 10 months ago in reply to Alex Fager

Prodigy 80 points

I don't understand. I stated that I ran the demos. I also noticed debugging seems awkward and asked specific questions. Is there something I am missing you are trying to point out?

0 Alex Fager 10 months ago in reply to William Cullen

TI__Genius 12371 points

Hello William,

Some source code that can help here is the TI MobileLink app, SIMPLELINK-CONNECT-SW-MOBILE-APP Code example or demo | TI.com, which features OAD development.

In the meantime I am bringing onto the thread another team member more familiar with OAD than me.

THanks,
Alex F

0 David 10 months ago in reply to William Cullen

TI__Genius 15535 points

Hello William,

I would work on the application development first and then work on adding OAD. Of course I would suggest to be mindful of the Flash and RAM (particularly Flash) consumption considering you need to reserve space for the Bootloader (MCUBoot in this case) and the light weight program that will reception the image (hosting the OAD service) which in our examples is referred as persistent_app. When debugging and application with OAD, I would refer back to the last section of the training material Alex shared Bluetooth Low Energy Enhanced Over the Air Download (OAD) Fundamentals (ti.com).

BR,

David.

0 William Cullen 10 months ago in reply to David

Prodigy 80 points

Hi - thanks you for the suggestion. By chance is there anything that describes the changes to the basic ble example for OAD? I could try to diff for it all I suppose but that is not fun. I understand there are bootloader and memory layout issues and such, but also there is the reset function which I will have to hunt for and perhaps other things? It would be nice if I could run the OAD examples without the bootloader to just work on the app and then switch back to the OAD configuration so I'm not porting code back and forth between the two over time.

0 David 10 months ago in reply to William Cullen

TI__Genius 15535 points

Hello William,

I would suggest first the README file from the basic_ble_oad_onchip out of the box example from the SDK, for a general overview of what is added (specially the services, which you already mentioned it is only OAD_Reset for the basic_ble_oad application part). Although it is not a very elegant method, a diff compare between the basic_ble_oad_onchip and the basic_ble example project would provide specifics of what has been changed. We will soon release a training material to explain how to add OAD to a basic_ble example, which will explain this better. However, currently that would be my suggestion.

BR,

David.

Bluetooth®︎

Bluetooth forum

CC2340R5: OAD debugging manual steps