Re: How do you do this?
- From: "rdragomir" <raimond.dragomir@xxxxxxxxxxxx>
- Date: 23 Jun 2006 23:47:57 -0700
Mr. Jeff Fox has a clear advantage here. The CPUs in the SEAforth chip
transmit and receive data (code here) instruction by instruction (or
even more: words of 4 instructions at one time). They instantly wake up
when data is ready, and go to sleep when there is no data. Very simple.
There is no need to make strings, encapsulate them, transmit, receive
an ack, etc. And because the opcodes are forth, there is no
optimisation issue (or I think it doesn't worth it). And here is a
matter of nanoseconds.
I wish I have had a system with more than one processor with this type
of sending code to be executed. 20 microseconds and I could be proud of
it. But every time I have two micros linked with some type of serial
connection, I quikly invented some sort of simple and very limited
protocol to send some data and commands. Very rudimentary. A couple of
miliseconds at best.
I realy wish to have a sea chip to make some embedded application I
have to, even if the sea would be too much for that. It'll be fun!
.
- Follow-Ups:
- Re: How do you do this?
- From: Jeff Fox
- Re: How do you do this?
- From: Alex McDonald
- Re: How do you do this?
- References:
- How do you do this?
- From: Jeff Fox
- How do you do this?
- Prev by Date: Re: Is Forth suitable for heavy scientific computation?
- Next by Date: Re: What's your favourite forth implementation and why?
- Previous by thread: Re: How do you do this?
- Next by thread: Re: How do you do this?
- Index(es):