• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 355 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.

LAUNCHXL-CC1352R1: BLE OAD Environment Setup issue

James Mel
Expert 1380 points
Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: UNIFLASH, CC1352R

Greetings,

I was following the steps in page:

http://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_3_20_00_68/docs/ble5stack/ble_user_guide/html/ble-stack-oad/setting-up-environment.html

to test on-chip OAD using CC1352R1 with SDK 3.20.00.68 and BLE-5 stack 2.00.04.00. I used "simple_peripheral_oad_onchip" and "bim_onchip" with Debug configuration. I followed all steps but still on step 10 I can't verify the chip boot up, with the below behaviors:

* I get error when connecting to the XDS110 Class Application/User UART port using Tera Term.

* The board is not advertising (it does not appear when scanning bluetooth using my mobile - as it does usual when advertising with other examples).

* I still can get the primary BLE address using Uniflash like in step 11.

1) What can cause the above issue?

2) What is meant by "Build the stack project" in step 6? There is no stack project required in the previous steps. I thought it means the "simple_peripheral_oad_onchip" project, but building it is mentioned in step 8 "Build and flash the app project". Is there a stack project that should be imported and built in this step?

Thanks in advance.

* James *

  • 0
    TI__Guru 57865 points

    Hi James,

    Assigning this to our OAD expert.

  • 0 in reply to J Lindh
    TI__Intellectual 2430 points

    HI James,

    Step 6 is no longer necessary as the workspace structure has changed from previous SDK releases.
    This is a change that was missed when the documentation got updated and will be fixed so thanks for noticing and letting us know :)

    In regards to your issue, this could be a number of things.

    First of all, which IDE are you using to build the image?
    How do you flash the image to the device?
    Are you making sure that you are flashing the file with the _oad.bin ending?

    Best Regards,
    Yuval

  • 0 in reply to Yuval G
    Expert 1380 points

    Hello  Yuval,

    Thanks for your response.

    I use Code Composer Studio v9.0.0 for building all projects (including the _oad image).

    Both "ble5_simple_peripheral_oad_onchip_cc13x2r1lp_persistent_app" project and "cc13x2r1lp_bim_onchip" project are flashed using CCS. The "simple_peripheral_oad_onchip_app_CC13X2R1_LAUNCHXL_tirtos_ccs_Debug_oad.bin" image using UniFlash v5.1.0.2397. I tested flashing them all using "UniFlash", but it's the same result.

    * James *

  • 0 in reply to James Mel
    Expert 1380 points

    Hello Yuval,

    To help knowing the problem, I extracted the board flash memory using UniFlash into binary file. The data is extracted from the memory after flashing Persistent App, _oad.bin image, and BIM as per the user manual.
    KFA the hex file for each project, and the extracted memory binary file:

    CC1352R1_BLE_OAD_issue.zip

  • 0 in reply to James Mel
    Expert 1380 points

    Hello Yuval,

    Another question, after analysis I figured out the flash layout for the cc1352r on-chip OAD solution:

    But in the ".map" files of both user application (simple_peripheral_oad_onchip_app_CC13X2R1_LAUNCHXL_tirtos_ccs) and persistent application (ble5_simple_peripheral_oad_onchip_cc13x2r1lp_persistent_app), there is a section defined at 0x32000 with length 0x4000 and input section "board.obj".

    Is the above layout correct? and what area is section 0x32000 allocated to (user app or persistent app)?

    * James *

  • 0 in reply to James Mel
    TI__Intellectual 2430 points

    Hi James,

    Have you tried debugging and seeing if the device starts?

    Also, you can check out the chapter about OAD onchip flash layout in the BLE User's Guide :

    Best Regards,
    Yuval