• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 55 subscribers
  • Views 1125 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.

Original question:

hex2000 says "section XYZ falls in unconfigured memory"

CCS/TMS320F280045: Hex2000 Says "Section X.out (.ecc#) at 01080000h falls in unconfigured memory

Jose Lopez2
Prodigy 180 points

Part Number: TMS320F280045

Tool/software: Code Composer Studio

Hi,

I have a project for the F280045 for which I have Flash ECC enabled.  I added the ECC memory ranges to the Linker Command File MEMORY section using the correct start address according to SPRS945C table 6-2 (i.e. 0x01080000 for bank 0) and a length of 1 byte for every 8 bytes of flash memory covered.  This is all tested and works well (compiles, runs and is able to detect ECC errors). I will need to convert the OUT file to a HEX file for flashing.

I was using the following in CCS Build -> Steps -> Post-Build steps:

"${CG_TOOL_HEX}" -i "${BuildArtifactFileName}" -o "${BuildArtifactFileBaseName}.hex" -romwidth 16

After a succesful compilation and linking, the hex2000 application gives me the following warning:

warning: section DSP.out(.ecc2) at 01080000h falls in unconfigured memory

Effectively, the memory addresses after 0x01080000 were not included as part of the resulting HEX file.

I tried removing the post build steps and using the C2000 Hex Utility options on the project properties (which I assume should be equivalent).   I enabled the utility, selected intel output and configured the romwidth option to 16.  I obtain the same warning in the console and the HEX file still doesn't contain the ECC memory ranges.  I added the option to create a mapfile output, the CONTENTS section doesn't list the ECC memory ranges.

What I understand from SPRU513 is that the ranges defined Linker Command File would be "configured memory" and would be used to create the HEX file, but it doesn't seem to be the case for the ECC memory. 

I have a similar project for the TMS570LS033x using ECC as well and it works without a problem using post build steps similar to the described above (romwidth = 32)

I would like to avoid duplicating what is already specified in the Linker Command File in a command file to use the hex2000 ROMS directive (haven't tried and not sure if this works).  Is there something else I could try or is this the only path to include the ECC ranges in the HEX output?

Thanks in advance,

Jose Lopez

  • 0
    TI__Guru**** 252280 points

    Please see if you have the problem described in this forum thread.  In summary, make sure everything in the linker command file is on PAGE 0.

    Please let me know if this resolves the problem.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 180 points

    Hi George,

    Thanks for your reply.  All my flash memory related ranges were allocated to PAGE 0 (including the ECC ranges).  I have some RAM ranges allocated to PAGE 1.

    I tried allocating them all to page 0 and got the same warning.

    Thanks,

    Jose Lopez

  • 0 in reply to Jose Lopez2
    TI__Guru**** 252280 points

    I'm not sure what is happening.  I need to reproduce the problem and then investigate.

    It would be ideal if you submitted your CCS project.  Please zip up the project by using the directions in the article Sharing projects, then attach that zip file to your next post.

    If that is not practical, then zip up the final executable .out file and attach it to your next post.  Also show exactly how the hex utility is invoked.  Copy and paste the text from the CCS Console (not Problems) view.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 180 points

    Hi George,

    I can't submit my real CCS project, but I created a new project and configured it similarly and obtained the same results.  Find it attached.

    The command used to run HEX2000 and the results of running it are the following:

    Invoking: C2000 Hex Utility
    "C:/ti/ccs1000/ccs/tools/compiler/ti-cgt-c2000_20.2.1.LTS/bin/hex2000" --map="TestProject2.map" --romwidth=16 --intel -o "TestProject.hex" "TestProject.out"
    Translating to Intel format...
    "TestProject.out" .text ==> .text
    "TestProject.out" .cinit ==> .cinit
    "TestProject.out" .ecc0 ==> .ecc0
    "TestProject.out" .ecc2 ==> .ecc2
    "TestProject.out" .ecc1 ==> .ecc1
    warning: section TestProject.out(.ecc0) at 01080000h falls in unconfigured memory (skipped)
    warning: section TestProject.out(.ecc2) at 01080001h falls in unconfigured memory (skipped)
    warning: section TestProject.out(.ecc1) at 01082000h falls in unconfigured memory (skipped)

    Ideally you should obtain the same after importing.

    Notice that disabling the ECC generation in the linker options  (--ecc = off) removes the warning. The OUT file with ECC generated is about 49K, while without it is about 17K. This means that the ECC data is added to OUT.  The ECC data is not included in the HEX regardless.

    3157.TestProject.zip

    Let me know if you need anything else.

    Thanks,

    Jose Lopez

  • 0 in reply to Jose Lopez2
    TI__Guru**** 252280 points

    Thank you submitting a test case.  I can reproduce the problem.  It does appear to be a bug in the hex utility.  I filed the issue EXT_EP-10052 to have this investigated.  You are welcome to follow it with link below in my signature.

    Thanks and regards,

    -George

  • 0
    TI__Guru* 84285 points

    The C2000 hex conversion utility by default thinks that C2000 binaries can only have 22-bit addresses.  This used to be true, but not when ECC is present.

    You can work around this issue by using a hex conversion utility command file:
    /*
    hex2000 thisfile.cmd <the rest of your options>
    */
    ROMS
    {
        ROW1: origin=0x00000000 len=0x100000000
    }