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.

Map file format and mapping of code in flash memory



Hi,

I have been using LM4F232 stellaris micro controller and CCSV5.1 compiler for my application. While developing I found that for different application; CCS generate different entry point address ( ENTRY POINT SYMBOL: "_c_int00"  address: 000004c5). When I saw the map file; i came know that,  actual code map in flash memory is some what like this - .intvecs at 0th address.  +  memcpy_t2.obj + auto init code + main application code + copy_decompress_rle.obj + cpy_tbl.obj + boot.obj (boot loader provided by stellaris) + exit.obj  and so on.... Actually I have to know how does  compilers map all these object files or different modules in flash memory. is there any special format of mapping all modules like : Int vects  + Code to copy + init code + Application code + bootloader code + ...etc.?  (On this mapping compiler determines the entry point address.). please let me know if there any document regarding this.

  • It is probably easiest to do a search of the c:\ti\... directory and find the pdf files -- and the index files for html. The only caution is that there are likely multiple directories as additional compilers are added.

    What I did was make a folder for the Stellaris material on my desktop and insert links to the compiler, PinMUX,  LMFlash, my Hex calculator, CodeCompare and any other necessary utilities.

    I then made links for all the PDF files relevant to each processor I work with. The user guides and MCU manuals go there.

    I also create a Help directory for each compiler version and place the manuals there for the compilers etc. Some of the Help is in HTML format -- like the Dinkum Compilers -- so I make a link to the index and any others I feel to be worthwhile.

    If you are searching for pdf links on the main site -- I find it best to remove the "pdf" extension and do a search. For whatever reason the link give above does not work -- but a search for the manual name does turn up the correct document.

  • Thanks for reply. I got the document. Dave, thanks for your suggestion, i would like to follow your method in my project.