Redirecting CrossLoad output

Follow

A.J. van de Ven

• October 04, 2013 01:51

We recently started experimenting with CrossLoad on a development machine to see whether purchasing CrossLoad for Production would be useful in the future.

To assist with testing, we're trying to redirect the output from the CrossLoad to a text file. We've tried using the DOS 'pipe' command (e.g., crossload [options] > output.txt) but the output appears in the console and not the text file.

Has anyone had luck redirecting the output to something other than the console?

0

• 

  Jon Elliott

  • October 04, 2013 16:06

  I've just tried it here and it is working as I would expect.

  If you're trying to redirect the crossload help screen then the problem is that it is being output on stderr rather than stdout. To redirect stderr you use 2> rather than >

  Regards,

  Jon

  0

  Comment actions Permalink
• 

  A.J. van de Ven

  • October 04, 2013 22:59

  Perhaps I'm doing something wrong. This is the command I'm trying to run:

  "C:\Program Files\Rowley Associates Limited\CrossWorks for ARM 2.2\bin\crossload" -target usb -solution "C:\MySolution.hzp" -project MyProject -config "THUMB Flash Release" -loadaddress 0 "C:\MyBinary.bin" > C:\out.txt

  The output appears in the console window, but when the programming process completes, I open the newly created out.txt and it's blank.

  I see the same when I try just running crossload.exe with no parameters, regardless of whether I use one or two > symbols.

  Other console applications, such as running chkdsk /? > out.txt, behaves as I'd expect, redirecting the entire output to the text file and not displaying anything in the console.

  0

  Comment actions Permalink
• 

  Jon Elliott

  • October 07, 2013 07:44

  > I see the same when I try just running crossload.exe with no parameters, regardless of whether I use one or two > symbols.
  No, to redirect stderr, you do:

  crossload 2> err.txt

  '>>' appends stdout to a file.

  See here for more information on redirecting output in Windows.

  0

  Comment actions Permalink
• 

  A.J. van de Ven

  • October 09, 2013 23:51

  That was it. I misunderstood your comment regarding 2> and thought you meant "two >" instead of "2>".

  I appreciate your assistance!

  0

  Comment actions Permalink

Please sign in to leave a comment.