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.

warning: section falls in unconfigured memory (skipped)



Hello,

When I generate a hex file, I get a warning as per the title. I'd like to remove the warning but not sure what it is telling me.

I am generating a hex file using post-build steps as follows:

${CG_TOOL_HEX} ${command} ${flags} ${output_flag} ${output} ${inputs} ../hex_file_all_sectors_image.hexcmd

The content of my command file is:

..\CPU1_FLASH\CPU1.out
--image
--intel
ROMS
{
    ALL_FLASH_SECTORS: org = 0x80000, len = 0x40000, romwidth = 16, fill = 0xFFFF
                       files = { CPU1_IMAGE.hex }
}

The actual hex file contents are correct as far as I can tell I get the following warning:

warning: section ..\CPU1_FLASH\CPU1.out(dclfuncs) at 0124h falls in
   unconfigured memory (skipped)

Section 'dlcfuncs' is directed to RAMM0 at 0x0123 in the linker command file:

    dclfuncs           : > RAMM0,       PAGE = 0, ALIGN(2)

Questions:

  1. Why does hex2000 think I should be warned about this?
  2. How can I avoid the warning please?

Thank you.

  • I need to reproduce the same warning diagnostic.  In order to that, I need you submit two files.

    Use CCS to perform the part of the build that includes running the hex utility.  Then save the contents of the Console (not Problems) view to a text file.  Use the icon named Copy Build Log.  When you name the log file, be sure to use the file extension .txt

    I also need the file CPU1.out.

    Put both CPU1.out, and the build log text file, in a zip file, then attach it to your next post.

    Thanks and regards,

    -George

  • CPU1_FLASH.zip

    Thanks. I attached files as requested.

  • The warning is correct.  Because of these lines in the hex2000 command file ...

    ROMS
    {
        ALL_FLASH_SECTORS: org = 0x80000, len = 0x40000, romwidth = 16, fill = 0xFFFF
                           files = { CPU1_IMAGE.hex }
    }

    ... the hex utility ignores sections with an address outside the ALL_FLASH_SECTORS memory range.  The only such section is dclfuncs, which starts at address 0x124.  

    You probably mean for this section to load in flash, and run at an address in RAM.  To learn how to do that, please see this forum post.

    Thanks and regards,

    -George

  • Thanks George. I will look into this.