On Tue, Sep 11, 2001 at 09:49:32AM +0200, K=FCbek Tony wrote:
> Hi,
> Byron A Jeff wrote:
>=20
> >Personally I'd like to see straight assembly. ASM can be integrated in=
to
> >higher level languages, can run standalone, and doesn't lock users int=
o a
> >particular environment. For example I'm planning on resurrecting my NP=
CI
> >programming language in the near future. Wouter's JAL could definitly
> benefit.
> >Then there's the Basic crowd. The only common denominator is ASM. Thin=
k
> >ASM library with whichever high level interface required...
>=20
> I second that :)

Glad you agree. I think that Dale's suggestion of writing in a high level
language and then cleaning up the assembly generated is workable.

>=20
> <snip>
> >Drivers are the way to do. Define a clear robust interface between the
> stack
> >and the driver. Then build all drivers to that spec. You will never ev=
er
> >regret it.
>=20
> That to..
>=20
> And in an previous posting he wrote:
>=20
> <snip>
> >It's starting to look like I'll have to deliver a UDP/ICMP/IP stack on=
 a
> >12C509 before anyone will believe that the cost of the stack isn't tha=
t
> >significant. Would anyone like to take a crack at defining a usable=20
> >specification for such a project?
>=20
> This is something I was plannning persuing this fall anyway,
> and I already had decided using UDP, nice to hear it wasn't a bad choic=
e.

I just don't think that a microcontroller can afford the complexity of
managing TCP. I think it's easier to build up an appropriate protocol fro=
m
a base line, instead of having to take a full fledged TCP protocol and st=
art
tearing it down.
>=20
> And since Byron asked how about an serial->udp gateway ;-)=20
> i.e only the payload is passed through the serial interface.
> The protocol used by the serial device should be (could be) completely
> arbitary. This simple 'gateway' receives an packet from an 'master' on =
the
> UDP
> it handles all the protocol issues and only delivers the payload on the
> serial
> i/f. Upon reception of data on the serial i/f it assembles an packet
> to be sent to the 'last known host' ( or default ) with the serial data=
 as
> the payload.

If you get a chance go back and take a look at the multiple discussions o=
n=20
this subject. I personally think it raises the complexity to have to deal
with multiple protocols. There should be no serial to UDP gateway, UDP ge=
ts
passed through all the way to the target.

BAJ
>=20
>=20
> I'm willing to contribute with ASM coding,

Great. Again if you get a chance go and take a look at the partial design
that I posted on how this thing can be built.

Probably between the three of us we can get a serial/SLIP/IP/UDP stack
running in short order. Then we can figure out the clean breaks so that
we can separate the physical/data link layers from the network/transport
layers.

BAJ

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.