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.

TIRTOS_ROM.icf

Other Parts Discussed in Thread: CC1310

Hi

I find there many symbols are placed in the fixed address in flash/SRAM speciefied in file TIRTOS_ROM.icf file for the CC1310 chip, such as the symbol const_xdc_runtime_Error_policy__C.

Are these symbol must be at these address? Is there any method to place these symbol be in some address by application? It is my block to design the flash layout due these symbols with fixed address.

Thanks,

HH

  • And another question for these symbols, are there more symbols will be added or the address changed in TIRTOS_ROM.icf file furture?

    Thanks,
    HH
  • user1730962 said:
    Are these symbol must be at these address?

    Yes, the addresses represent code and data in a fixed ROM, so they must stay as they are in TIRTOS-ROM.icf.

    user1730962 said:
    It is my block to design the flash layout due these symbols with fixed address.

    Are you wanting to place the code and data that these ROM symbols represent in your flash?

    I guess I don't understand your issue, how does the specific ROM location of these symbols affect your flash layout?

    Regards,

    - Rob

  • user1730962 said:
    And another question for these symbols, are there more symbols will be added or the address changed in TIRTOS_ROM.icf file furture?

    No, the addresses will not change, nor will any more be added.  The addresses represent a fixed snapshot of the particular part being currently produced.  A different ROM would be a different chip.

    Regards,

    - Rob

  • Hi Rob

    Thansk for you reply. I want a confirm on these symbol information and your answer is enough for me.

    For my purpose, I want to implement a upgrading over the air feature and I need the a flash layout, so I post this question and want a confirm.

    BTW, I have taken a look on the OAD example provided in BLE stack installation, and I guess this is one of reason that the on-chip OAD solution can not make OAD on the image A.

    Thanks agian.
    HH