• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 744 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.

CINIT section problem

Dalibor Kuchta
Prodigy 60 points

Hello,

I use myself loader for loading application to external memory. Now I want load also CINIT section directly to ebss section(ram-model auto inicialization). Hex file (Intel MCS-86 Object Format) is generated by hex2000 utility. Source ".out" file is off-course linked in "ram-model". The problem is that output hex binary file does not contains CINIT section, so from this file is impossible to completely  init application. In hex binary file generated from "rom-model" linked applicatin CINIT section is included and everything is OK.

Does any body know where is problem ?

  • 0
    TI__Guru**** 253230 points

    I suspect you use the output of hex2000 to program some Flash memory.  If that is the case, then you cannot use the RAM model of auto-initialization (I'll call it RAM model for short).  RAM model presumes that, as a side effect of loading, you can copy values into the part of RAM used by .ebss.  All of this initialization of RAM must occur before the system begins execution.  There is no way to accomplish that as a side effect of programming Flash.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 60 points

    I use off-course generated file to load off-chip RAM memory and whole appplication run from this RAM memory, so this is not problem. I saw information about CINIT in map file, but I can find this section in output Intel format file.

    Thanks for reply

    Dalibor