This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: FW: Re: Why is my executabel in DOS file format?


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[You mailed me privately; I'm re-adding the list.]

On Mon, Mar 08, 2004 at 02:17:24AM -0700, Meg Abyte wrote:
> >stty -F /dev/tts/0 -onlcr
> >
> >onlcr would indeed have converted an original \015\012 into
> >\015\015\012.
> 
> HI,
>  Sorry, could you explain what you are saying a little more. One should to 
> issue that command to try fixing this you're saying?

On your unixish box (GNU/Linux in this case) issue that command as root:
# stty -F /dev/tts/0 -onlcr  (/dev/tts/0 is another name for /dev/ttyS0)

(*)

The onlcr setting, if enabled (you're disabling it here), tells the
kernel to translate \012 into \015\012, or \n into \r\n (except that the
meaning of '\n' is a little more ambiguous across host types).  So if
your srec files already contain \015\012 as emitted by the bfd routines,
they will go out as \015\015\012 on the serial port, on which your board
will barf.

Disable -onlcr and hey presto, maybe problem solved.  Let us know how it
works out!

(*) Before you do this command, maybe you want to say
# stty -F /dev/tts/0 -a
to see what the current settings are?  Maybe you'll see onlcr (without a
leading dash), which means the kernel will translate LF to CRLF on
output.

- -- 
http://voyager.abite.co.za/~berndj/ (up again for now - yay!)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQFATEWW/FmLrNfLpjMRAiaeAJ9HNRNZSVhfRnaYuQCkYsVD6Hgx7QCghK8i
bYhvQ/Ryhpk/gaSRinQc7RY=
=Hsz8
-----END PGP SIGNATURE-----


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]