• State TI Thinks Resolved
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 123 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

TMS320F28377D-EP: 0xFFFF is missing from the bin file generated by 28377D

albert qiu
Intellectual 300 points
Part Number: TMS320F28377D-EP

Tool/software:

When using CPU2 of 28377D, use the emulator to download the generated out file to flash, and when viewing memory, there is a 0xFFFF in memory, but when Vscode opens the corresponding bin file, the corresponding position is not 0xFFFF。As shown in the figure below, 4 0xFFFF are missing from the bin file

  • 0
    TI__Guru**** 245180 points
    albert qiu said:
    but when Vscode opens the corresponding bin file

    Where does this bin file come from?  Please show the text, and not a screenshot, of the command used to create it.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Intellectual 300 points

    Use CCS to enable the bin file generated by "Enable C2000 Hex Utility".The settings are as follows：--memwidth=16 --order=MS --romwidth=16 --diag_wrap=off --binary。Also, CPU1 cores don't have this problem if they use the same setup。

    Is there anything special about CPU2, or is there an official setup tutorial?

     

  • 0 in reply to albert qiu
    TI__Guru**** 245180 points

    A binary file created by ...

    albert qiu said:
    Use CCS to enable the bin file generated by "Enable C2000 Hex Utility".The settings are as follows：--memwidth=16 --order=MS --romwidth=16 --diag_wrap=off --binary。

    ... has a problem.  Any gap in memory between sections is ignored.  

    Please use the workaround described in this forum post.  Among other details, this workaround requires adding a hex utility command file to the CCS project.  For the details of how to do that, please see the last part of the article Hex utility in CCS.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Intellectual 300 points

    I have changed the way to generate bin files.

    post build, I use: "${CCE_INSTALL_ROOT}/utils/tiobj2bin/tiobj2bin" "${BuildArtifactFileName}" "${BuildArtifactFileBaseName}.bin" "${CG_TOOL_ROOT}/bin/ofd2000" "${CG_TOOL_ROOT}/bin/hex2000" "${CCE_INSTALL_ROOT}/utils/tiobj2bin/mkhex4bin"

    CPU1 and CPU2 use the same method, CPU1 has no problem with the bin file (the bin file is exactly the same as in the memory view)

    However, there is a problem with CPU2: for example, after the JATG is downloaded, the data viewed in the memory view is FFFF FFFF FFFF, but the bin file is 0000 0000 0000

  • 0 in reply to albert qiu
    TI__Guru**** 245180 points

    The workaround I referred you to does not use tiobj2bin.  Because tiobj2bin has problems.

    One, it doesn't work with C2000 EABI files.  I presume you build with EABI, so I don't know how you got it to work.  

    Two, gaps are always filled with 0.  

    If you use the workaround I suggest, it fills gaps with 0 by default.  But you can change that default by adding the option --fill=0xffff to the hex2000 command.

    Thanks and regards,

    -George