| |
In lugnet.robotics.nxt.nxthacking, John Hansen wrote:
> 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.
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. :-)
> 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?
Code is as follows:
if (!mem) mem= (char*)(VarsCmd.Pool);
memset(mem, 0, POOL_MAX_SIZE);
I'm setting it to 0x00 because that's what the custom VM expects. Do you think
it would be easier to just allocate separate storage for the custom VM's data
and set POOL_MAX_SIZE to a very low number (maybe 4 - just something that
doesn't use up much RAM) so that the remnants of the standard NXT VM don't get
annoyed?
|
|
Message has 1 Reply:
 | | Re: Messing with memory pool
|
| (...) So you have not removed the line from cCmdInitPool where VarsCmd.Pool is set equal to IOMapCmd.MemoryPool, correct? Can you say where "mem" comes from and is it for certain being initialized to zero or nil before cCmdInitPool gets called? Is (...) (17 years ago, 20-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
Message is in Reply To:
| | Re: Messing with memory pool
|
| (...) 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. (...) Why are you setting it to 0x00 if other parts of the (...) (17 years ago, 17-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
|
|
|
|
