TMS320F28027F: After Enabling Hex Utility and selecting output format as --ti-txt,many warnings are generated related to unconfigured memory

Can you tell me what flags you're using with the hex utility?

Whitney

I am enabling the C2000 Hex Utility and then in Output Format options I have selected TI-TXT hex format.

I tried but it still didn't work.Can you tell me the steps so that I can verify if I have done it correctly or not.The information is all confusing and scattered.

Are your memwidth and romwidth settings set to 16?

I have set it to 8.But for ti-txt format ,its default to 8 bit right?

Have you created a file containing a ROMS directive?

Contents of ROMS directive

//-------------------------------------------------------------

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

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

//---------------------------------------------------------------------------------

Have you edited the command line pattern in the project properties to specify that file as shown in this wiki page?

Yes,I have modified the memory width and rom width to 8 as per the link.

In Build->Post build steps:

path/hex2000.exe path/mkhex.cmd  

I still get the error that IMD.out  not found.If I check hex utility and add post build steps, then out file is not generated.

I have used the extension to .txt. The post built steps failed as permission is denied.

Here is the console output.

Building target: "IMD_V0.14.out"
Invoking: C2000 Linker
"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.2.LTS/bin/cl2000" -v28 -ml -mt -O2 --advice:performance=all --define=FLASH --define=FAST_ROM_V1p7 --define=F2802xF -g --diag_warning=225 --display_error_number --asm_listing -z -m"IMD_V0.14.map" --stack_size=0x200 --warn_sections -i"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.2.LTS/lib" -i"C:/Users/Admin/workspace_v8/IMD_V0.14/headers/" -i"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.2.LTS/include" --priority --reread_libs --disable_auto_rts --diag_suppress=16002 --xml_link_info="IMD_V0.14_linkInfo.xml" --rom_model -o "IMD_V0.14.out" "../2802xRevB_Fast_IQ_ROMSymbols.lib" "../2802xRevB_Fast_ONLY_ROMSymbols.lib" "../2802xRevB_Fast_RTS_ROMSymbols.lib" "../fast_public.lib" "../IQmath.lib" "./CodeStartBranch.obj" "./adc.obj" "./clarke.obj" "./clk.obj" "./cpu.obj" "./ctrl.obj" "./filter_fo.obj" "./flash.obj" "./fw.obj" "./gpio.obj" "./hal.obj" "./ipark.obj" "./memCopy.obj" "./offset.obj" "./osc.obj" "./park.obj" "./pid.obj" "./pie.obj" "./pll.obj" "./proj_lab10a.obj" "./pwm.obj" "./pwr.obj" "./svgen.obj" "./svgen_current.obj" "./timer.obj" "./traj.obj" "./usDelay.obj" "./user.obj" "./wdog.obj" "../F28027F.cmd" -llibc.a
<Linking>
Finished building target: "IMD_V0.14.out"

Building files: "IMD_V0.14.out"
Invoking: C2000 Hex Utility
"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.2.LTS/bin/hex2000" --map="IMD_V0.14.map" --memwidth=8 --romwidth=8 --ti_txt -o "IMD_V0.14.txt" "IMD_V0.14.out"
Translating to TI-TXT format...
"IMD_V0.14.out" .text ==> .text
"IMD_V0.14.out" ramfuncs ==> ramfuncs
"IMD_V0.14.out" .cinit ==> .cinit
"IMD_V0.14.out" codestart ==> codestart
"IMD_V0.14.out" .econst ==> .econst
warning: section IMD_V0.14.out(.text) at 07e0000h falls in unconfigured memory
(skipped)
warning: section IMD_V0.14.out(ramfuncs) at 07e667ah falls in unconfigured
memory (skipped)
warning: section IMD_V0.14.out(.cinit) at 07e7596h falls in unconfigured memory
(skipped)
warning: section IMD_V0.14.out(codestart) at 07effech falls in unconfigured
memory (skipped)
warning: section IMD_V0.14.out(.econst) at 07ec000h falls in unconfigured
memory (skipped)
Finished building: "IMD_V0.14.out"

C:\ti\ccsv8\tools\compiler\ti-cgt-c2000_18.1.2.LTS\bin\hex2000.exe C:\Users\Admin\workspace_v8\IMD_Pro35K_V0.14\mkhex.txt
makefile:198: recipe for target 'post-build' failed
fatal error: cannot open input file
"C:\Users\Admin\workspace_v8\IMD_Pro35K_V0.14\mkhex.txt": Permission denied
gmake[1]: [post-build] Error 1 (ignored)


**** Build Finished ****

You shouldn't need to call hex2000 in a post-build step. Checking the "Enable C2000 Hex Utility" box should already cause hex2000.exe to run after the build.

Add the file with the ROMs directive in the hex utility command-line pattern instead.

Whitney

I am still not sure how to adjust the length and origin in ROMS directive.Can you suggest a document which explains this information.

MAP file.zip

The best document for it is here:

www.ti.com/lit/ug/spru513p/spru513p.pdf

Looking at your .map file it's still not clear to me why you're still getting warnings. Can you share your current ROMS directive too?

Whitney

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

ROMS
{
FLASH: origin=0x7a0000, length=0x8FF00
}

Here are the build errors

//----------------------------------------------------------------------------------------------------------

