 | | Re: BrickOS Assembler
|
|
(...) One more answer... :-) Mark #include <unistd.h> #include <conio.h> int x = 10; int y = 5; int z; int main() { __asm__(" mov @_x,r0 mov @_y,r1 add r1,r0 mov r0,@_z "); lcd_int(z); msleep(5); return 0; } (21 years ago, 19-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: BrickOS Assembler
|
|
(...) In rethinking I think that compiling with the -S option will do what you want. It should create a file with a .s suffix. -S makes the compiler compile, but not assemble. Kevin "YOU ARE A GENIUS!!!!!! you can put that in your sig file!!!" Chris (...) (21 years ago, 19-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: BrickOS Assembler
|
|
(...) I recommend compiling with the -gstabs+ option (by modifying the makefile). After your .lx file is generated use "h8300-hms-objdump --disassemble-all --source > my.lst" to get a disassembled file with the C source intermixed.into the file (...) (21 years ago, 19-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: BrickOS Assembler
|
|
(...) Hi Mike, Check out the source for memcpy.c in the C library. It's not immediately clear, but the directives at the end of the __asm__ section beginning with "r" associate the %n macros with the given variables. I'm not sure of the exact syntax (...) (21 years ago, 18-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: BrickOS Assembler
|
|
(...) I need to access elements of a 2d array. I don't think this is an option for that. Nevertheless, could you post code that demonstrates this? (...) How do I do that? (...) ??? (...) Hmm... this sounds more like what I'm trying to do. Someone? (...) (21 years ago, 18-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: BrickOS Assembler
|
|
Hi, Michael. I had some trouble with getting variables into registers, as well. I can think of three ways: 1) Pass the variable to a function - the first function argument seems to be r0. You can easily experiment with this by inspecting the (...) (21 years ago, 18-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Brickos fun and games!
|
|
(...) I actually had this exact problem at the Hobby Show. I was in a hurry and didn't want to think about it (all I was doing was tweaking the light sensor thresh), so I just rebooted every time. Chris: I had lots of trouble too, but the final (...) (21 years ago, 17-Jan-04, to lugnet.robotics.rcx.legos, FTX)
|
| |
| | Re: NEWBIE question : installing BrickOS
|
|
I hate to see questions go unanswered. Steve H replied to me saying it took him 12 hours under these conditions, and now that I have done it I can say it took my P233 laptop a full 24 hours to install brickOS under Paolo's instructions. I'm also sad (...) (21 years ago, 17-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | BrickOS Assembler
|
|
Okay, I'm working on a proc in ASM, and I need help with using MOV to move stuff back and forth between memory and registers. I have the following (very simple) program working, but I can't for the life of me get the MOV to work. I've got the (...) (21 years ago, 17-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | NEWBIE question : installing BrickOS
|
|
HI, preface, I wouldn't know a cygwin from a GCC if it him me in the head. I just want to D/L a .c prg into my RCX I need advice on the process of installing BrickOS on a p233 laptop running W98se. my question is this: What is a reasonable amount (...) (21 years ago, 16-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Brickos fun and games!
|
|
(...) Looks like a nasty one, hopefully someone can offer some specific help. If you'd prefer to use a more recent gcc you can, I posted some info (URL) here>. My problem seemed to be the version of binutils I had. It may be time consuming, but with (...) (21 years ago, 16-Jan-04, to lugnet.robotics.rcx.legos, FTX)
|
| |
| | Re: BricxCC release 3.3.7.6
|
|
(...) You are welcome! I'm glad you were able to get the pre-built tools installed and working. The brickOS root that BricxCC had configured on your system was a result of having a previous installation of BricxCC where I had used that path as the (...) (21 years ago, 15-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: BricxCC release 3.3.7.6
|
|
Hi John, Thanks to your pre-built BrickOS tools, I have finally installed it on my Windows 2000 machine (I tried several times in the past... no luck !). The installation was really fast and easy, the only problem I got was that the default BrickOS (...) (21 years ago, 15-Jan-04, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: The BrickOS Task Manager
|
|
(...) C++ is more particular with types than regular ol' C. However, I think BrickOS's definition of NULL in mem.h is incorrect (as this was causing one of the problems in the execi call). IMO, it should be defined like so: #ifdef __cplusplus (...) (21 years ago, 13-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
(...) When saved as multi.c, but not when saved as multi.cpp (...) Start multiple tasks within a program that uses objects. I could rewrite a number of parts to use structs instead, but I just wanted to check that there wasn't some easy solution. (...) (21 years ago, 13-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
(...) Were you able to compile it as is? What are you trying to do? What errors are you getting? I tested that with version xx.09, not the latest one. Steve (21 years ago, 13-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
(...) Thank you again for the help, but unfortunately it only compiles when saved as a '.c' file. Some of my code depends pretty heavily on classes... is there any easy change to make this work as object oriented code? *just spent two hours trying (...) (21 years ago, 12-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: BricxCC release 3.3.7.6
|
|
(...) I will make this change. Thanks for the report! John Hansen (21 years ago, 12-Jan-04, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: BricxCC release 3.3.7.6
|
|
small suggestion: when you've a syntax error in NQC, it goes like this - error is reported - you correct the error - recompile the source - code is downloaded - error message disappears In my opinion, the last 2 actions should be the other way (...) (21 years ago, 11-Jan-04, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Re: The BrickOS Task Manager
|
|
(...) Thank you very much. That was exactly what I needed. Very much appreciated. Mike (21 years ago, 10-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
(...) This works. Steve ---- #include <unistd.h> #include <dbutton.h> #include <dmotor.h> int MotorSpeed = 0; int RunMotor() { while (!shutdown_requested()) { motor_a_dir(MotorSpeed); } return 0; } int CheckButton() { while (!shutdown_requested()) { (...) (21 years ago, 10-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Implementation of Installable Timers
|
|
(...) I'd go with the flag, myself. (...) Its certainly possible for the client timer to reinsert itself - therefore the recurring timer is not strictly required. It could be left out for space reasons. I'd probably either take it out and make it (...) (21 years ago, 10-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
(...) Sorry, I'm still just not getting it at all. I have type errors all over the place trying to pass arguments to my task. Could someone please simply email me or post an example of a program that starts, runs two or more threads, and will (...) (21 years ago, 10-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Brickos fun and games!
|
|
Hello. I have finally got gcc 2.95.3 - the official brickos compiler - installed on my computer (SUSE Linux). I can type "make" and compile all the brickos directory fine. firmdl3 works fine. BUT, dll doesn't seem to work. When I use dll to download (...) (21 years ago, 9-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Implementation of Installable Timers
|
|
(...) It would seem reasonable to check the location of the struct; if in kernel memory, don't remove; if in user memory, remove. However, you could add a flag to the timer struct which could use T_KERNEL and T_USER flags. (...) I looked quickly (...) (21 years ago, 9-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Implementation of Installable Timers
|
|
(...) You are right. I found in an app that I was using that if I pressed the run / stop button, my task would be killed, and leave a dangling timer - which would usually blow the little brick into the weeds :o) I 'solved' it in a crude way by (...) (21 years ago, 9-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Implementation of Installable Timers
|
|
Iain McInnes wrote: [snip] (...) Great idea! (...) In your implementation, would it be possible for the client task to be killed (in the case of a run-away task)... causing the struct to be deallocated... while the struct is still in the linked (...) (21 years ago, 8-Jan-04, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Points to: 'Implementation of Installable Timers'
|
|
Hi, ppl. I posted this one in the wrong place :0 (URL) Enjoy ! Iain. (21 years ago, 8-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Points to 'Design by Contract'
|
|
Hi, Folks, I posted some stuff on an assert() macro - in the wrong place - (D'oH). The thread is here: (URL) Enjoy ! Iain. (21 years ago, 8-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Hello World !
|
|
Hello everybody. I’ve been fooling around with BrickOS in the last few weeks, becoming familiar with it. BrickOS is very cool. Thank you, those who have made it what it is, and thank you, those who help out those with the common problems (yes, I had (...) (21 years ago, 8-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
IIRC the issue was that Task, Process and Thread were all used to represent the same item/concept in the Kernel code. After some discussion, it was decided that the word Task would be used in all cases. This improves readability, etc... (ie. Task (...) (21 years ago, 6-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Sensor Power
|
|
(...) Take a look at the functions ds_power_on() & ds_power_off() as defined in the dsensor.c kernel file. When you've set the sensor to passive mode, you should be able to manipulate the sensor power bits using these functions[1] or just use the (...) (21 years ago, 6-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Display
|
|
(...) This problem has been fixed in the most recent CVS source file (dmotor.c), but as far as I can tell it hasn't been part of an offical release yet: (URL) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
tid_t -> thread ID pid_t -> process ID ? "nanobapt" <nanobapt@wanadoo.fr> wrote in message news:3FF95FD4.608020...adoo.fr... (...) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Sensor Power
|
|
ok, I have a real question. I'm interested in sending messages between RCXs using only the sensor ports. I've tested and found by switching between active and passive, signals can be sent, however, when the port is set to active, it is not powered (...) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Motor Display
|
|
For some silly reason, I was browsing through the BrickOS code and I noticed this: void motor_a_dir(MotorDirection dir) { dm_a.dir = dm_a_pattern[dir]; dlcd_hide(LCD_A_LEFT); dlcd_hide(LCD_A_RIGHT); if (dir == fwd || dir == brake) (...) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
(...) only as a side note: you shouldn't really do this. you are burning precious cpu-cycles here. it should look something like while(!(rowdone && coldone)) msleep(5); if you're in a hurry you can make smaller msleep's... (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
in version 2.6.1 (I've just download it) extern tid_t execi(int (*code_start) (int, char **), int argc, char **argv, priority_t priority, size_t stack_size); declare in unistd.h ! So use the tid_t and not the pid_t ! (like say ROSCO) Does anyone (...) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: problems wirh installing driver for usb-tower under linux
|
|
Von: "Annedore Rößling" <u15780@hs-harz.de> Betreff: Re: problems wirh installing driver for usb-tower under linux Datum: Sonntag, 4. Januar 2004 13:25 (...) When I tried ./configure --with-linux-include...n/include/ confiure.in continued but (...) (21 years ago, 4-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: The BrickOS Task Manager
|
|
(...) [snip] (...) Hi Mike, What version of BrickOS are you using? IIRC the correct type for thread IDs in the current version is tid_t, not pid_t. Also, I dunno if it was a typo, but you should include tm.h, not tm.c. HTH ROSCO (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
|
