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

Hex55 utility v4.3.6 -b option

Vikram Ragukumar
Prodigy 120 points


Hello,

I am trying to generate a binary file with boot table information using Hex55 v4.3.6. This file will be used for Flash boot of a C5510 on a custom module. The memory width of the Flash being used on the module is 16 bits.

This is the command line I am using

hex55 -boot -v5510:2 -parallel16 -memwidth=16 -romwidth=16 -delay=10000 -e=_c_int00 -o=tmsc55xx.rom -b tmsc55xx.out

Upon entering the above command line, I get the following error message

"fatal error: Binary format must have a memory width of 8 bits (aborting)".

What options am I missing in order to generate a binary file with boot table for a memory width of 16 ?

Thanks and Regards,

Vikram.

  • 0
    TI__Guru**** 251230 points

    The -b option requires that --romwidth=8.  Other values for --romwidth are not supported.

    Thanks and regards,

    -George 

  • 0 in reply to George Mock
    Prodigy 120 points

    George,

    Thanks for your reply.

    I found an earlier version of the hex55 utility v3.2.2, and used the same command line as before, i.e. with romwidth 16 and -b. The utility did output a valid binary file with a boot table. Is there a fundamental reason why romwidth 16 is not supported in the newer version of the utility ?

    Thanks and Regards,

    Vikram.

  • 0 in reply to Vikram Ragukumar
    TI__Expert 4280 points

    First, I believe Georgm misspoke in his response.  The restriction is that memwidth (not romwidth) must be 8 for binary format. And that was the intention for 3.2.2, but the hex55 utility did not enforce the restriction.

    Having just tried a few experiments it is not clear that the 4.3.6 hex55 always enforces the restriction or perhaps I misunderstand the restriction.  I believe there is no fundamental reason that 16 cannot be supported.  Given that binary format is just a stream of bytes (with no metadata) representing the raw contents of a ROM I'm not sure how using memwidth 16 would change anything.  (Maybe there is some worry  about endianness or what to do with an odd number of bytes.)  My guess is that the memwidth 8 restriction was meant to reflect the fact that the resulting file is a simple byte stream.  I doubt that the memwidth setting has any affect and restricting to 8 was a way of making that clear.

    In any case, if the command you cite worked for you with 3.2.2 I believe you can get the same result with 4.3.6 if you drop the "-parallel16" option.  Without that option hex55 seems to proceed without emitting the error message and for the files I tried it produces the same output as 3.2.2.

     

  • 0 in reply to Paul Knueven
    Genius 3420 points

    Paul-

    Thanks for your fast reply.   If v4.3.6 without "-parallel16" option produces the same result as v3.2.2 then we're good.

    My only suggestion would be that TI tools guys change the v4.x error message to include a suggestion for alternative command-line options.

    -Jeff