Re: TCP/IP stack on ELKS
On 30-Jan-99 Phil Wise wrote: I was interested in ELKS cos we're thinking of implementing TCP/IP on a small chip. This chip (or Microcontroller) could provide a network connection to any electronic appliance which can be interfaced and can hence be controlled over a network. One basic application (which I really need) is to control my washing machine from College !! Its just an idea really, so I dont know how brilliant/awful the idea is. Does anyone know of any similar projects or previous implementations of the same thing (there goes my nobel prize). Comments and suggestions are totally welcome. I Think its a great idea, in the future everything will have an IP address (lights, light switches etc.) so this would be the first step. Would Pic's be big enough for this (1K EEprom, 36 bytes ram, 13 io pins)? Yes, it's possible, I have made an IP/SLIP/UDP/ICMP-stack in a PIC 16F84 with device drivers for a lot of devices. (Card reader, LCD, keyboard etc). It is tight, especially on RAM, but you can squeez in IP-buffers and 40 chars card reader buffer in 36 bytes if you compress all data you store! I use them for door access control systems, outdoor terminals, network interface for PIR detectors and receipt printers. It's always nice to ping your PIR detector ;-) You can check "http://www.ipsi.nu" for details. -- Stefan Pettersson Voice +46-70-5933800 Kanard AB [EMAIL PROTECTED] ([EMAIL PROTECTED]) Fax +46-221-50180 Vretberga finger [EMAIL PROTECTED] for my public key S-732 96 ARBOGA "What a scary world it must be, for those with no UID:GID" /OZ9ABN PGP signature
Re: TCP/IP stack on ELKS
[...] At my company, emWare, we take a slightly different approach to the Coke Machine and other embedded systems. Our software uses a gateway piece (which I am currently porting to plain Linux) to handle TCP/IP, security, LDAP, etc... and a much smaller, more compact protocol on the embedded side. We figure that there are tens of millions of 8 and 16 bit machines already embedded in devices, and we can "fit" in with the existing code on those devices (as small as 2k of code). This also allows millions of devices to be connected to the internet without having millions of IPs. This is the sensible way to go. Just out of interest, are you using custom IP packets, or something more esoteric? ELKS is a potential target for our gateway piece, but a ways off. It is multithreaded and ideally has dynamic loading and some other "big" features. If my boss gives me time, I will start working on it! The problem with ELKS is that it runs on 8086 machines... and newer, more powerful, less energy-intensive processors are available which are cheaper as well as easy to interface. And Linux isn't a good choice for one of them, as it's too heavyweight. --David -- +- David Given ---McQ-+ "You'll have to excuse me. There are | Work: [EMAIL PROTECTED] | five things I need to do today, all of | Play: [EMAIL PROTECTED] | them annoying." --- Susan Ivanova +- http://wired.st-and.ac.uk/~dg -+
