 | | malloc() bug found -- BAD MEMORY REGION :-(
|
|
It looks like it's not a bug in legOS, but in the RCX hardware: Memory from 0xfb80 to 0xfd7f is simply NOT WRITEABLE, or more exactly, always read as 0xff, at least on my RCX ! Try the following little test: // // memory test // #include <conio.h> (...) (25 years ago, 1-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | asm in NQC.
|
|
All, I have tried various ways to put asembly in my NQC programs. I have copied stuff from the header files but it does not work. I would like to use the slope parameter of the SetSensorMode opcode, but NCQ does not support this. That is why I need (...) (25 years ago, 1-Mar-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC troubles
|
|
Rob, You could set up a seperate task to watch the switch and turn off the moter. This task will run seperatly from the main task. John C. Quillan (...) (25 years ago, 1-Mar-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC troubles
|
|
Thanks for your help. I was also wondering if there is a way to have the motor turn off at any time in the program when the touch sensor is pushed, rather than having to re type the until statements a bunch of times. would I have to use a task for (...) (25 years ago, 1-Mar-00, to lugnet.robotics.rcx.nqc)
|
| |
| | malloc() bug haunt: getting closer..
|
|
Yesterday evening i found something, that might be the reason for some of the crashes reported lately: The chain of memory blocks used by malloc() has a broken entry, say: the reserved block at 0xfd7c has a length word of 0xfffe. This will cause (...) (25 years ago, 1-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Robolab 2.0 aliases
|
|
The Robolab 2.0 examples on the CD included with Dave Baum's book Definitive Guide to Lego Mindstorms contains the program scanbot2nqcextra.vi. In this program the generic containers are identified by name using some type of alias mechanism. These (...) (25 years ago, 1-Mar-00, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Using ROBOLAB for FIRST LEGO League
|
|
(...) According to First, the 2000 season will have the same schedule as the 1999 season. They will require registration by September 2000, they will start the challenge starting in October, and will hold tournaments in early December. (25 years ago, 1-Mar-00, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: NQC troubles
|
|
(...) Hi. The problem is that the if statement doesn't wait -- it just checks once, and if it fails, goes right past. So, if you have the switch pushed down right at the beginning, it'll work. Try this: OnFwd(OUT_A); until (SENSOR_1 ==1); (...) (25 years ago, 29-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC troubles
|
|
Hi, I am pretty new to the lego robotics thing (but I have been a lego maniac since birth), and have had a lot of fun tinkering with the mindstorms set that I got for Christmas. I have recently downloaded Nqc and RCX command center. While working on (...) (25 years ago, 29-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | J.Knudsen's 2nd NQC article online
|
|
havn't seen this mentioned yet, so here ya' go (hope nobody minds): (URL) MindStorms: Programming with NQC by Jonathan Knudsen 02/25/2000 In the second column in his series on Lego MindStorms robots, O'Reilly & Associates author Jonathan Knudsen (...) (25 years ago, 29-Feb-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Odd behavior
|
|
(...) afaik, with vanilla legOS-0.2.3, lnp_addressing_write and lnp_integrity_write are not thread-safe, there is a little patch fixing this in the lnpd tarball. (25 years ago, 29-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Never mind
|
|
Well, my so-called "working" program crashed again, after adding two sleep statements and two sound calls, neither of which my program actually got to. So, I guess there are other causes behind my hangs as well. Ah the joys. :) -- "Though I am not (...) (25 years ago, 29-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
(...) For me, at least, it's not hanging during dll. My earlier problem was that dll just wouldn't complete with my program, but it didn't crash the RCX. By the way, I think I've found my crashing problem. It looks like I had some LCD calls that (...) (25 years ago, 29-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
Luis Villa <liv@duke.edu> : (...) box (...) for (...) Wow Thanks! Here is the error I am getting-> loading cache ./config.cache checking if compiler cc1obj has been built... yes checking for gcc... h8300-hitachi-hms-gcc checking whether the C (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
I've also been struggling with building the cross compiler. I'm trying to create a DJGPP hosted version. Once I am successful, we will be able to use Markus's legOS on DOS/Windows as-is. Currently, I have to rewrite Makefile.Common, Makefile.Kernel, (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
(...) This may not be the case- the cross-compiler will try to compile something, but at least with the directions most of us use, there is no standard C library created and so the compiler thinks it doesn't work. The trick (then) is to use Markus's (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
"Markus L. Noga" <markus@noga.de> : (...) Thanks! In one of the sections under this document there is a short paragraph explaining that cross compilers may not like having 32 bit ints (Like BeOS uses) turn into 16 bit ints (Like I bet the RCX uses) (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
Jim Jackson <jjackson@jnjackson.com> : (...) GCC-2.95.2 (...) --host=i586-pc-beos (...) This gave me the Idea to tell the configure that I was running a Linux box (instead of a bebox) It almost worked too. At the end of the make the machine says I (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
(...) currently i believe there is some really subtle bug in malloc(), that shows up only under special circumstances. I experience similar problems with a fat kernel/application that disappear after adding one cputw(), making the binary a little (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
(...) Or worse, MacOS. I use and love my Macs, but lord they sure don't have much crash protection right now. I just wish there was a way to avoid having to reload the firmware every time it breaks, but I suppose that without an MMU, that's a bit (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
