• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 57 subscribers
  • Views 1017 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 v4.3.6

Bill Allen
Prodigy 230 points


Hi,

I just 'upgraded' to v4.3.6 and there have been several changes that are haunting me. The command file that used to work with version 3.xx (don't know exact number) no longer works.

Specifically:

1. this option causes a warning (which results in hex55 just ignoring the whole thing) : -reg_config=0x1c00,0x2810

The warning states that this is an illegal address and an illegal argument. I tried it with and with the hex format, but both ways produce a similar warning. The '=' wasn't previously required, but apparently it is now.

2. this option also causes a warning: -delay=0x100

The warning states that the argument is out of range. I have tried (just for fun) values from 0x01 to 0x1000000, with the same result. So what is the range for this option???

I have tried the -h (help) option on both these, with rather laughable results (try it). Do you think TI might be able to provide just a wee bit more documentation on this version of such an important utility, since the documentation where hex55 is covered (SPRU280H & SPRA375F) apparently no longer applies?

Bill

  • 0
    TI__Genius 13045 points

    Bill,

    I moved your post to the Compiler Forum because they will better be able to answer your question.  They have the experts on the Code Generation Tool suite which includes the Hex utility.

    Regards.

  • 0
    TI__Expert 4280 points

    Bill,

    I was unable to reproduce any of the problems you mention with either the Linux- or Windows-hosted hex55 4.3.6.  Both -reg_config and -delay worked OK, no '=' was required, and I got no laughable results from -h.  Maybe there is some strange interaction between the options.  Can you send me the exact command line used?  What host are you using?  (My guess: Windows)  I assume you are invoking hex55 from a command line prompt.  If not, how?

    It seems like the command line processing is somehow broken.  The warnings you mention and the handling of '=' and -h are all part of the command line interpreter.

  • 0 in reply to Paul Knueven
    Prodigy 230 points

    Hi Paul,

    Yes, I am invoking in a command window under WinXP, and by laughable, I meant that the help isn't much. ie) -delay: inserts a delay. Oh really? No mention of allowable range, expected format, etc. Since the error I was getting stated that 0x100 was not in the allowable range, it would be nice to know what it expected.

    My command file as it was when it used to work under the previous version of hex55 (filename: udl.cmd):

    -boot -v5510:2 -serial8 -reg_config 0x1c00,2810 -delay 0x100 -b -o udl.bin udatalogger.out

    My command line: hex55 udl.cmd

    I placed a copy of hex55.exe in my 'Debug' directory where 'udatalogger.out' exists to save on typing and so I wouldn't have to add a seperate environment variable.

    When I run this under 4.3.6, it just ignores the entire file as though I had typed hex55 (with no arguments), and spits out the usage text. If I insert the '=' after the option switches, it doesn't ignore the command file, but I get the errors. The previous version of hex55 had no problem running this last week on the same computer, so I doubt it's an OS problem.

    Bill

  • 0 in reply to Bill Allen
    TI__Expert 4280 points

    Parsing of the -reg_config option within a command file has a bug.  I have filed defect SDSCM00035366 reporting this problem.

    It appears that everything following -reg_config on the same line of a command file is ignored (or worse).  Putting any following options on a new line will work around the problem. There also is no problem when the option appears directly on the command line.

    The errors you were getting concerning out-of-range and invalid values were caused by the use of the '=' to spearate the option and its value.  So despite what the documentation says, '=' cannot be used.  This too is a bug.  This problem also only occurs inside a command file.

     

  • 0 in reply to Paul Knueven
    TI__Guru**** 251290 points

    Feel free to query the status of  SDSCM00035366  with the SDOWP link in my sig below.

    -George

     

  • 0 in reply to George Mock
    Prodigy 230 points

    Paul,

    Thanks for resolving this.

    Bill