To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.roboticsOpen lugnet.robotics in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / 8295
8294  |  8296
Subject: 
idea for firmware development
Newsgroups: 
lugnet.robotics
Date: 
Wed, 17 Nov 1999 23:44:18 GMT
Original-From: 
Brian Connors <connorbd@yahooSAYNOTOSPAM.com>
Viewed: 
586 times
  
As long as we're talking freeware spirit.ocx
replacement, how about this: freeware reimplementation
of the Lego firmware itself. Not so much like LegOS,
more the idea of creating a bytecode-compatible open
source firmware package that is extensible in ways
that Lego might take a year or more to get to.

Basically, my thinking is this: first, Lego is
creating a toy, and toys don't have the upgrade
turnaround time that "real software" often does.
Second, the RCX firmware is not (and most likely won't
be anytime in the near future) Open Source. This is
not necessarily a bad thing per se, but it's still
problematic for the hacker community, which is why we
have LegOS in the first place.

Someone mentioned the idea of Linux for the RCX. This
is hideously impractical (as someone else pointed out,
even ELKS won't fit), but there's an interesting idea
underlying that. Linux is where it is because it's a
clone of Unix, duplicating and extending its
traditional functionality while running many of the
same applications and utilities. This is what I'm
suggesting here. The essence of the idea is bytecode
and comm protocol compatibility; in other words, if a
program is sent via spirit.ocx (or NQC or even, one
can only hope, spectre) it won't know whether it's
dealing with the lego stuff or the new stuff UNLESS it
uses extensions.

(Brian walks down the hall to the infomercial stage
where the "audience" sits like trained seals, clapping
madly in that Stepford Spectator way they often have)

Now what do you have in mind featurewise, Brian you
non-RCX-owning poseur, I hear you asking. Well, that's
a very good question. I think the big one is probably
VLL. Some of Scout's hinted-at multiprocessing
features might be a good idea too. And of course, the
idea of being able to use RCXcode or NQC without
Lego's bugs might work too.

So? Anyone interested? (I'd do it myself, but
Seance/Spectre is tricky enough in and of itself...)

/Brian

=====
--



Message has 2 Replies:
  RE: idea for firmware development
 
(...) Hmmm, kind of like pbForth... Cheers, Ralph Hempel - P.Eng ---...--- Check out pbFORTH for LEGO Mindstorms at: (URL) ---...--- Reply to: rhempel at bmts dot com ---...--- (25 years ago, 18-Nov-99, to lugnet.robotics)
  Re: idea for firmware development
 
a question whih ocurred to me when I was reading this, is what is the size of the permanent storage we have in Kb? Tony (25 years ago, 19-Nov-99, to lugnet.robotics)

4 Messages in This Thread:


Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    
Active threads in Robotics

 
Verified and Trusted Team of Hackers
8 hours ago
Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR