• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 634 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.

CCS/CC2650: OAD Image B FLASH Region

Frank K
Prodigy 50 points

Part Number: CC2650
Other Parts Discussed in Thread: BLE-STACK, SYSBIOS,

Tool/software: Code Composer Studio

Hi, eweryone I'm makin a On-chip OAD for CCS. I`ve been using IAR's on-chip solution for BT (while I'm using 15.4) as reference. the question is  how do I make programm in CCS with FLASH_BASE at 0x9010 so oad_image_tool.py could build my app correctly. When I set this address in linker I get this errors: 

error #10264: DEFAULT memory range overlaps existing memory range FLASH
error #10264: DEFAULT memory range overlaps existing memory range SRAM
error #10010: errors encountered during linking; "Image_B_dummy.out" not built

The  reset vector in cfg is set: m3Hwi.resetVectorAddress = 0x9010;

Image A doesn't give this issue because it's addr is 0x100, which is ok. If I set same or some address that is near to it - Image B builds successfully. But  In this case  oad_image_tool.py wouldn't give image that could work as needed. 

  • 0
    TI__Genius 12815 points
    Hi Frank,

    The BLE-Stack v2.2.1 does not support On-chip OAD with CCS. There is CCS On-chip OAD support in BLE-Stack v3.0.0 and later. I would recommend you look at the way those files were created to help with your linker errors. Did you review the map file to make sure the image could fit within the constraints specified by the On-chip OAD Memory Layout in the OAD User Guide?
  • 0 in reply to RachelP
    Prodigy 50 points

    Hi, Rachel, thank you for your reply. Yes Image definitely fit in range. As far as I understood in suggested oad exmple (ss. "persistent_app_cc2640r2lp" ) a HIGH flash range boundary aligment is used among with image_hdr page aligment for BIM image find convinience? I managed to do so. But I faced with problem that "ti_sysbios" and "xdc_runtime" items are still maped to it's default address range from 0x100 to 0x600. Problem is I haven't got in RTOS this far to get how does "persistent_app_cc2640r2lp" example manages to keep this items within range. I get this warnings:

    warning #10229-D: output section ".data" refers to load symbol "ti_sysbios_knl_Clock_doTick__I" and hence cannot be compressed; compression "lzss" is ignored
    warning #10229-D: output section ".data:ti_sysbios_BIOS_Module__state__V" refers to load symbol "ti_sysbios_BIOS_startFunc__I" and hence cannot be compressed; compression "lzss" is ignored

  • 0 in reply to Frank K
    TI__Genius 12815 points
    Hi Frank,

    Please see the OAD User Guide located in SimpleLink CC2640R2 SDK v1.00.00.22. This contains an explanation of adding OAD to an existing project. You should understand completely these steps as well as the steps in the porting guide in order to make this work on the CC2650. We still advise you to use the IAR project instead because we have found the IAR compiler provides more available flash than the CCS compiler.