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.

S19 file : Data Record containing an address in an unused sector (TMS320F28335)

Other Parts Discussed in Thread: TMS320F28335, SYSBIOS

I have 2 projects for a TMS320F28335

  1. Boot code which resides Sector A
  2. App code which resides in Sectors B - H. This app uses SysBios.

The linker command file is setup such that the app code is not using Sector A. I verified that Sector A is unused using the map file. However, when I look at the S19 file for the App code, there is a data record containing an address for Sector A.

Here are the final 3 lines of my .s19 file for reference:

S20866FFF89493000370         <-- 66FFF8 byte address =  337FFC word address
S20867FEFCD8BFAF97B9      <-- 67FEFC byte address =  33FF7E word address   *THIS IS SECTOR A*
S70500071100E2                     <-- Termination record

Why is there an entry with a Sector A address if Sector A is unused?

  • I don't know what is going on.  Please create a zip file that contains the App .out and .map files.  Attach that to your next post.  What version of the hex utility hex2000 is used?  Please show exactly how hex2000 is invoked.

    Thanks and regards,

    -George

  • I don't think I can provide can provide you with the .out file unless there was a NDA in place.

    I am not sure how to determine the version of Hex2000. I am using Code Composer 6.1.2.

    Here is the info on hex2000.

    "${CG_TOOL_ROOT}/bin/hex2000.exe" -m -memwidth=16 -romwidth=16 -order=LS -exclude=".trace"  -exclude=".args" -exclude="passwords" -exclude="csm_rsvd" -map="${BuildDirectory}/${ProjName}.mxp" "${BuildDirectory}/${ProjName}.out" & "${ProjDirPath}/Common/Targets/TI28x/OutToS19Converter/s19conv28xx.exe" "${BuildDirectory}/${ProjName}.m00" "${BuildDirectory}/${ProjName}.s19" 262016 6815484

  • I see you are using a utility named s19conv28xx.exe.  That does not come from the TI compiler team, and I am not familiar with it.  I searched a bit, and I cannot determine where it comes from.  Is it from TI?  It seems your problem appears in the output of this utility, so that is where you should look next.  I'm sorry I cannot direct you to a better forum.

    Thanks and regards,

    -George

  • The macro CG_TOOL_ROOT will be a path containing the compiler version number. If you look in the build console, this will have been expanded.