Amaresh-
> I some time back i played with COFF file
format.
> As such i didnt come across any document related to
> "idata" section format. The best thing is to findout
> from the initial code of the runtime loadable object
> file. The initial code which loads the consts and
> other section.
> Hope this helps you
Mystery solved last night. They are actually .cinit sections; CCS saves
them for the end of the load. You won't see them unless you have
load-time autoinitialization turned on.
My problem was that our COFF loader STILL did not understand the correct
COFF file format for .cinit sections; it was finding far fewer than it
should. Evidently TI has made some changes in .cinit record formatting
that are not documented, maybe it's a V2 COFF thing, I don't know.
Anyway, our loader is finding all .cinit sections now, and they match
CCS's ".idata" sections, so I'm Ok with that.
Thanks for your help Amaresh.
-Jeff
> --- Jeff Brower <> wrote:
>>
>>
>> Does anyone know about "idata" sections in TI's COFF
>> file format? When
>> CCS loads a COFF file, at the end it also loads
>> sections that appear to be
>> in addition to what's documented in the C6xxx COFF
>> file format. I.e. not
>> cinit, not .const, not .data, etc. but in addition
>> to those. We're trying
>> to figure out how to extract these from the COFF
>> file and load them.
>>
>> One clue: if we look at the addresses that go past
>> when CCS is loading
>> idata sections, then check memory at those
>> addresses, we can see a number
>> of symbols, things like cleanupptr, dtors, lock,
>> unlock, etc. These
>> appear to be CSL and/or DSP/BIOS symbols and they
>> are in fact in the COFF
>> file, at the tail end near the symbol table... but
>> how to deal with any
>> data associated with them?
>>
>> One of our engineers believes this is some COFF
>> formatting that has been
>> added to support DSP/BIOS but is not yet documented.
>>
>> Jeff Brower
>> system engineer
>> Signalogic
>>
>> _____________________________________
>> Note: If you do a simple "reply" with your email
>> client, only the author of this message will receive
>> your answer. You need to do a "reply all" if you
>> want your answer to be distributed to the entire
>> group.
>>
>> _____________________________________
>> About this discussion group:
>>
>> To Join: Send an email to
>>
>>
>> To Post: Send an email to
>>
>> To Leave: Send an email to
>>
>>
>> Archives: http://www.yahoogroups.com/group/c6x
>>
>> Other Groups: http://www.dsprelated.com
>>
>>
>> ">http://docs.yahoo.com/info/terms/
>>
>
> __________________________________
> _____________________________________
> Note: If you do a simple "reply" with your email client, only the
author
> of this message will receive your answer. You need to do a "reply
all" if
> you want your answer to be distributed to the entire group.
>
> _____________________________________
> About this discussion group:
>
> To Join: Send an email to
>
> To Post: Send an email to
>
> To Leave: Send an email to
>
> Archives: http://www.yahoogroups.com/group/c6x
>
> Other Groups: http://www.dsprelated.com
> ">http://docs.yahoo.com/info/terms/
>
|