 | | Re: strange motor behaviour
|
|
(...) The problem is that the upper memory area (0xf000-0xf800) is connected to both RAM and motor output. Every byte written here is also interpreted as motor command. The latest CVS version of BrickOS has fixed this (this memory is written only (...) (22 years ago, 2-Apr-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: strange motor behaviour
|
|
(...) (this should be your user programm of course) (...) and i've been a bit too quick, it should be 40*40*1 (you're allocating char's), still thats' about 1.5kByte, that is, 1/10th of the memory available to you as user, so the following reasoning (...) (22 years ago, 2-Apr-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: strange motor behaviour
|
|
(...) well, the RCX only has 32Kbyte of memory of wich half is used by brickOs the remaining half should fit you user programm and all runtime stacks and heaps, so allocating 40*40*2Bytes(the minimum for a pointer in an 32Kbyte adresspace) will need (...) (22 years ago, 2-Apr-03, to lugnet.robotics.rcx.legos)
|
| |
| | strange motor behaviour
|
|
Hello, I wonder if somebody can help me wíth the following problem. In general my program is running okay but when I change the attached data definition, the two motors I use show very strange behaviour (just making some noise and moving very slow (...) (22 years ago, 1-Apr-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Problems with BrickOS Installation
|
|
Carson, It looks like you missed the tar package.You can check to see what Cygwin packages have been installed on your system by using the cygcheck command at the cygwin command prompt. Try cygcheck -c If the output is too large for your dos window (...) (22 years ago, 1-Apr-03, to lugnet.robotics.rcx.legos)
|
