CCS/CC3220: mkhex4bin error

Is that the complete text as seen in the CCS build console? 

Could you provide a screenshot of how the command looks in the post-build step and also the full output seen in the CCS build console?

This is what the post-build step looks like. I'm posting this as text instead of a screenshot since it's too long to be displayed within the post-build window.

${CCS_INSTALL_ROOT}/utils/tiobj2bin/tiobj2bin ${BuildArtifactFileName} ${BuildArtifactFileBaseName}.bin ${CG_TOOL_ROOT}/bin/armofd ${CG_TOOL_ROOT}/bin/armhex ${CCS_INSTALL_ROOT}/utils/tiobj2bin/mkhex4bin


The full build console output is

**** Build of configuration Release for project network_terminal_CC3220S_LAUNCHXL_tirtos_ccs ****

"C:\\ti\\ccsv7\\utils\\bin\\gmake" -k -j 8 all -O

'Building file: ../CC3220S_LAUNCHXL.c'

'Invoking: ARM Compiler'

"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=vfplib -me -O2 --include_path="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/network_terminal_CC3220S_LAUNCHXL_tirtos_ccs" --include_path="C:/ti/simplelink_cc32xx_sdk_1_50_00_06/kernel/tirtos/packages/ti/sysbios/posix" --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/include" --define=CC32XX -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="CC3220S_LAUNCHXL.d" --cmd_file="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/tirtos_builds_CC3220S_LAUNCHXL_release_ccs/Release/configPkg/compiler.opt" "../CC3220S_LAUNCHXL.c"

'Finished building: ../CC3220S_LAUNCHXL.c'

' '

'Building file: ../main_tirtos.c'

'Invoking: ARM Compiler'

"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=vfplib -me -O2 --include_path="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/network_terminal_CC3220S_LAUNCHXL_tirtos_ccs" --include_path="C:/ti/simplelink_cc32xx_sdk_1_50_00_06/kernel/tirtos/packages/ti/sysbios/posix" --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/include" --define=CC32XX -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="main_tirtos.d" --cmd_file="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/tirtos_builds_CC3220S_LAUNCHXL_release_ccs/Release/configPkg/compiler.opt" "../main_tirtos.c"

'Finished building: ../main_tirtos.c'

' '

'Building file: ../radio_tool.c'

'Invoking: ARM Compiler'

"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=vfplib -me -O2 --include_path="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/network_terminal_CC3220S_LAUNCHXL_tirtos_ccs" --include_path="C:/ti/simplelink_cc32xx_sdk_1_50_00_06/kernel/tirtos/packages/ti/sysbios/posix" --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/include" --define=CC32XX -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="radio_tool.d" --cmd_file="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/tirtos_builds_CC3220S_LAUNCHXL_release_ccs/Release/configPkg/compiler.opt" "../radio_tool.c"

'Finished building: ../radio_tool.c'

' '

'Building file: ../netapp_cmd.c'

'Invoking: ARM Compiler'

"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=vfplib -me -O2 --include_path="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/network_terminal_CC3220S_LAUNCHXL_tirtos_ccs" --include_path="C:/ti/simplelink_cc32xx_sdk_1_50_00_06/kernel/tirtos/packages/ti/sysbios/posix" --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/include" --define=CC32XX -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="netapp_cmd.d" --cmd_file="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/tirtos_builds_CC3220S_LAUNCHXL_release_ccs/Release/configPkg/compiler.opt" "../netapp_cmd.c"

'Finished building: ../netapp_cmd.c'

' '

'Building file: ../str.c'

'Invoking: ARM Compiler'

"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=vfplib -me -O2 --include_path="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/network_terminal_CC3220S_LAUNCHXL_tirtos_ccs" --include_path="C:/ti/simplelink_cc32xx_sdk_1_50_00_06/kernel/tirtos/packages/ti/sysbios/posix" --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/include" --define=CC32XX -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="str.d" --cmd_file="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/tirtos_builds_CC3220S_LAUNCHXL_release_ccs/Release/configPkg/compiler.opt" "../str.c"

'Finished building: ../str.c'

' '

'Building file: ../network_terminal.c'

'Invoking: ARM Compiler'

"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=vfplib -me -O2 --include_path="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/network_terminal_CC3220S_LAUNCHXL_tirtos_ccs" --include_path="C:/ti/simplelink_cc32xx_sdk_1_50_00_06/kernel/tirtos/packages/ti/sysbios/posix" --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/include" --define=CC32XX -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="network_terminal.d" --cmd_file="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/tirtos_builds_CC3220S_LAUNCHXL_release_ccs/Release/configPkg/compiler.opt" "../network_terminal.c"

