Hi.
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.

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

One can use "A-Z" or something as "commands". That also
makes it easier to debug using a line listener.

Just my $0.02...

Jan-Erik.

--
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