• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 55 subscribers
  • Views 1099 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Hex File Format Code Composer Version 4.10.37

Dan Zimmermann
Prodigy 10 points

I have a .hex file that was apparently built with Code Composer version 4.10.37 under Windows XP. The .hex file is in the build folder of the project and the Build Instructions say to use version 4.10.37.  I don't have access to a development system or I could verify if the .hex was indeed generated from the source in question.  I am investigating the feasibility of using the .hex file to load Flash via Asset ScanWorks.  I inspected the format of the hex file and it isn' in Intel Hex format, which is required by ScanWorks.  I found an article on the Internet that says Code Composer use Intel mcs-86 hex format but the .hex that I have isn't in that format.  Does anyone know what specific hex format Code Composer 4.10.37 generates?

  • 0
    TI__Guru**** 465171 points

    Which compiler was used and what version?

  • 0 in reply to Ki
    Prodigy 10 points

    I don't have a good understanding of the legacy tools used for the project in question.  I found a document that says they used Xilinx ISE
    version 5.2.03i to build the hex file.  I posted here because I thought Code Composer 4.10.37 included a compiler.  Perhaps I should instead pose my question to Xilinx?  Or would you happen to know what the format is for a hex file that ISE 5.2 generates?

  • 0 in reply to Dan Zimmermann
    Guru 92251 points
    Dan Zimmermann said:
    I don't have a good understanding of the legacy tools used for the project in question.

    Which device is the hex file for?

    That may help to narrow down which legacy tools were used for the project.

  • 0 in reply to Chester Gillon
    Prodigy 10 points

    I looked into this more and found that the hex file is loaded into Flash, which is then transferred to a Xilinx XC2V6000-4 (Virtex II) FPGA on a power cycle.  I have programmed Flash/FPGAs but have not used Code Composer and don't understand what it does.  I initially posted to this thread because I thought Code Composer included a VHDL compiler, but I have since learned that ISE iMPACT was used to build the VHDL into a hex file.  iMPACT can create an mcs file, which is in Intel Hex format, and that will work with ScanWorks.  However I don't understand what role Code Composer plays when programming the Flash/FPGA or if I can bypass it when programming with ScanWorks.

  • 0 in reply to Dan Zimmermann
    TI__Guru**** 249860 points

    I understand very little of your last post.  But I think it would help if I explained how hex files fit within a typical build for execution on a system that has a TI CPU embedded in it.

    A customer often starts with an example from a software development kit (SDK).  Then they customize it to their system.  Then the C/C++ code is compiled, and linked together with several libraries, to finally form a binary executable file.  CCS (you call it Code Composer) can load this file on to the system, and control execution of it.  In many such cases, hex files are never used.

    However, there is sometimes a need to use yet other tools that are not part of the TI compiler toolchain, downstream from building the binary executable file, to program flash on the production line, or something similar.  These other tools cannot read a binary executable file created by a TI compiler toolchain.  But they can read a hex file.  Thus, the TI toolchain includes a hex utility.  The hex utility can read in a binary executable file and output it in one of about 8 different hex file formats.  One of those formats is named Intel MCS-86.  

    You don't say which TI device you use.  Just for now, presume it has an Arm CPU on it.  To learn the details of the hex file formats supported, please search the TI ARM assembly tools manual for the sub-chapter titled Description of the Object Formats.  

    Thanks and regards,

    -George