• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 82 subscribers
  • Views 364 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.

allocation problem of Sections in .out File

Sertac Bugra Kaya
Prodigy 140 points

Hi,

We try to bootload F28335 through eCAN and load my application code into flash of F28335. We have an interface that converts .out file into ascii hex file. We can examine the .out file's memory section with this interface parsing capabilities.

After conveting .out file to ASCII Hex format , It consists of the sections shown below.

 -Section#-  -Start Address-  -Block Size-  -End Address-  -Write Status- 
1 - 00311c48 - 0c23 - 0031286b - False
2 - 00312cdd - 0004 - 00312ce1 - False
3 - 00301d34 - e8d5 - 00310609 - False
4 - 00310609 - 163f - 00311c48 - False
5 - 0031288a - 0174 - 003129fe - False
6 - 00312c52 - 0055 - 00312ca7 - False
7 - 00312b33 - 011c - 00312c4f - False
8 - 003129fe - 0135 - 00312b33 - False
9 - 00300000 - 0100 - 00300100 - False
10 - 0000e9a0 - 0004 - 0000e9a4 - False
11 - 0000e30c - 0100 - 0000e40c - False
12 - 00312c4f - 0003 - 00312c52 - False
13 - 0033fff6 - 0002 - 0033fff8 - False
14 - 00312ca7 - 0036 - 00312cdd - False
15 - 0031286b - 001f - 0031288a - False
16 - 00300100 - 1c34 - 00301d34 - False

ASCII hex file has the sections whose start adress belong to RAM. ,Because of this, FlashProgram function of FLASH API gives error when I try to copy data from RAM inti FLASH.  

My question is that is it normal to be found these kind of memory sections  in ASCII HEX file ??

Best Regards

Sertac

  • 0
    TI__Guru* 95315 points

    Sertac,

    As mentioned in the other post, https://e2e.ti.com/support/microcontrollers/c2000/f/171/p/545511/2006929#2006929 , you need to examine your linker command files and map file. Not sure why you have a Flash based linker command file and a RAM based linker command file in the same project. It is conceivable one is excluded from the build configuration. You clearly have code sections that are mapped to RAM. Only uninitalized data sections can go in RAM for applications meant to run off flash. If you are using two linker command files, resolve conflicts between the two and ensure there are no code sections mapped to RAM. You can verify this with the help of the MAP file. That should fix the issue.