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.
Tool/software: Code Composer Studio
Hi Ti supporter,
I am working on EVM5517 RefF board. My project is completed, and now, I want to build project from .out file to .bin file. I'm trying but unsuccess.
I have added "
${CCE_INSTALL_ROOT}/utils/tiobj2bin/tiobj2bin ${BuildArtifactFileName} ${BuildArtifactFileBaseName}.bin ${CG_TOOL_ROOT}/bin/ofd55 ${CG_TOOL_ROOT}/bin/hex55 ${CCE_INSTALL_ROOT}/utils/tiobj2bin/mkhex4bin
" into Post-bulid steps.
Then, Console shows Binary files do not work for C5500
I want you confirm " Can CCS build from .out file to .bin file? "
Thank you and Best regards
Please read the article Linker Command File Primer. Focus on understanding these concepts.
With regard to pages of memory ... The article states memory pages are only used in C28x linker command files. That's because, at the time this article was written, it was thought that no C5500 development was occurring. It turns out C5500 also has memory pages, and they work the same way as on C28x.
With all of that new knowledge in mind ... I presume your program has initialized output sections on PAGE 0. Does it also have initialized output sections on PAGE 1?
Thanks and regards,
-George
Hi George
I reviewed my project, all output sections are initialized on PAGE 0, not PAGE 1. And output sections (.data, .const,..etc) are initialized.
I think that EVM5517 is not supported for .bin file output because I already worked with CC3220 module and built success .bin file output.
Thanks
You can use the hex utility hex55 to create a binary file.
Use the option --binary to get binary output.
A binary file has no address discontinuities. Therefore, you must use the --image option. Please search the C5500 assembly tools manual for the sub-chapter titled Image Mode and the --fill Option.
Because you use image mode, you have provide a ROMS directive. Please search the same manual for the sub-chapter titled The ROMS Directive. It usually has the same lines as the MEMORY directive in the linker command file, though you can leave out memory ranges which contain no initialized sections.
When you put it all together, the command looks similar to ...
% hex55 --binary --image executable_file.out -o binary_file.bin roms_directive.cmd
The input file is executable_file.out, and the output binary file is binary_file.bin.
Thanks and regards,
-George