Re: LuaChip - The Project So Far

[Erik Hougaard <erik@...>]

Quoting David Given <dg@cowlark.com>:
> Ack! You've just pushed the complexity up by another order of magnitude! What
> you have now is nothing *like* a embedded Lua system. What you have is a 
> single-chip computer running an OS like ucLinux or ECOS that just happens to
> run a Lua interpreter as one of many user processes. It's going to be big and
> expensive and have lots of RAM and ROM.
> You could well be better off trying to strip it down as much as possible. Do
> you really *need* a threading kernel, for example? Or a TCP/IP stack? Try 
> studying PICs and embedded Z80s. You couldn't run Lua on one, but that's the

Hi David,

I have done my share of PIC's, SX's, Coldfires, Z80's....

LuaChip is another kind of project... Its not for running CAN in a car or
controlling a CNC machine... Its for jobs that would be to complex to program
in embedded-C, its for jobs where you will want to change the functionality
after deployment without taking the unit offline... A embedded device that
could perform complex operations that usually required a PC of some sort.

You must think of this device as a "Computer-replacement" - not as a
microcontroller replacement. Some microtroller jobs can be done by the LuaChip
but if you look at the device you will see that there is just a few I/O pins
and just one UART. So a "normal" configuration would be to pair the LuaChip
with a microcontroller.

/Erik


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.