Backstory:
I am developing on the L138 in raw C because there is no big need for a
complicated OS and because i have no experience with embedded operating
systems like this. And i am writing my own bootloader as you need one to
fire up the DSP and i plan to also bootload the ARM core as well since
it provides some nice robustness for firmware updates (Never overwrite
the bootloader so bad firmware still allows a SD card firmware update)
So to feed the bootloader i use .bin files that get copied in to memory
and run and it worked great to load a DSP led blinker on to my hawkboard
but when i tried to load in a ARM led blinker it just didn't want to
work so i spent a day wrestling with it only to find out the .bin file i
made using ccs was bad. In the end i debug ran the ARM led blinker and
left it sit on the start while using the memory debug window to download
the entire ARM RAM in to a .bin file and loaded that instead, that file could be ran using my bootloader without problems.
So to export the .bin files from ccs i tried two different postbuild
commands that produce a different(content and file size) .bin file but
none of them work:
-1st try:
"${CCE_INSTALL_ROOT}/utils/tiobj2bin/tiobj2bin.bat"
"${BuildArtifactFileName}" "${BuildArtifactFileBaseName}.bin"
"${CG_TOOL_ROOT}/bin/ofd470.exe" "${CG_TOOL_ROOT}/bin/hex470.exe"
"${CCE_INSTALL_ROOT}/utils/tiobj2bin/mkhex4bin.exe"
-2nd try:
"${CG_TOOL_ROOT}/bin/hex470.exe" -b -o"${BuildArtifactFileBaseName}.bin" "${BuildArtifactFileName}"
Best thing to do is probably making my bootloader interpret *.ais files
as they also work with code in different memory spaces without making a
gigantic .bin and carry the program entry point in them. But still there
has to be a way of getting a .bin of your program.