'Finished building: ../network_terminal.c'

' '

'Building file: ../socket_cmd.c'

'Invoking: ARM Compiler'

"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=vfplib -me -O2 --include_path="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/network_terminal_CC3220S_LAUNCHXL_tirtos_ccs" --include_path="C:/ti/simplelink_cc32xx_sdk_1_50_00_06/kernel/tirtos/packages/ti/sysbios/posix" --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/include" --define=CC32XX -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="socket_cmd.d" --cmd_file="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/tirtos_builds_CC3220S_LAUNCHXL_release_ccs/Release/configPkg/compiler.opt" "../socket_cmd.c"

'Finished building: ../socket_cmd.c'

' '

'Building file: ../cmd_parser.c'

'Invoking: ARM Compiler'

"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=vfplib -me -O2 --include_path="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/network_terminal_CC3220S_LAUNCHXL_tirtos_ccs" --include_path="C:/ti/simplelink_cc32xx_sdk_1_50_00_06/kernel/tirtos/packages/ti/sysbios/posix" --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/include" --define=CC32XX -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="cmd_parser.d" --cmd_file="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/tirtos_builds_CC3220S_LAUNCHXL_release_ccs/Release/configPkg/compiler.opt" "../cmd_parser.c"

'Finished building: ../cmd_parser.c'

' '

'Building file: ../uart_term.c'

'Invoking: ARM Compiler'

"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=vfplib -me -O2 --include_path="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/network_terminal_CC3220S_LAUNCHXL_tirtos_ccs" --include_path="C:/ti/simplelink_cc32xx_sdk_1_50_00_06/kernel/tirtos/packages/ti/sysbios/posix" --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/include" --define=CC32XX -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="uart_term.d" --cmd_file="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/tirtos_builds_CC3220S_LAUNCHXL_release_ccs/Release/configPkg/compiler.opt" "../uart_term.c"

'Finished building: ../uart_term.c'

' '

'Building file: ../transceiver_cmd.c'

'Invoking: ARM Compiler'

"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=vfplib -me -O2 --include_path="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/network_terminal_CC3220S_LAUNCHXL_tirtos_ccs" --include_path="C:/ti/simplelink_cc32xx_sdk_1_50_00_06/kernel/tirtos/packages/ti/sysbios/posix" --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/include" --define=CC32XX -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="transceiver_cmd.d" --cmd_file="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/tirtos_builds_CC3220S_LAUNCHXL_release_ccs/Release/configPkg/compiler.opt" "../transceiver_cmd.c"

'Finished building: ../transceiver_cmd.c'

' '

'Building file: ../wlan_cmd.c'

'Invoking: ARM Compiler'

"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=vfplib -me -O2 --include_path="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/network_terminal_CC3220S_LAUNCHXL_tirtos_ccs" --include_path="C:/ti/simplelink_cc32xx_sdk_1_50_00_06/kernel/tirtos/packages/ti/sysbios/posix" --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/include" --define=CC32XX -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="wlan_cmd.d" --cmd_file="C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/tirtos_builds_CC3220S_LAUNCHXL_release_ccs/Release/configPkg/compiler.opt" "../wlan_cmd.c"

'Finished building: ../wlan_cmd.c'

' '

'Building target: network_terminal_CC3220S_LAUNCHXL_tirtos_ccs.out'

'Invoking: ARM Linker'

