• State TI Thinks Resolved
  • Locked Locked
  • Replies 16 replies
  • Answers 4 answers
  • Subscribers 55 subscribers
  • Views 429 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.

CCS/LAUNCHXL-CC2640R2: Multi_role example OAD Failed

Curly Lin
Prodigy 180 points
Part Number: LAUNCHXL-CC2640R2
Other Parts Discussed in Thread: CC2640R2F, CC2640, CC2652R, CC2642R, UNIFLASH

Tool/software: Code Composer Studio

Hi,

I'm working on the on chip OAD with multi role example .

Following the step in Enhanced OAD, but there's some problem occurred when OAD by btool.

In the app project setting, I ignore all the "OAD_IME_E" arg and use "OAD_IMG_B" instead.

At the Import files, using flash_interface/internal instead.

All the setting and code changes are following the document.

Both app and stack project could build and flash to board with no issue, but the OAD through btool will stop by unknow problem.

If there's information that I setting to the project need to be provide, please let me know.

Thanks.

  • 0
    TI__Guru** 101450 points

    Hi,

    I will assign an expert to look into your issue.

    Please specify the SDK version you are using.

    Kind regards,

  • 0 in reply to Clément
    Prodigy 180 points

    Hi Clément,

    The SDK version is simplelink_cc2640r2_sdk_3_40_00_10.

  • 0 in reply to Clément
    Prodigy 180 points

    Hi,

    Is there any progress at this issue?

    Thanks.

  • 0 in reply to Curly Lin
    TI__Genius 14845 points

    Hi Curly, 

    Do you want to use on-chip OAD? Because if you switch from OAD_IMG_E=1, as it says in the lab, to OAD_IMG_B=1, it means that it's using on-chip OAD. 

    Since multi_role is a large application, I don't think you have enough memory to perform an on-chip OAD on the CC2640R2 device with the multi_role project. Because when using OAD, there must be enough space to store two application images as well as the persistent app and bim. Is there a reason why you don't want to use off-chip OAD?

    Thanks, 
    Elin

  • 0 in reply to Elin W
    Prodigy 180 points

    Hi Elin,

    I just want to try on-chip OAD.

    Because I add some new feature in project_zero, the OAD is one of the feature, and I have an application has no external flash, it could only use on-chip OAD, 

    Is the code size of project_zero small enough to add OAD?

    Thanks.

  • 0 in reply to Curly Lin
    TI__Genius 14845 points

    Hi Curly, 

    If you just want to experiment with on-chip OAD, I would recommend you to use the simple_peripheral_onchip example in the SDK. 

    Project_zero is also a large application which, in the SKD example, uses external flash to boot. So I don't think it's a good idea to use it. 

    If you can share more details about your application I can give you some more specific advice. 

    Thanks, 
    Elin

  • 0 in reply to Elin W
    Prodigy 180 points

    Hi Elin,

    Thanks for reply.

    I already use the simple_peripheral_onchip  example for OAD practice, but the function in Project_zero is more close to the application that I want, and I'm trying off-chip OAD on Project_zero example.

    But there's still some problem on boot.

    I follow the instruction in Enhanced OAD to add OAD in Project_zero, and flash bim_oad_offchip to my CC2640R2F launchpad, and there's no message ouput to console.

    The Project_zero example is import from SDK simplelink_cc2640r2_sdk_3_40_00_10.

    And I add red/green LED on BIM to verify if it work, but LED seems no response.

    If there's any detail need to provide, please let me know.

    Thanks.

  • 0 in reply to Curly Lin
    TI__Genius 14845 points

    Hi Curly, 

    Where and how did you add the LED functionality in the BIM project? Can you put a breakpoint there and see if the application reaches it? If you reach the breakpoint, look at the return value of the function. 

    Thanks, 
    Elin

  • 0 in reply to Elin W
    Prodigy 180 points

    Hi Elin,

    The LED is add in BIM project before Bim_checkImages(), it works.

    But it still has few problem need your help.

    1)

    I already add OAD in project_zero and flash BIM into cc2640 lauchpad.

    It has no response after board reset, but it works in debug mode.

    2)

    The proces stop at ImageBlockWrite when perform OAD, here is the btool log.

    btool.log
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    ----------------------------------------------------
    - Log Start Marker -
    ----------------------------------------------------
    [03/17/2020 06:40:40.240] <Info > [76] : <Info> - 06:40:40.239
    Start OAD Download
    --------------------------------------------------------------------
    [03/17/2020 06:40:40.244] <Info > [77] : <Info> - 06:40:40.242
    Image Service Discovery
    --------------------------------------------------------------------
    [03/17/2020 06:40:40.246] <Info > [78] : <Info> - 06:40:40.246
    OAD Send UUID Discovery
    --------------------------------------------------------------------
    [03/17/2020 06:40:40.249] <Info > [79] : <Tx> - 06:40:40.232
    -Type : 0x01 (Command)
    -OpCode : 0x2016 (HCI_LEReadRemoteUsedFeatures)
    -Data Length : 0x02 (2) byte(s)
    Handle : 0x0000 (0)
    [03/17/2020 06:40:40.251] <Info > Dump(Tx):
    0000:01 16 20 02 00 00 .. ...
    --------------------------------------------------------------------
    [03/17/2020 06:40:40.263] <Info > [80] : <Tx> - 06:40:40.248
    -Type : 0x01 (Command)
    -OpCode : 0xFD86 (GATT_DiscPrimaryServiceByUUID)
    -Data Length : 0x12 (18) byte(s)
    ConnHandle : 0x0000 (0)
    Value : 00:00:00:00:00:00:00:B0:00:40:51:04:C0:FF:00:F0
    [03/17/2020 06:40:40.266] <Info > Dump(Tx):
    0000:01 86 FD 12 00 00 00 00 00 00 00 00 00 B0 00 40 ...............@
    0010:51 04 C0 FF 00 F0 Q.....
    --------------------------------------------------------------------
    [03/17/2020 06:40:40.280] <Info > [81] : <Rx> - 06:40:40.279
    -Type : 0x04 (Event)
    -EventCode : 0x00FF (HCI_LE_ExtEvent)
    -Data Length : 0x06 (6) bytes(s)
    Event : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
    Status : 0x00 (0) (SUCCESS)
    OpCode : 0xFD86 (GATT_DiscPrimaryServiceByUUID)
    DataLength : 0x00 (0)
    [03/17/2020 06:40:40.282] <Info > Dump(Rx):
    0000:04 FF 06 7F 06 00 86 FD 00 .........
    --------------------------------------------------------------------
    [03/17/2020 06:40:40.428] <Error > Attribute Dictionary Invalid Handle Cannot Be Used
    Key = 0000_FFFF
    UpdateTmpAttrDict()
    Invalid Handle = 0xFFFF
    {AttrDataUtils}
    [03/17/2020 06:40:40.430] <Info > [82] : <Rx> - 06:40:40.428
    -Type : 0x04 (Event)
    -EventCode : 0x00FF (HCI_LE_ExtEvent)
    -Data Length : 0x0A (10) bytes(s)
    Event : 0x0507 (1287) (ATT_FindByTypeValueRsp)
    Status : 0x00 (0) (SUCCESS)
    ConnHandle : 0x0000 (0)
    PduLen : 0x04 (4)
    Handle : 2E:00
    Handle : FF:FF
    [03/17/2020 06:40:40.433] <Info > Dump(Rx):
    0000:04 FF 0A 07 05 00 00 00 04 2E 00 FF FF .............
    --------------------------------------------------------------------
    [03/17/2020 06:40:40.435] <Info > [83] : <Info> - 06:40:40.435
    OAD Send UUID Info Discovery
    --------------------------------------------------------------------
    [03/17/2020 06:40:40.526] <Info > [84] : <Rx> - 06:40:40.523
    -Type : 0x04 (Event)
    -EventCode : 0x003E (HCI_LE_GenericReportEvent)
    -Data Length : 0x0C (12) bytes(s)
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    If there any information need to provide, please let me know.

    Thanks.

    Curly

  • 0 in reply to Curly Lin
    Guru 86605 points

    Hi Curly,

    Adding OAD to multi-role either on-chip or off-chip is not a good combination. I have done the same and I encounter heap issues that will result in failed OAD. Sometimes it works, but most of the tries it does not.

    It is out of spec. But if you use other BLE chips with bigger memory maybe it is doable. BLE chips such as CC2642R and CC2652R.

    -kel

  • 0 in reply to Markel Robregado
    Prodigy 180 points

    Hi Markel,

    You mean that is impossible to add another task in simple_peripheral_oad_offchip and stably perform OAD?

    I also encounter maybe heap or flash size problem, that is a difficult trouble.

    Thanks/

    Curly

  • 0 in reply to Curly Lin
    TI__Genius 14845 points

    Hi Curly,

    Curly Lin said:
    It has no response after board reset, but it works in debug mode.

    Unfortunately just because it works in a debug session doesn't mean that it works automatically on the device when BIM is responsible for booting the image. If the image doesn't contain a valid OAD Image Header, the BIM doesn't boot the image. Did you use the OAD Image tool to generate the files and did you load them on the right order and the correct way?

    Curly Lin said:
    The proces stop at ImageBlockWrite when perform OAD, here is the btool log.btool.log

    Thanks for the log, I'll look at it tomorrow and get back to you. 

    Thanks, 
    Elin

  • 0 in reply to Elin W
    Prodigy 180 points

    Hi Elin,

    The bin file is generate by OAD Image tool define in build > step > post-build step, am I right?

    And the program step is :

    1. flash stack by CCS.

    2. flash app by Uniflash

    3. flash BIM by CCS

    Is that correct?

  • 0 in reply to Curly Lin
    Guru 86605 points

    Curly Lin said:
    You mean that is impossible to add another task in simple_peripheral_oad_offchip and stably perform OAD?

    The simple peripheral off-chip oad will work. It is a big example program. It also requires a lot of memory for oad to work. If you add multi-role code to it which also requires a lot of memory to work, the problem occurs.

    As is the simple peripheral off-chip oad will work, you can add a lot of code to it and it will still work. After modifying the simple peripheral off-chip oad you need to test oad many times like 20/20 to make sure oad is reliable.

    -kel

  • 0 in reply to Markel Robregado
    Prodigy 180 points

    Markel Robregado said:
    The simple peripheral off-chip oad will work. It is a big example program. It also requires a lot of memory for oad to work. If you add multi-role code to it which also requires a lot of memory to work, the problem occurs.

    I add a new task to simple peripheral off chip example, but the code size in flash seems still not enough to fit it.

    And still work on code reduction.

    Curly

  • 0 in reply to Curly Lin
    TI__Genius 14845 points

    Hi Curly, 

    Yes, that is the correct order. And the OAD Image Tool is defined as a post-build step, but it's always good to check that it has worked as expected and that you use the *_oad.bin file.

    Just checked through the log and it looks like the first error message you get is "Attribute Dictionary Invalid Handle Cannot Be Used" so I would try and get to the root cause of that first. 

    Thanks, 
    Elin