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

How To Get UnifFlash To Ignore Non-Hex Records

Kier
Mastermind 9720 points

Other Parts Discussed in Thread: UNIFLASH

I want to embed the SVN revision into the hex file output from CCS using the SVN Revision keyword.

For example:

I was hoping that UniFlash would:

a) Ignore anything after the End-Of-File record.

or

b) Ignore any line that doesn't start with a colon.

Sadly Uniflash does neither and tries to interpret my Revision line as a record even though it can't be a record since it doesn't start with a colon:

Is there a comment delimiter that would be effective please?

If not, please log a feature request for UniFlash to ignore non-hex records.

Thank you very much.

  • 0
    TI__Guru**** 484261 points

    Hello,

    Kier said:
    Is there a comment delimiter that would be effective please?

    This is currently not supported

    Kier said:
    If not, please log a feature request for UniFlash to ignore non-hex records.

    Note that Intel Hex format does not officially have a definition for comments so this feature request would be an addition on top of the existing support for the standard Intel Hex format.

    That said:

    Kier said:
    a) Ignore anything after the End-Of-File record.

    This request seems reasonable and preferable compared to option "b". Before exploring this request, I do want to mention that other hex formats like Motorola S-Record does have a type of record format for comments and is supported by UniFlash. This comment record is often used for things like revision number, etc. Perhaps Motorola S-Record can be an alternate option for Intel Hex?

    Thanks

    ki 

  • 0 in reply to Ki
    Mastermind 9720 points

    Many thanks for the reply.

    In my case the hex file is for word-addressable C28x and as far as I have discovered, the resulting file is definitely not "standard" Intel hex format even though I use option --intel in the hex command script. Except for UniFlash, the hex file is not understandable by my non-TI hex utilities. My point is that TI seem to have already set a precedent for divergence from the "standard" format so a comment feature shouldn't be an issue.

    Perhaps adding a comment feature to one of the TI proprietary formats (ti-tagged, ti_txt) would be preferable?

    Thanks for the S-Record tip, I'll look into that.

  • 0 in reply to Ki
    Mastermind 9720 points

    I checked but the S-rec option (header record) is still encoded rather than the human readable plain text that SVN can substitute with its revision. But thanks for the suggestion anyway.

  • 0 in reply to Kier
    Mastermind 9720 points

    I found a solution to the problem. In a way UniFlash does support comments but more by accident than by design.

    On a hunch I added the SVN keyword after the record checksum at the top of the hex file. To my surprise UniFlash ignores the comment text and proceeds to Load/Verify as normal. It seems to work on any line but the top line is ideal since this catches the eye when opened by text editor. I infer that UniFlash is using the checksum as the line terminator rather than CR/LF etc.

    Problem solved.