CODECOMPOSER: Resolving warning: section xx.out at 020000h falls in unconfigured memory

Hi George,

We had ROMS directive multiplied by 2 already.

The Flash and RAM linker command as follows.

BEGIN                             : origin = 0x080000, length = 0x000002  // Update the codestart location as needed
FLASH_BOOT_CODE  : origin = 0x080002, length = 0x003FEC, fill = 0xFFFF
BOOT_FUNCTION_ID : origin = 0x083FEE, length = 0x000002, fill = 0xFFFF /* Function ID record  */
BOOT_VERSION           : origin = 0x083FF0, length = 0x000010, fill = 0xFFFF /* Boot version record */
…
RAMGS0             : origin = 0x010000, length = 0x002000
…
ramgs0 : > RAMGS0, type= NOINIT

ROMS {
  all_mem: o = 0x100000, l = 0x8000
}

W can produce a .bin of 32kb w/o problem.

Next, customer wants to have DMA buffer initializes the configuration to GS RAM -> ramgs0, the initialization procedure is as follows 

#pragma SET_DATA_SECTION("ramgs0")
Create_DMA_Object(dmaDcanRxObj, 16, DmaRegs.CH1);
#pragma SET_DATA_SECTION()

The warning: section BOOT.out(ramgs0) at 020000h falls in unconfigured memory
(skipped) shows up again.

However, if I remove type= NOINIT from linker (as below), the above warning disappears, but user hopes the ramgs0 zone is not initialized.

Is there a way to meet ramgs0 isn't initialized and also the warning is gone ?

Thanks for the comment.

Regards,

Johnny

Please configure things so this occurs ...

Johnny Chen said:

"C:/ti/ccs1271/ccs/tools/compiler/ti-cgt-c2000_22.6.1.LTS/bin/hex2000.exe" -q -b -image -o "BOOT.bin" roms_directive_file.txt "BOOT.out"

 warning: section BOOT.out(ramgs0) at 020000h falls in unconfigured memory

Please put these files in a zip and attach it to your next post.

• linker command file
• roms_directive_file.txt
• BOOT.out

Thanks and regards,

-George

Hi George,

Attach a zip file contains partial linker command file and roms_directive_file.txt.

Customer could not provide the .out file to us.

So the question is that is there a way to have ramgs0 not initialized in linker command file, and also have the warning removed after compilation ?

5126.files.zip

Thanks for your support.

Johnny

Based on the roms directive file, the section ramgs0 is out of range.  I suspect that is intentional.

If the section ramgs0 is uninitialized (similar to .bss), then this diagnostic ...

George Mock said:

warning: section BOOT.out(ramgs0) at 020000h falls in unconfigured memory

does not get emitted.  Since it is emitted, I am forced to conclude ramgs0 is initialized (similar to .const).  Is this intentional, or some kind of error?  Based on the section name alone, I expect it to be uninitialized.

Thanks and regards,

-George

Hi George,

Thanks for your input. 

George Mock said:

Based on the section name alone, I expect it to be uninitialized.

Yes, agree with you. It should be uninitialized for the section here. 

George Mock said:

Is this intentional, or some kind of error? 

Are you saying the warning is because of user's defined linker command file or our CCS ? 

Is there any solution to this ?  

Thanks,

Johnny

Please get a better understanding of the terms initialized section and uninitialized section by searching the C28x assembly tools manual for the sub-chapter titled How the Assembler Handles Sections.  

Because we see the diagnostic ...

Johnny Chen said:

warning: section BOOT.out(ramgs0) at 020000h falls in unconfigured memory

... we know ramgs0 is an initialized section.  This diagnostic also means ramgs0 is not in the .bin file.  The program needs this initialized data, or it won't work.

Everything else we see about ramgs0 indicates it is intended to be uninitialized.  So, we need to understand why it is initialized instead.  None of the files you sent earlier help explain why it is initialized.

How does ramgs0 get created?  Please consider this question at the level of the C code (or assembly code) which creates it.  It is likely that it is created in a single C file.  If that is correct, then for that C file, please follow the directions in the article How to Submit a Compiler Test Case.  Note this calls for submitting much less than an entire CCS project.

Thanks and regards,

-George

Hi George,

Thanks for your input. I agree with your analysis.

George Mock said:

How does ramgs0 get created?  Please consider this question at the level of the C code (or assembly code) which creates it.

It is just an output section named by user then allocate to the actual memory RAMGS0 in device. There is no such C code (or assembly code) that creates the ramgs0.

What user does here is naming an output section then allocate to memory in device, then have the data specifically copied to that output section. 

Customer also have tried to assign the data (using #pragma SET_DATA_SECTION) to other section in main code, the diagnostic follows. 

Is it because of all the output section address out of the range of the ROMS directive ?

The ROMS directive is all_mem: o = 0x100000, l = 0x8000

Thanks for your support.

Regards,

Johnny