> I took a quick look at the EeasyProg(tm) protocol.
> http://www.embedinc.com/easyprog/easyprog_prot.txt.htm
>
> I see that it uses an "opcode byte" with values (dec)
> 1 - 38 (currently). Now, some of these values, such
> as 10 (LF) and 13 (CR) may create problems on
> platforms where a standard serial port used some
> kind of "terminal driver". Depending on how the port
> is setup ("passthrough", "binary" or whatever) these
> control characters might create some problems.

I've never run into a system that couldn't handle straight binary bytes
over RS-232.  Besides, even if the opcodes avoided "control characters",
it would be a great deal of trouble to avoid them with the data bytes.
So, once you buy into using a binary protocol, you might as well make
things easy and start the opcodes at 1 or 0.

> Personaly, I don't think it wise to use the lower
> 32 ASCII chars as something else then what they once
> was defined for.

Probably wise, but this protocol isn't ASCII.

Do you know of a particular system that can't do raw binary I/O over its
serial port?


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics