30 May
2002
30 May
'02
5:47 a.m.
You could use a Rabbit board: http://www.rabbitsemiconductor.com/
--tom
At 09:30 AM 5/30/02 -0500, you wrote:
On Thu, 30 May 2002, Glen Goodwin wrote:
I'm starting to have some second thoughts about how I'm going to do this.
I'm considering an external 'black box' that will connect to a PPP server
on one end and have a RS-232 connection on the other that will provide
something like a serialized verion of BSD's sockets. I'm also thinking
about implementing a raw tcp port that would connect to an extra RS-232
port [optionally password protected] that could be used to attach to the
system's console, and replicate it on the other end of the network.
Right now I'm looking at either a Z80 with 32k of ram, 16k of flash, a CTC
and one or two DUARTS, or a uC that'll provide as much of that in hardware
as possible. PICs are nice, but generally seem to have too little memory
for TX/RX buffers, and Basic stamps are too slow. (and who wants to
program in BASIC anyways?)
Any suggestions on a good uC to use?
-- Pat
From: Pat
Finnegan <pat(a)purdueriots.com>
What I'm looking to do is provide a (small)
SLIP or PPP based TCP/IP
stack
for a machine that will stay resident and can be
used by CP/M 2.2 [or
perhaps MP/M II] user programs.
Pat --
I would be extremely interested to learn of your progress in this area.
Please keep us posted, or contact me off-list. 
30 May
30 May
5:55 a.m.
That sounds nice, but there's no way I can afford (or even rationalize)
getting a $200+ development board. The on-board ethernet is a nice thing,
however. I'll see what I can get through Purdue perhaps...
-- Pat
On Thu, 30 May 2002, Tom Uban wrote:
You could use a Rabbit board:
http://www.rabbitsemiconductor.com/
--tom
At 09:30 AM 5/30/02 -0500, you wrote:
On Thu, 30 May 2002, Glen Goodwin wrote:
I'm starting to have some second thoughts about how I'm going to do this.
I'm considering an external 'black box' that will connect to a PPP server
on one end and have a RS-232 connection on the other that will provide
something like a serialized verion of BSD's sockets. I'm also thinking
about implementing a raw tcp port that would connect to an extra RS-232
port [optionally password protected] that could be used to attach to the
system's console, and replicate it on the other end of the network.
Right now I'm looking at either a Z80 with 32k of ram, 16k of flash, a CTC
and one or two DUARTS, or a uC that'll provide as much of that in hardware
as possible. PICs are nice, but generally seem to have too little memory
for TX/RX buffers, and Basic stamps are too slow. (and who wants to
program in BASIC anyways?)
Any suggestions on a good uC to use?
-- Pat
From: Pat
Finnegan <pat(a)purdueriots.com>
What I'm looking to do is provide a (small)
SLIP or PPP based TCP/IP
stack
for a machine that will stay resident and can be
used by CP/M 2.2 [or
perhaps MP/M II] user programs.
Pat --
I would be extremely interested to learn of your progress in this area.
Please keep us posted, or contact me off-list. 
6:05 a.m.
In my previous post, I deliberately left Rabbit out. I played with that
board, wanting to implement a fairly little simple TCP/IP server for my
weather station. While it claims a 1MB address space, your code executes in
two 8K sliding windows. And apparently, arraning windows or some BS like
that is left to the user.
All I know for sure is that I'm a fairly experience micro person, and I
couldn't get it to work. My object file was something like 43K with their
stack compiled in. And it was claimed to be "too large". The limited help
I got from Rabbit was an example of how to do it, which was a complete
re-write of my code, and not in a way that made sense. It's a little
difficult to explain, but in spite of Fred Eadys paid endorsement for them,
it sucks.
With all the other choices in micros out there, the Rabbit is best left in
the dumpster^wbox.
--John
-----Original Message-----
From: cctalk-admin(a)classiccmp.org [mailto:cctalk-admin@classiccmp.org]On
Behalf Of Tom Uban
Sent: Thursday, May 30, 2002 10:48
To: cctalk(a)classiccmp.org
Subject: Re: CP/M TCP/IP (was Re: CP/M coding question)
You could use a Rabbit board: http://www.rabbitsemiconductor.com/
--tom
6:23 a.m.
Interesting! I haven't used it myself, but I have thought about trying it
from time to time. It makes sense that the 1MB address
space would have to
be bank switched, but 8K windows sounds like a bit of a pain.
Too bad...
--tom
At 11:05 AM 5/30/02 -0400, you wrote:
In my previous post, I deliberately left Rabbit out.
I played with that
board, wanting to implement a fairly little simple TCP/IP server for my
weather station. While it claims a 1MB address space, your code executes in
two 8K sliding windows. And apparently, arraning windows or some BS like
that is left to the user.
All I know for sure is that I'm a fairly experience micro person, and I
couldn't get it to work. My object file was something like 43K with their
stack compiled in. And it was claimed to be "too large". The limited help
I got from Rabbit was an example of how to do it, which was a complete
re-write of my code, and not in a way that made sense. It's a little
difficult to explain, but in spite of Fred Eadys paid endorsement for them,
it sucks.
With all the other choices in micros out there, the Rabbit is best left in
the dumpster^wbox.
--John
-----Original Message-----
From: cctalk-admin(a)classiccmp.org [mailto:cctalk-admin@classiccmp.org]On
Behalf Of Tom Uban
Sent: Thursday, May 30, 2002 10:48
To: cctalk(a)classiccmp.org
Subject: Re: CP/M TCP/IP (was Re: CP/M coding question)
You could use a Rabbit board: http://www.rabbitsemiconductor.com/
--tom
8070
days inactive
8070
days old
3 comments
3 participants
participants (3)
-
jcwren＠jcwren.com -
pat＠purdueriots.com -
uban＠ubanproductions.com