|
 | | Re: LEGO remote controller problem
|
| (...) Then this is the first time ;) It was indeed the compiler. Using those versions you named in your message, my compiled brickOS.srec file works as well. The lr_startup and lr_shutdown calls don't make any difference, whether they are in or out. (...) (21 years ago, 29-Jul-03, to lugnet.robotics.rcx.legos)
| |
|  
brickos
(score: 1.256)
|
|
| | Re: LEGO remote controller problem
|
| "Michael Obenland" <obenland@t-online.de> wrote in message news:HIqqFv.1Iwz@lugnet.com... (...) starting (...) I think the call to lr_shutdown() in Christian's program clobbered things such that the remote may no longer be useable unless the power (...) (21 years ago, 28-Jul-03, to lugnet.robotics.rcx.legos)
| |
|
brickos
(score: 1.256)
|
|
| | Re: LEGO remote controller problem
|
| (...) Great. (...) I use h8300-hms-gcc-3.1-1.i386.rpm h8300-hms-binutils-2...1.i386.rpm but I never heard from anyone that some gcc version produces a bad brickOS system. Strange, indeed. Regards, Michael (21 years ago, 28-Jul-03, to lugnet.robotics.rcx.legos)
| |
|
brickos
(score: 1.256)
|
|
| | Re: LEGO remote controller problem
|
| Hi Michael, Thank you very much for your answer. Well, there isn't really much source, here we go: #include <conio.h> #include <unistd.h> #include <remote.h> #include <dsensor.h> int my_lr_handler(unsigned int etype, unsigned int key) { cputw(key); (...) (21 years ago, 28-Jul-03, to lugnet.robotics.rcx.legos)
| |
|
brickos
(score: 1.256)
|
|
| |
|
brickos
(score: 1.256)
|
|
| | sys_time not working
|
| Hi i install successfully brickOS-0.2.6.10 under Win2000 without any problems and ran successfully "helloworld.lx" I created one first elementary small program using the sys_time function. The problem is that it doesn't compile correctly. The (...) (21 years ago, 5-Aug-03, to lugnet.robotics.rcx.legos)
| |
|
brickos
(score: 1.256)
|
|
| |
|
brickos
(score: 1.255)
|
|
| | Re: Question about mm.C in BrickOS
|
| Thanks to both of you, I was pretty close to my understanding of it, but I did not know about the "new block creation behind the current block" but it makes sense now, if I have any other question (I am sure I will) I will def. ask. Thanks again, (...) (21 years ago, 14-Aug-03, to lugnet.robotics.rcx.legos)
| |
|
brickos
(score: 1.255)
|
|
| | Re: Question about mm.C in BrickOS
|
| Hi, (...) Ptr points to the length byte of the first free block (...) *(ptr-1) actually is MM_FREE and is now set to the callers id. (...) Now we can do two things: We could grab all memory we found in this block or we could allocate only the memory (...) (21 years ago, 13-Aug-03, to lugnet.robotics.rcx.legos)
| |
|
brickos
(score: 1.255)
|
|
| | trouble compiling brickOS
|
| Hi! I am pretty new to lego and I started for a few days to make my rcx work under Linux. After I passed all the makefile issues, gcc 3.3 mlsl problems, I still get this error from memcpy.c: make[1]: Entering directory (...) (21 years ago, 3-Sep-03, to lugnet.robotics.rcx.legos)
| |
|
brickos
(score: 1.254)
|
|
| | Re: trouble compiling brickOS
|
| (...) Hm, that should not happen. Try to start your hitachi compiler by hand, for example with "h8300-hms-gcc --version" to get an "I am alive" message from it, so you are sure it is installed as intended. If _you_ can't get it to work, configure (...) (21 years ago, 5-Sep-03, to lugnet.robotics.rcx.legos)
| |
|
brickos
(score: 1.253)
|
|
| | BrickOS = shoot self in head
|
| I think I've concluded that the makers of BrickOS are secretly scheming to take over the world by making geeks' heads explode by repeated impact with the nearest CONCRETE WALL... Okay, first question: regarding the list of packages. The Step-By-Step (...) (21 years ago, 28-Sep-03, to lugnet.robotics.rcx.legos)
| |
|
brickos
(score: 1.252)
|
|
| | Re: trouble compiling brickOS
|
| (...) I did! (...) It did complain and I did install the hitachi 8300 gcc version. Funny thing, after installing it, the configure script was still complaining that it cannot find the hitachi gcc compiler, although the binaries were right there in (...) (21 years ago, 5-Sep-03, to lugnet.robotics.rcx.legos)
| |
|
brickos
(score: 1.252)
|
|
| | Re: trouble compiling brickOS
|
| (...) Run ./configure!!! (...) Let me guess: You use the original c compiler of your linux distribution. May be that configure will complain that it does not find the gcc compiler? You run Linux on a Intel box. Your normal gcc will compile c to (...) (21 years ago, 3-Sep-03, to lugnet.robotics.rcx.legos)
| |
|
brickos
(score: 1.252)
|
|
| | Maths functions
|
| I'm having trouble finding a maths header file. It's usually called "math.h". I need to do stuff like sine and cosine, and use the "abs" function to make a number positive. Does a file like this exist? Are there any plans to incorporate a maths (...) (21 years ago, 29-Aug-03, to lugnet.robotics.rcx.legos)
| |
|
brickos
(score: 1.250)
|
|
| | Re: BrickOS = shoot self in head
|
| (...) Perhaps because the tutorial isn't update .... (...) Make sure that the gcc.exe is in your PATH .... To know it try those step : Locate the folder where gcc.exe is stock. when it's done type : "echo $PATH" in a console (without "") make sure (...) (21 years ago, 29-Sep-03, to lugnet.robotics.rcx.legos)
| |
|
brickos
(score: 1.250)
|
|
| | Re: Question about mm.C in BrickOS
|
| (...) Michael I was reading through your reply you sent me a while back and I don't understand what that line in the code does and you explaination of it. I don't understand what is meant by pointing behind the block. Any help would be great thanks. (...) (21 years ago, 14-Sep-03, to lugnet.robotics.rcx.legos)
| |
|
brickos
(score: 1.250)
|
|
| | Re: Question about mm.C in BrickOS
|
| (...) Yes it does, thank you very much Michael, you helped me out again. I just wasnt thinking of next as being a ptr like that. i just always thought it pointed to the address of the location of the memory that it can use next. thanks again... Mike (21 years ago, 15-Sep-03, to lugnet.robotics.rcx.legos)
| |
|
brickos
(score: 1.249)
|
|
| | Re: Question about mm.C in BrickOS
|
| (...) +---- +------+---...---+--...-+-------- | pid | size | data..... | pid | size | data... *-----+------+---......-+-------- ^ +---...--- ptr points to that address. This is the memory layout for the data allocation pool. Pid is the process id of (...) (21 years ago, 15-Sep-03, to lugnet.robotics.rcx.legos)
| |
|
brickos
(score: 1.249)
|
|
| |
|
brickos
(score: 1.249)
|
