| |
In lugnet.robotics.nxt.nxthacking, Jeremy Rand wrote:
> the NXT-G memory pool to hold data for the new VM, but I'm running into
There is no such thing as an NXT-G memory pool. The standard NXT firmware has
nothing to do with the graphical programming language implemented by LEGO and NI
which is called NXT-G.
> problems. Apparently, doing a memset to set all of the pool to 0x00 causes the
> firmware to crash.
Why are you setting it to 0x00 if other parts of the firmware want it to be
filled with deadbeef? Are you certain that you aren't overwriting memory in
your memset call? Can you post your replacement code?
> Nor have I messed with any of the NXT-G VM memory allocation functions,
Again, the memory allocation functions in the standard NXT firmware are
unrelated to the programming language called NXT-G that happens to target the
standard NXT firmware.
You might just as well refer to the standard RCX firmware as the RIS firmware or
the Robolab firmware (or the LASM or MindScript firmware). But none of these
would be correct. More often than not it was the NQC firmware but that would
still be the wrong name. The brickOS firmware for the RCX was never called by
the name of the programming languages that could be used to target it (C, C++,
and Pascal). Please, for the sake of clarity and to avoid misrepresentation or
confusion, call the standard NXT firmware by its actual name - the standard NXT
firmware. You can drop the word standard if you must but never call it by the
name of a programming language that is just one of several that target the
(standard) NXT firmware.
John Hansen
|
|
Message has 1 Reply:
 | | Re: Messing with memory pool
|
| (...) Okay, thanks for the tip. It was a bit unnecessary for you to spend two paragraphs on that, though; a sentence or two would have sufficed. :-) (...) Code is as follows: if (!mem) mem= (char*)(VarsCmd.Pool); memset(mem, 0, POOL_MAX_SIZE); I'm (...) (17 years ago, 17-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
Message is in Reply To:
| | Messing with memory pool
|
| I'm working on a custom firmware with a new VM. I'm currently trying to reuse the NXT-G memory pool to hold data for the new VM, but I'm running into problems. Apparently, doing a memset to set all of the pool to 0x00 causes the firmware to crash. (...) (17 years ago, 16-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
4 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
