 | | Re: Global Objects was Strange RCX startup issues
|
|
(...) I opt for option. Not much may be to much in some cases. And I don't want to program in c++ anyway. Regards, Michael (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Global Objects was Strange RCX startup issues
|
|
(...) [snipped] (...) I simply added ctor_size and dtor_size to the *image*, *lx* and *program* structures. This allows the program manager to calc the start and end of these segments. (...) It wasn't as hard as I had thought. I have the fix (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: BricxCC release 3.3.7.6
|
|
(...) Unfortunately I haven't documented my pbForth support very well. Perhaps the following explanation will be useful to all BricxCC users who want to try pbForth. BricxCC figures out some things based on the extension of the file open in the (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.pbforth, FTX)
|
| |
| | Re: Memory, Motors and Odd Things
|
|
(...) no. Ok, that's my first problem. (...) hmm. yep. malloc()... (...) no, using the firmdl3. (...) Yes, it's recursive. And, I'm sure your hunch is right. (...) It sounds like it's the malloc() bug. I'm using 0.2.6.09 (?) I'm not going to switch (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos, FTX)
|
| |
| | Re: BricxCC release 3.3.7.6
|
|
(...) Wow! I've just discovered Bricxcc! Thank you very much for providing such a useful tool. I'm using PbForth and I was impressed by what you've included in BricxCC. Just to share with you, here's what I did so far. I've renamed the Help file so (...) (21 years ago, 11-Dec-03, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics, FTX)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) <snip> (...) <snip> (...) <snip> I didn't have time to mention this in my earlier post, but this memory dump points out a potential problem with the way BrickOS allocates memory for programs. In the above memory dump, the 0x6B words at 0xB648 (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: NQC's future
|
|
(...) click thru to: Présentation (URL) I found the English page: (URL) my eye, Babelfish seems to think the French there says: Legnoppix is a version of Knoppix Linux, bootable via CD even in a PC that ordinarily boots Windows. Legnoppix differs (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: Memory, Motors and Odd Things
|
|
(...) Hi Steve, Are you using BrickOS 0.2.6.10? In earlier versions, it was possible for malloc() to return pointers to RAM in the range [F010,FB7F], which was shared with the motor port controller. Writing to this memory adversely affected the (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos, FTX)
|
| |
| | Re: Logging sensor data
|
|
(...) That's why I use brickOS nanobapt (21 years ago, 10-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Memory, Motors and Odd Things
|
|
I ran into something odd, and I'm wondering if someone can explain it. I have a pretty large BrickOS program, (the .lx is about 9k) and it uses around 2k for variables. (I think) I've noticed when the program is running, it's not doing anything with (...) (21 years ago, 10-Dec-03, to lugnet.robotics.rcx.legos)
|
