How to remove xdc.meta data from image

The CCS ROV tool uses the information contained in the xdc.meta section to know how to interpret the binary image.

Removing the xdc.meta section from the image will result in ROV not being usable for that application.

The xdc.meta section does not occupy any memory in the target. It exists only in the file.

Do you really need to remove it?

Alan

Hello Alan,

thanks.

If the meta would be only in the out file, I would not have a problem with it,
but it looks for me, that it is also within the h file generated via AISgen.

When starting developing on the OMAPL-138, I observed that AISgen had
overwritten my ARM code with the meta data and when running out of the flash
this meta data "code" was executed which leads to ARM exceptions.
When looking into the map file I saw that xdc.meta was using same addresses (0xc0002100) as my code:

xdc.meta   0    c0002100    000000f8     COPY SECTION
                  c0002100    000000f8     ARM9_OS_SPIW_ELF_configuration_xe9.oe9 (xdc.meta)

.text      0    c0002100    000150e0    
                  c0002100    000041b8     taskPM.obj (.text)

As a solution I added in my configuration the following section map:

Program.sectMap["xdc.meta"] = new Program.SectionSpec();
Program.sectMap["xdc.meta"].loadSegment = "META";
Program.sectMap["xdc.meta"].type = "COPY";

and within my own custom platform a memory section "META".

With this, I had no overlapping of xdc.meta and .text section and the code worked fine, extract from the new map file:

xdc.meta   0    c0002100    000000fc     COPY SECTION
                  c0002100    000000fc     ARM9_OS_SPIW_ELF_configuration_xe9.oe9 (xdc.meta)

.text      0    c0002300    000150b8    
                  c0002300    000041b8     taskPM.obj (.text)

As ROV will not be usable I aggree to not remove xdc.meta data.

However, why are the xdc.meta data in the generated h file?
You were stating, that it does not occupy any memory in the target and I also read this in other threads.

Is this a problem of AISgen and I need a new one?
Is there anything else which must be changed to get rid of xdc.meta data in the target image (generated h file)?

Frank

Frank, I'm not familiar with the AISgen tool you're referencing. I don't know about the associated header file nor how it is used. When I load an application that contains xdc.meta data using CCS, the xdc.meta data IS NOT written to the target. Alan

Alan,

that's what I also observed: loading the out file with the emulator (CCS) my code is loaded/executed and NOT the xdc.meta data.

Shall I open a new ticked for AISgen or can you internally (within TI) forward this thread to someone who is familiar with it?

Thanks,
Frank

Frank,

Please file a ticket for AISgen.

Alan