• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 72 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.

TM4C1231E6PZ: Release mode executable files generation

manoj kumar
Prodigy 40 points
Part Number: TM4C1231E6PZ
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi TI,

I want proper configuration for hex file generation in ccs 12 version. Right now, i'm using .bin file programming through Uniflash and it works fine, but soon after powering off the controller won't run any firmware(.bin). 

From the Hex utility, generated hex file is not at all working i.e from uniflash it says program success but the MCU won't run.

Please provide the configuration required for executable file generations for release mode or production firmware flash.

Thanks & regards,

Manoj Kumar CH.

  • 0
    TI__Guru**** 191206 points

    Hi,

    manoj kumar said:
    I want proper configuration for hex file generation in ccs 12 version.

      How did you generate the hex file?

      You need to use --romwidth 32 and --memwidth 32 flags so only one hex file is merged and produced. Refer to TI Arm Assembler user's guide for details. If this does not solve your problem, I will forward your question to our toolchain experts. 

    manoj kumar said:
    Right now, i'm using .bin file programming through Uniflash and it works fine, but soon after powering off the controller won't run any firmware(.bin). 

    How did you generate the .bin file?

    If you use any of the TivaWare examples, it will generate a .out file as well as a .bin file. For example, in the CCS post-build processing steps, it has the below commands to generate a .bin file. Are you using the same commands? 

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

    When you said it does not run the firmware, do you have the same problem when you load the .out file instead? We need to isolate the problem (program won't run after a power cycle) if it is related to your .bin file generation or the firmware itself. 

  • 0 in reply to Charles Tsai
    TI__Guru**** 191206 points

    Hi,

      I have not heard back from you. I will close the thread for now. If you have any update, you can write back to this post and the status will change to OPEN.