"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=vfplib -me -O2 --define=CC32XX -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on -z -m"network_terminal_CC3220S_LAUNCHXL_tirtos_ccs.map" -i"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/lib" -i"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/include" --reread_libs --diag_wrap=off --display_error_number --warn_sections --xml_link_info="network_terminal_CC3220S_LAUNCHXL_tirtos_ccs_linkInfo.xml" --rom_model -o "network_terminal_CC3220S_LAUNCHXL_tirtos_ccs.out" "./CC3220S_LAUNCHXL.obj" "./cmd_parser.obj" "./main_tirtos.obj" "./netapp_cmd.obj" "./network_terminal.obj" "./radio_tool.obj" "./socket_cmd.obj" "./str.obj" "./transceiver_cmd.obj" "./uart_term.obj" "./wlan_cmd.obj" "../CC3220S_LAUNCHXL_TIRTOS.cmd" -l"C:/Users/vvelasco/Documents/CC3220/CC3220 workspace/tirtos_builds_CC3220S_LAUNCHXL_release_ccs/Release/configPkg/linker.cmd" -l"C:/ti/simplelink_cc32xx_sdk_1_50_00_06/source/ti/display/lib/display.aem4" -l"C:/ti/simplelink_cc32xx_sdk_1_50_00_06/source/ti/drivers/lib/drivers_cc32xx.aem4" -l"C:/ti/simplelink_cc32xx_sdk_1_50_00_06/source/third_party/fatfs/lib/fatfs.aem4" -l"C:/ti/simplelink_cc32xx_sdk_1_50_00_06/source/ti/drivers/net/wifi/ccs/rtos/simplelink.a" -l"C:/ti/simplelink_cc32xx_sdk_1_50_00_06/kernel/tirtos/packages/ti/dpl/lib/dpl_cc32xx.aem4" -l"C:/ti/simplelink_cc32xx_sdk_1_50_00_06/source/ti/devices/cc32xx/driverlib/ccs/Release/driverlib.a" -llibc.a

<Linking>

'Finished building target: network_terminal_CC3220S_LAUNCHXL_tirtos_ccs.out'

' '

C:/ti/ccsv7/utils/tiobj2bin/tiobj2bin network_terminal_CC3220S_LAUNCHXL_tirtos_ccs.out network_terminal_CC3220S_LAUNCHXL_tirtos_ccs.bin C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armofd C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armhex C:/ti/ccsv7/utils/tiobj2bin/mkhex4bin

C:/ti/ccsv7/utils/tiobj2bin/mkhex4bin failure occurred. Giving up.

' '

**** Build Finished ****



I think this is happening because I'm using CCS 7.0 instead of 7.4.  (Our IT dept hasn't been able to upgrade my system yet.)

Dean,

The only way I can generate a "mkhex4bin failure occurred. Giving up" message is if I break up the command into multiple lines. Could you confirm that your post-build command is in a single line?

Also does the command fail in a similar fashion with other projects as well? I believe most, if not all of the example projects in the Simplelink CC3220 SDK have this command as a post-build step. Could you try building a couple of example projects and let us know if they also fail with this message?

Dean Velasco88 said:

This leads me to suspect that it's an issue with CCS 7.0.

The oldest version I currently have installed is CCS 7.1 and I couldn't reproduce the error with that. I will install 7.0 and give it a try, although the other poster in this thread said they saw the issue even with CCS 7.4.

Dean,

One more quick thing to check. The mkhex4bin utility creates temporary files in the system temporary directory set by TMP environment variable. Could you double-check permissions to your TMP directory or set TMP to something simple like c:\temp with full permissions and see if that changes anything?

I can give you bit more insight in to what is happening.  But not enough to fix it.  For that, I need a test case that allows me to reproduce the problem.

tiobj2bin is a Windows batch file.  The problem happens in these lines ...

if %perlcmd% == none (
   %mkhexcmd% %xmltmp% > %hextmp%
) else (
   %perlcmd% %mkhexcmd% %xmltmp% > %hextmp%
)

if not %errorlevel% equ 0 (
   echo %mkhexcmd% failure occurred.  Giving up.
   exit /b
)

You don't have perlcmd, so line 2 executes.  This invokes mkhex4bin.  When it runs successfully, it returns 0 to Windows.  Line 7 checks on that return code.  If it isn't 0, then the failure message is issued, and the batch file quits.  I don't understand how mkhex4bin can exit with a code other than 0, and yet not issue any diagnostics of its own.  That is what I need to reproduce.

Please zip up the .out file, and attach that to your next post.  

Thanks and regards,

-George

Okay, and thanks. Here is a sample .out file that doesn't get converted.

Could this be a permissions issue?  I ask because I can generate the .bin files on my home computer, but not on my workplace computer.

portable_CC3220S_LAUNCHXL_tirtos_ccs.zip

Dean Velasco88 said:

Here is a sample .out file that doesn't get converted.

Works for me.  Unfortunately.

Dean Velasco88 said:

Could this be a permissions issue?  I ask because I can generate the .bin files on my home computer, but not on my workplace computer.

It seems likely that whatever is wrong is specific to your system.  Make sure of the following ...

• The TMP environment variable is set to a suitable temporary directory.  A typical setting is: C:\Users\name\AppData\Local\Temp .  Change "name" to the login name on your system.
• The TMP directory has write permissions
• The TMP directory has plenty of space