Building target: "IMD_V0.14.out"
Invoking: C2000 Linker
"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.2.LTS/bin/cl2000" -v28 -ml -mt -O2 --advice:performance=all --define=FLASH --define=FAST_ROM_V1p7 --define=F2802xF -g --diag_warning=225 --display_error_number --asm_listing -z -m"IMD_V0.14.map" --stack_size=0x200 --warn_sections -i"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.2.LTS/lib" -i"C:/Users/Admin/workspace_v8/IMD_V0.14/headers/" -i"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.2.LTS/include" --priority --reread_libs --disable_auto_rts --diag_suppress=16002 --xml_link_info="IMD_V0.14_linkInfo.xml" --rom_model -o "IMD_V0.14.out" "../2802xRevB_Fast_IQ_ROMSymbols.lib" "../2802xRevB_Fast_ONLY_ROMSymbols.lib" "../2802xRevB_Fast_RTS_ROMSymbols.lib" "../fast_public.lib" "../IQmath.lib" "./CodeStartBranch.obj" "./adc.obj" "./clarke.obj" "./clk.obj" "./cpu.obj" "./ctrl.obj" "./filter_fo.obj" "./flash.obj" "./fw.obj" "./gpio.obj" "./hal.obj" "./ipark.obj" "./memCopy.obj" "./offset.obj" "./osc.obj" "./park.obj" "./pid.obj" "./pie.obj" "./pll.obj" "./proj_lab10a.obj" "./pwm.obj" "./pwr.obj" "./svgen.obj" "./svgen_current.obj" "./timer.obj" "./traj.obj" "./usDelay.obj" "./user.obj" "./wdog.obj" "../F28027F.cmd" -llibc.a
<Linking>
Finished building target: "IMD_V0.14.out"

Building files: "IMD_V0.14.out"
Invoking: C2000 Hex Utility
"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.2.LTS/bin/hex2000" --memwidth=8 --romwidth=8 --ti_txt -o "IMD_V0.14.txt" "IMD_V0.14.out" "C:\Users\Admin\workspace_v8\IMD_V0.14\mkhex.txt"
Translating to TI-TXT format...
"IMD_V0.14.out" .text ==> .text
"IMD_V0.14.out" ramfuncs ==> ramfuncs
"IMD_V0.14.out" .cinit ==> .cinit
"IMD_V0.14.out" codestart ==> codestart
"IMD_V0.14.out" .econst ==> .econst
warning: section IMD_V0.14.out(.econst) at 07ec000h falls in unconfigured
memory (skipped)
Finished building: "IMD_V0.14.out"

**** Build Finished ****

So that I can reproduce the same error diagnostics, I'd appreciate if you would also submit the file IMD_V0.14.out.  So the forum will accept it, please zip it up first.  If you are reluctant to post it to the forum, then please send it just to me, with the private messaging feature of the forum.  Hover your mouse over my name or avatar.  A box will pop up. Click on Send a private message. In the message compose interface which comes up, use the paper clip icon to attach the zip file.

Thanks and regards,

-George

The solution is to change your linker command file to put the output section .econst on page 0.

Explanation ... The output section .econst is the only initialized section on page 1 which is in the memory range that should be converted by the hex utility.  Because it is on page 1, and not page 0, your current ROMS directive ...

ROMS
{
            FLASH:       origin=0x7a0000, length=0x8FF00
}

... does not cover the .econst section.  That is why you get the diagnostic about how .econst falls in unconfigured memory.  You might consider changing the ROMS directive to this ...

ROMS
{
            FLASH:       origin=0x7a0000, length=0x8FF00
   PAGE 1 : FLASH_PAGE1: origin=0x7a0000, length=0x8FF00
}

That avoids the diagnostic, and .econst does get converted.  But not like all the other output sections.  Because it is on page 1, the hex utility puts the output for .econst in a separate file.  That does not solve the problem.

So, the solution is to change the linker command file so the output section .econst is on page 0.

Thanks and regards,

-George

We have tried moving the output section.econst to page 0 .The code composer did not throw any warnings but GANG programmer did.I have attached the the modifications that we did and the error we got.

Modifications.docxlinker command file.zip

Can you please confirm if the modifications that we have done are correct? Secondly do you provide any flasher tool like MSP flasher with which we can program the controller using ti-txt file.

Sorry but I accidentally clicked This resolved the issue.

Hi Abhishek,

Are you able to program your project within CCS using your modified linker command file? What about if you program the .out or .hex file using Uniflash, do the program and verify stages succeed?

Best,
Kevin

P.S. Can you provide your .map and .hex files after building in CCS?

I am able to built the code and generate ti-txt file.But gang programmer and the uniflash gives an error when i upload the ti-txt file .Here are the files

1565.files.zip

Thanks for your patience. I'm exchanging some e-mails with the Uniflash and hex utility experts, trying to get to the bottom of this. We'll get back to you soon.

Whitney

Sorry for the late reply.But changing the address doesn't let me load the program.Any other suggestions.

No,its a different error. Uniflash gave this error report .

with address 0x3f0000 it says Attempted to write past the end of memory at  0x7effec@program

with address 0x7f0000 it says Attempted to write past the end of memory at  0x7e0000@program 

I got the above error when iIchanged only one address.But after this error I check the memory map,it showed that other address was  out of bound.So I changed the other address too from 0x7effec to 0x3f7ff6.

I am attaching 3 files.

1> Original File generated by Code composer

2< Replaced only 0x7e0000 by 0x3f0000

3>Replaced  0x7e0000 by 0x3f0000 and 0x7effec by  0x3F7FF6  

Error for 3

I have attached the 3 .txt files.Can you please check them

1>1.txt

2>2.txt

3>3.txt