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.

About generating input sections and what is inside

Hello everyone,

Here is a snapshot from .map file.

-------------------------------------------

SECTION ALLOCATION MAP

 output                                  attributes/
section   page    origin      length       input sections
--------  ----  ----------  ----------   ----------------

.sdram     0    80510000    000bcc00     UNINITIALIZED
                80510000   00094800            _in_img
                805a4800   00000640            _draw_p
                805a4e40   00000640            _draw_unp
                805a5480   00000640        _eraz_p
                805a5ac0   00000640        _eraz_unp
                805a6100   00000640        _clear_unp
                805a6740   00000640        _clear_p
                805a6d80   00000640        _ppt_p
                805a73c0   00000640        _ppt_unp
                805a7a00   00025200        _Binary_Buffer_PPT_BU

I realized that the _in_img section is very large, I am wondering what is inside and when is it generated.

From the data sheet, I know this input section should contain some variables as it is inside .sdram.

But it is too large to be a single variable, right?

Can anyone tell me what the contents are? or is there anyway to check the content inside?

**I am thinking that it may consist of several image data, for example a 320*240 lcd need 76800 bytes for a full frame of image, supposing that each pixel consumes one bytes.

here it is 94800, while, if anyone has any idea, please let me know.

Thank you very much!

-da

  • There is no way to tell from the map file alone what is contained in this section.  You will need to look at your source code and linker command file to understand what contributes to this input section.

    Based on the name, and this is purely a guess, the _in_img section represents a buffer, or series of buffers, of image data as you mentioned.  But again, that is pure speculation at this point.  You will need to review the source code and determine this for yourself.