POST-Buils /Create flash image warnings/ Piccolo 28069

Sabina Greenberg101872

Other Parts Discussed in Thread: TMS320F28069

Dear support,

We work with Piccolo 28069/ ti.platforms.tms320x28:TMS320F28069/ Sys/BYOS 6.33.3.33/ XDC Tools 3.23.4.60.
We added in POST-Buils step the command:
"${CG_TOOL_ROOT}/bin/hex${CG_TOOL_SUFFIX}" --ti_txt "${BuildArtifactFileName}" -o "${BuildArtifactFileBaseName}.txt" -order MS -romwidth 16
for Create flash image: TI-TXT.

get the following warnings:

D:/ti/ccsv5/utils/bin/gmake --no-print-directory post-build
'Create flash image: TI-TXT'
"D:/ti/ccsv5/tools/compiler/c2000/bin/hex2000" --ti_txt "PiccoloApp.out" -o "PiccoloApp.txt" -order MS
Translating to TI-TXT format...
warning: section PiccoloApp.out(.text) at 07b0000h falls in unconfigured memory
   "PiccoloApp.out"   ==> .text
   (skipped)
   "PiccoloApp.out"   ==> .econst
warning: section PiccoloApp.out(.econst) at 07c04c0h falls in unconfigured
   memory (skipped)
warning: section PiccoloApp.out(.cinit) at 07c38d0h falls in unconfigured
   memory (skipped)
warning: section PiccoloApp.out(ramfuncs) at 07c443ah falls in unconfigured
   memory (skipped)
warning: section PiccoloApp.out(.switch) at 07c4478h falls in unconfigured
   memory (skipped)
warning: section PiccoloApp.out(.pinit) at 07c44b0h falls in unconfigured
   memory (skipped)
warning: section PiccoloApp.out(.ti_catalog_c2800_init_begin) at 07effech falls
   in unconfigured memory (skipped)
   "PiccoloApp.out"   ==> .cinit
   "PiccoloApp.out"   ==> ramfuncs
   "PiccoloApp.out"   ==> .switch
   "PiccoloApp.out"   ==> .pinit
   "PiccoloApp.out"   ==> .ti_catalog_c2800_init_begin
' '

we've tried the pos-build command without '-romwidth 16', but it didn't help.

What could be the reason the these warnings? How to eliminate it?

Thanks,Sabina

over 13 years ago

0 AartiG over 13 years ago

TI__Guru**** 173310 points

Sabina,

This error occurs when the executable contains sections whose load addresses fall outside the defined memory range. In this case since you are not using the ROMS directive to define the ROM range, the memory range should default to the entire processor address space. However, I believe 0x7b0000 address range is not within the F28069 address space, hence the error.

0 Sabina Greenberg101872 over 13 years ago in reply to AartiG

Expert 2780 points

Is it possible to define ROM range? we use standard TMS320F28069.cmd. What directive should be added to this file for eliminate these warnings.

Thanks,Sabina

0 Sasha Slijepcevic over 13 years ago in reply to Sabina Greenberg101872

TI__Mastermind 37985 points

Sabina,
could you post your linker command file F28069.cmd, and also the linker command file linker.cmd generated by XDCtools? You can find linker.cmd in the directory Debug/configPkg in your project directory. From the content of these two files we should be able to tell what's the source of the warnings and how to fix it.

0 Sabina Greenberg101872 over 13 years ago in reply to Sasha Slijepcevic

Expert 2780 points

Hi Sasha,

these are files:

1727.Linker.rar

Thanks,Sabina

0 AartiG over 13 years ago in reply to Sabina Greenberg101872

TI__Guru**** 173310 points

Sabina,

I think I know what is causing the error. When you use --ti_txt output format, the width of address bits defaults to 8 (this is mentioned in the C28x Assembly Language Tools Users Guide). So the addresses and lengths of the ROMS directive are specified in terms of 8-bit bytes, and not 16-bit words. Thus, you need to double both the origin and length values of the ROMS directive to avoid this error. Please see this related thread for more information.

In your case, since FLASH begins at 0x3D8000,try adding a ROMS directive with origin at 0x7B0000 and of appropriate length.

The same Users Guide has details about the ROMS directive as well and how they can be used within hex command files.

0 Sabina Greenberg101872 over 13 years ago in reply to AartiG

Expert 2780 points

Hi,

Should I replace the command in Post-buils steps '"${CG_TOOL_HEX}" --ti_txt "${BuildArtifactFileName}" -o "${BuildArtifactFileBaseName}.txt" -order MS -romwidth 16' to the

"hex2000.exe mkhex.cmd' and with the following directive:

DummyApp.out    /* input = executable object file */
-b              /* binary */
-image          /* total flash image */
-memwidth 8
-map DummyAppRaw.map
-fill 0xffff

ROMS
{
    FLASH: origin=0x3D8000, length=0x40000, files={DummyApp.bin}
}

Thanks, Sabina

0 AartiG over 13 years ago in reply to Sabina Greenberg101872

TI__Guru**** 173310 points

Sabina Greenberg101872 said:

Should I replace the command in Post-buils steps '"${CG_TOOL_HEX}" --ti_txt "${BuildArtifactFileName}" -o "${BuildArtifactFileBaseName}.txt" -order MS -romwidth 16' to the

"hex2000.exe mkhex.cmd'

Yes, you can do that, or even better: "${CG_TOOL_HEX} mkhex.cmd" but be sure to add the full path to mkhex.cmd.

The contents of the mkhex.cmd should match your requirements, so something like the following:

PiccoloApp.out /* input = executable object file */
--ti_txt
-o PiccoloApp.txt
-order MS

ROMS
{
FLASH: origin=0x7B0000, length=0x3FF00
}

0 AartiG over 13 years ago in reply to AartiG

TI__Guru**** 173310 points

Continuation of this thread and final resolution is in this thread: http://e2e.ti.com/support/development_tools/compiler/f/343/t/188550.aspx

Code Composer Studio™︎

Code Composer Studio forum

POST-Buils /Create flash image warnings/ Piccolo 28069