• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 813 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.

.bin file and CSM PWL

Raymond Reno
Prodigy 20 points
Other Parts Discussed in Thread: TMS320F28335

Hello:

I have an embedded field upgradable application for a TMS320F28335 that I'm building with CCS 3.3.  I've been generating a binary image (.out->.hex->.bin) to download via RS232 for upgrades.  I've been successfully using this method without locking the DSP via the CSM password (8 words @ 0x33fff8).  I've been able to properly link a .out file with the initialized CSM password at locations 0x33fff8-0x33ffff.  The hex file also appears to be generated properly as well (inspecting it manually).  However, when I perform the binary translation using hex2bin.exe, any data I try to put in the 0x33fff8-0x33ffff region is discarded (and, in fact, it combines with the previous 2-word segment @ 0x33fff6 before it and discards the whole thing, not putting any of it in the final binary image):

      Saving Segment, Starting Address = 0x30f59a, Segment Length (words) = 222.

      Disgarding Segment, Starting Address = 0x33fff6, Length (words) = 10.

Can anyone provide any assistance?  Thank you!

  • 0
    TI__Guru**** 466071 points

    Hi Raymond,

    Is the only difference between the working procedure and the non-working procedure being the linking with the CSM password in the case where it fails (hex2bin.exe disregards a segment in this case)? Also please specify which exact build of CCSv3.3 you are using, which service release version you are up to and what compiler version you are using.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 20 points

    Ki:

    Thank  you for your response.  I did figure out my problem.  The hex2bin.exe I was using was customized by a former employee who was explicitly disallowing the inclusion of any segment which contained a CSM PWL memory address.  I assume this was to prevent any of our internal engineers from accidentally locking the DSP.  I've now altered the hex2bin.exe we are using to allow this situation and everything is working as-expected.

    -RRR

  • 0 in reply to Raymond Reno
    TI__Guru**** 466071 points

    Good to hear you found the cause of the issue and thanks for the update.

    ki