Subject:
|
Re: Improving the firmware?
|
Newsgroups:
|
lugnet.robotics.nxt
|
Date:
|
Sat, 27 Jan 2007 19:38:51 GMT
|
Viewed:
|
13511 times
|
| |
|
|
In lugnet.robotics.nxt, <dickswan@sbcglobal.net> wrote:
> The challenge is how new opcodes/functions added to the firmware can be
> integrated in the NXT-G compiler so that a user written block can call
> these opcodes. Ideally there would be some kind of "backdoor" in the
> NXT-G compiler that would allow one to emit an arbitrary opcode and
> parameters; however, I did a quick glance through the NXT "build a
> block" toolkit and didn't find an obvious capability to do this.
Dick,
I was thinking more in the direction of adding a new Module, with a IOMap that
has room to set a command and several parameters, and use the ReadIOMap and
WriteIOMap to set them. This may not be the fastest solution, since as you (I
think) mentioned somewhere the current firmware Read/Write IOMap routines are
wasteful (but maybe they can also be speed up by using hash tables or just
removing the wildcard string checking) but can be exended to support many new
opcodes in a natural way. One can even use the existing opcodes interperter to
parse and execute the IOMap written command, enabling integration of
opcode-level code into NXT-G, as well as extending the opcode selection.
Guy Ziv
|
|
Message is in Reply To:
 | | RE: Improving the firmware?
|
| David Wallace wrote on Tuesday, January 23, 2007 7:34 PM: (...) This is an opportunity for the open source community to improve the firmware. Enhanced firmware does not need to have any dependency on the LEGO or NI development teams. The challenge (...) (18 years ago, 24-Jan-07, to lugnet.robotics.nxt)
|
14 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
Active threads in NXT programmable brick
|
|
|
|
|
|
