• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 53 subscribers
  • Views 1046 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Issues when using hex430

Jacob Kenney
Prodigy 80 points
Other Parts Discussed in Thread: MSP430F5418A

On Code Composer Studio 6.1.3, I call the hex430 utility post build to convert my output file to hex using the following:

"${CG_TOOL_HEX}" -i "${BuildArtifactFileName}" -o "${BuildArtifactFileBaseName}.hex" -order MS -memwidth 8 -romwidth 16

However, I took this project over from someone else who was originally working on it and notice when I build the hex output, my hex file is larger and does not quite match up to theirs when I do a side-by-side comparison. Somewhere, my file is getting off by 0xB80 bytes and I believe is the root of my issue when I try to load this to my board. I am using an MSP430F5418A and have not modified the code that was given to me and cannot produce the same hex file from before. Does anyone know what may be the cause of this? The only difference in workstations I believe is he was using CCSv5 on a 32-bit machine while I am using CCSv6 on a 64-bit machine, but I'm not sure if that would cause a discrepancy in the output hex file. Any advice is greatly appreciated.

Thank you.

  • 0
    Guru 92251 points

    Jacob Kenney said:
    The only difference in workstations I believe is he was using CCSv5 on a 32-bit machine while I am using CCSv6 on a 64-bit machine

    Is the same compiler version used on both workstations?

    The use of different compiler versions on the workstations is more likely than hex430 to explain the difference in the final hex file.

  • 0 in reply to Chester Gillon
    Prodigy 80 points
    I am using the same compiler (MSP430 TI v4.0.1) to build the outputs, this was the compiler that was noted to be used.
  • 0
    TI__Guru**** 173310 points

    Are you sure the command line being used is the same in both computers? And is the .out file from which the hex file is being generated also the same on both machines?

  • 0 in reply to AartiG
    Prodigy 80 points
    I believe they are both using the same command line, how can I verify that? And they use the same compiler with the same files, I'll try to verify the .out files are the same but what other aspects would cause a difference in them?
    Thank you.
  • 0 in reply to Jacob Kenney
    TI__Guru**** 173310 points

    Jacob Kenney said:
    I believe they are both using the same command line, how can I verify that?

    If you still have access to the original project you can check it there (it should be in the .cproject file if you still have the original one archived somewhere).

    If there is a difference in the .out files, then the hex files will also be different, even if the same command line is used for the hex conversion. A difference in .out file could occur due to a difference in compiler version or a difference in compiler or linker options. 

    If the .out files are identical then I would suspect the hex commands are different. If the version of hex utility, hex command line options and .out file are all the same, I can't explain why the hex outputs would be different.

  • 0 in reply to AartiG
    Prodigy 80 points
    Thank you for the help, in the project's documentation it lists to use compiler 4.0.1, however the last build of it that we have a backup of is using 4.0.2. Once I switched to using this compiler, my hex files matched up better and everything is at least in the correct memory space.