If that all seems fine, then try running the key commands directly from the command line.  The following commands run OFD to create an XML file, then run mkhex4bin over that XML file to create a small text file.  The last command shows the return code from mkhex4bin.  You'll have to tweak these commands to your system.

% C:\ti\ccsv7\tools\compiler\ti-cgt-arm_16.9.0.LTS\bin\armofd -x --xml_indent=0 --obj_display=none,sections,header,segments network_terminal_CC3220S_LAUNCHXL_tirtos_ccs.out > C:\Users\name\AppData\Local\Temp\t1.xml
% C:\ti\ccsv7\utils\tiobj2bin\mkhex4bin C:\Users\name\AppData\Local\Temp\t1.xml > C:\Users\name\AppData\Local\Temp\t2.tmp
% echo expect exit code 0, get %errorlevel%

I'm not sure what you will see.  But it will probably help you figure out what happened.

Thanks and regards,

-George

Thanks for the input.  The TMP directory checks out as far as I can tell, so I tried the commands you listed.  I got the following result:

    "expect error code 0, get -1"

I'm sorry, but I am quite lost on this one.  I have never seen this happen, and I don't understand what is causing it.

Here is a bit of background on tiobj2bin, which may be helpful.  It is one of many utilities in the cg_xml package.  The two files needed for tiobj2bin are added to CCS as a convenience to users.  Otherwise, they would have to install the package just to get one utility.  The two files are tiobj2bin.bat and mkhex4bin.exe.  The first is a Windows batch file, and the second is a Windows executable.  mkhex4bin.exe starts out as a Perl script named mkhex4bin.pl, which is also in the package.  Very long story short, creating standalone executables from Perl scripts is not straightforward, like it is for C.  The cg_xml package includes a file named getting_started.txt which has some basic information about the executables.  I'll reproduce it here.

------------------------------------------------------------------------------
4. Standalone Executables Use the System Temporary Directory
------------------------------------------------------------------------------
A standalone Perl executable version of a script, such as sectti.exe, uses
several files in a directory under the system temporary directory. On
Windows systems the temporary directory is typically:

    C:\Users\<username>\AppData\Local\Temp

On Unix systems the temporary directory is typically /tmp.

The first time an executable runs it installs those files and then uses
them to execute. On subsequent runs the installation step is not required,
and thus the executable starts up much faster.

Please insure the system temporary directory has permissions that allow
any user to add directories. On Unix systems, this typically requires
that /tmp have all permissions set.

------------------------------------------------------------------------------
5. Control How Standalone Executables use Temporary Directories and Files
------------------------------------------------------------------------------
To explicitly set the temporary directory where the standalone executables
store temporary files, add the environment variable setting:

PAR_GLOBAL_TMPDIR=<your directory path here>

If you want the files in the temporary directory to be deleted each time a
standalone executable completes execution, add the environment variable
setting:

PAR_GLOBAL_CLEAN=1

Note such deletion of the temporary files will slow the startup of the
standalone executables.

So, with that as background, here is another suggestion.  Completely empty the temporary directory, and try again.  Maybe something is messed up in there, and it all needs to be created fresh.

If this general background gives you any other ideas, by all means, try them out.

Thanks and regards,

-George

We tried emptying the temporary files folder, but to no avail.  Should we try adjusting the permissions on any other folders?

Please try to see the help summary for the mkhex4bin command.  It should look like this ...

C:\work\dir>C:\ti\ccsv7\utils\tiobj2bin\mkhex4bin -h
Usage: mkhex4bin.exe [options] <xml file>   ... OR ...
       ofdXX -x <input file> | perl mkhex4bin.exe [options]

Is that what you see?

Thanks and regards,

-George

I have two more suggestions for you to try.

One ... To be sure you have the same mkhex4bin.exe that I have, compute the SHA-256 checksum and compare it to the one in the following screen shot.  Here is how I did it. My system has the 7-Zip archiver installed.  Use File Explorer to browse to a directory similar to C:\ti\ccsv7\utils\tiobj2bin .  Right click on mkhex4bin.exe and choose CRC SHA | SHA-256 .  

Two ... Get a fresh install of the cg_xml package and replace both of the files in the tiobj2bin directory.  See this forum thread for the details.

If neither of these suggestions work ... Then I have no choice but to conclude there is some problem specific to your system.  Unfortunately, I lack the expertise to help you find it.

Thanks and regards,

-George

I used https://md5file.com/calculator to generate the SHA-256 hash and got the following result:

I also tried replacing the entire folder, but the result remains the same.  At this point, this is clearly a problem that's unique to the way our computers have been set up.