 | | 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)
|
