• State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 21 subscribers
  • Views 631 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

BL51 @a.b >c.d

erik malund

Thanks to Andy Neil, I got my commandfile to run and everything is cool except that I do not get the "console file" c.d in the above example. Until I switched to the @ format, I got the file and printed it conditionally on an errorlevel test which is a nice way of doing things as far as I'm concerned (no messages, it's cool - messages, check it).
Does anyone have any idea as to the above problem?

Happy memorial day

Erik

Parents
  • 0

    My guess is that using the @commandfile prevents BL51 from writing anything to the console;
    This would make sense in the case where BL51 is invoked automatically by something like uVision, where there is no console window to receive any output!

    Therefore, if you want the messages, you'll have to specify a PRINT control to put them in a file?

    You could still test the ERRORLEVEL, and then do something like this to display the messages if it indicates problems:

    BL51 @commandfile
IF NOT ERRORLEVEL 1 GOTO :success
find "*** WARNING" listfile
:success

    BTW: I find the Keil pagination of listing files rather clumsy (a throwback to the old 66-line lineprinter days); therefore I always specify PAGELENGTH(65535) - which is as close as you can get to disabling the pagination.

    BTW2: uVision2 has a bug which limtits you to only 32760 for the maximum pagelength, and early versions forgot to add the PAGELENGTH control to the linker command line!

Reply
  • 0

    My guess is that using the @commandfile prevents BL51 from writing anything to the console;
    This would make sense in the case where BL51 is invoked automatically by something like uVision, where there is no console window to receive any output!

    Therefore, if you want the messages, you'll have to specify a PRINT control to put them in a file?

    You could still test the ERRORLEVEL, and then do something like this to display the messages if it indicates problems:

    BL51 @commandfile
IF NOT ERRORLEVEL 1 GOTO :success
find "*** WARNING" listfile
:success

    BTW: I find the Keil pagination of listing files rather clumsy (a throwback to the old 66-line lineprinter days); therefore I always specify PAGELENGTH(65535) - which is as close as you can get to disabling the pagination.

    BTW2: uVision2 has a bug which limtits you to only 32760 for the maximum pagelength, and early versions forgot to add the PAGELENGTH control to the linker command line!

Children
No data