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

[Bernd Jendrissek <berndj at prism dot co dot za>]

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

On Tue, Mar 09, 2004 at 12:07:27PM -0700, Meg Abyte wrote:
> >Can you quote what stty gives you when you say
> ># stty -F /dev/tts/0 -a
> >please?
> 
> speed 9600 baud; rows 0; columns 0; line = 0;
> intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
> eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;
> lnext = ^V; flush = ^O; min = 1; time = 0;
> -parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts
> -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon 
                                                               ^^^^^
> -ixoff
> -iuclc -ixany -imaxbel
> opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 
  ^^^^^               ^^^^^
> ff0
> isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
> echoctl echoke

Turn those two off.  Not sure about opost, but I'd guess you might as
well kill that too.

> I tried everything that had to do with CR and LF in the stty config you 
> mentioned, and any other commands that looked somehow related.

Maybe you also want to turn off the echo parameters?

> I even did a serial loop back and that seeme to be ok, (i.e. it had ONLY 
> CR, or it had ONLY CR/LF) however, that doesn't prove what is really going 
> OUT, as coming in it might chage.

True - you really need something more low-tech to see what's *really*
going on.

> As far as using the system this is all you see on the screen:
> Mbug >>dl
> / ERROR : not in S-Record Format
> Mbug >>S3153000000071092A01E80660027308B203200301BC0
> 
> That tells me it didn't like the first line. As after dl the transfer 
> occurs. I can't tell though if it had two CR's or not.  This does work fine 
> though if the file has ONLY CR, or ONLY LF. And hardware works fine on same 
> machine if windows is use to send ONLY LF, or CR/LF.

According to your settings, you'd have this mapping:

File contents		Serial port output
\012 (LF)		\015 (should work)
\015 (CR)		\015 (should work)
\015\012 (CRLF)		\012\012 (should *not* work)

> I think only a protocol analyser of some sort. Or a program on my laptop 
> that would read the raw charaters comming in on the serial port would be 
> able to tell me what is going on.  Know of any win terminal apps that are 
> free and print the raw input? I'll have to write one when I get the time.

DOS is good at being stupid - hack up a little serial ISR that hexdumps
the receive FIFO to be really sure.

HTH, but I think I've run out of ideas now.  Good luck.

- -- 
http://voyager.abite.co.za/~berndj/ (up again for now - yay!)
[I can't guarantee the integrity of my mail; I suspect my employer of
mail tampering (adding disclaimers without my authorization).  Please
consider only signed text as my words.  Verify if you can!]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQFATrcM/FmLrNfLpjMRAqQDAJ9ri8pKmTuWtW1VB7COkgxBkQlMUwCeKN9A
Ng09XQBYA7rjn00oqQyJ1TA=
=+dVM
-----END PGP SIGNATURE-----