Re: ELKS 0.0.81 available from ftp.ecs.soton.ac.uk
On 13-Nov-99 David Murn wrote: On Sat, 13 Nov 1999, Stefan Pettersson wrote: So we are back to the usual problem, where in the 640 kB should we put or own EPROM. Sorry, my fingers wasn't syncronized with my brain. What I meant was: So we are back to the usual problem, where in the 640kB..1024kB range should we put or own EPROM. -- 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
RE: KISS networking for elks
On 11-Nov-99 Vali Dragnuta wrote: What is this all about: We're clear that a full TCP implementation would be expensive. Because IP is quite stuffy (quite many options to care about), and TCP is even more complex for a 8086 toy.TCP is good for long distance conections over the internet,but our elks will not need such long distance connections ever. No, IP is more ingenious than you think. You can scale it both up and down. If you skip all fancy IP options, it's very simple and doesn't take much memory at all. IP/ICMP/UDP can be done in 1-2 kb (I have done it before). Even TCP can be much simplified, eg you can set window size to 1, and thereby disabling all window handling. So why do not we set up our OWN PROTOCOL to use it to connect to our server ? Thiss protocol (let's name it KISS TCP) would do for local network connections. Once upon a time, I had the same idea (for a different project), but when I studied my own protocol and IP, I realized that all I wanted was already there in IP. The simplest way to do that is having such a simple multichannel protocol running over a serial line to a bigger machine (a real Linux) with a multiport board ((with a port for each node)) For a serial network connection, the most easy way is SLIP. SLIP can even be multipoint, so you can use it as a real LAN. -- 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
Re: ELKS 0.0.81 available from ftp.ecs.soton.ac.uk
On 12-Nov-99 Sam Steele wrote: My PCjr has a BASIC ROM (a slightly modified version that shows off the "advanced grahpics/sound" of the PCjr when you hit escape as soon as it starts), and when booted without a harddrive, my AMIBIOS based K5 says "NO ROM BASIC", so I don't know if the BASIC call has been replaced with the BIOS setup This is unverified, but I think the Basic-hook is still there, untouched. But some of the EPROM area reserved for Basic has been used for the setup subprograms. So we are back to the usual problem, where in the 640 kB should we put or own EPROM. -- 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
RE: Embedded and Real-time systems
On 07-Oct-99 Alistair Riddoch wrote: I would therefore like some pointers to texts that would give me an answer to the following questions: I can tell what we use in our own propietary OS. What sort of features are required for this type of system? It seems to me that a filesystem is not all that important with no storage. We use a FLASH based file system to store data bases in. Are device drivers Oh yes, for all kind of devices. From 2x40 LCDs to high pressure pumps. interrupt handling Very important and memory management the types of features required? No What sort of real-time features to such operating systems generally have? Some processses/threads are to be run at exact intervals. The rest are to be run when the system feels for it (in ordinary Unix way). What type of API is the application code going to use? Is the UNIX system API any use at all? No opinion Are embedded applications run as stand-alone binaries, or do they get linked into the kernel and run as kernel threads? Both Can anyone tell me where I can get hold of a cheap SBC with an x86 CPU, EPROM, RAM and a serial interface at least on? No, but with a Z80 :-) In addition: EPROM XIP is important. There is no point in copying EPROM data to RAM just to execute it. This is what counts in my world. -- 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
Re: ELKS Networking: TCP/IP?
On 19-Apr-99 Tobias Ekbom wrote: --Murn wrote: On Sun, 18 Apr 1999, Tobias wrote: What I wanted was a discussion about TCP/IP in computers with very limited memory. --Tobias Ekbom I have written a SLIP/IP/ICMP/UDP-stack that fits in 2000 bytes program and 36 bytes RAM (not KILObytes) including operating system and device drivers, that fits in a PIC 16F84. So it isn't a problem to implement networking in limited memory. -- 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
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
OT: Assemblers
I have a large program written in MS-DOS-assembler, which I want to assemble in big-linux. Which assembler has most similar mnemonics? Sorry, the question is a bit off-topic. -- 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
