 | | RE: newbie
|
|
If you decide to use LegOS you won't be needing nor will you have the chance to use NQC because a RCX with LegOS loaded won't understand nor respond to any standard firmware commands. Check (if you didn't already) the side links at: (URL) From: (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | RE: newbie
|
|
so if i decide to use LegOS I don't need NQC, right? as I understood, de LegOS itself it's complete to be used alone.... (...) programs on RCX. (...) LEGO (...) could call (...) LEGO (...) standard LEGO (...) for (...) run some (...) don't (...) -- (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | RE: newbie
|
|
LegOS is an operation system ( a firmware replacement in itself) It's like a mini UNIX system, that will run true C compiled programs on RCX. NQC on the other hand, all it does is translate a NQC program into LEGO pCode that will be *interpreted* by (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | newbie
|
|
Hi everybody, I'm starting to use Lego products and I'm having problems to undrestand a few things. For example, I want to use NQC and I don't understand why the LegOS needs a C cross-compiler... or by having LegOS I don't need NQC? -- Paula Berger (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: thread class for legOS
|
|
(...) Static DOES matter; it declares the method as being a "class" method, rather than a normal instance method. I believe there is no implicit 'this' parameter and therefore it can be treated like a normal function. Of course, it can't be linked (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: thread class for legOS
|
|
(...) No, static doesn't matter but it is possible the calling conventions of C and C++ might be different (I don't know of a platform where that is the case for a an extern function), so you might need to specify C linkage, as in: extern "C" int (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: thread class for legOS
|
|
(...) Haven't done any C++ for a while, but IIRC you just need to declare runWrapper as static, ie: private: static int runWrapper(...) ; HTH ROSCO (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: threads - bug in the firmware?
|
|
(...) Advantage: Less memory used (each thread needs a block of memory in the kernel, I'm at work & can't remember the struct name off hand). In the case under discussion, this doesn't make much difference, but in a large project, memory use can (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Still having problems with helloworld.c
|
|
John, Where is the source for makelx ?? I am having this same problem. Thanks JohnG (...) (23 years ago, 20-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Routing daemon with tcp/ip for RCX/legOS, Cybermaster/NQC
|
|
Sources for the LNPoI Router are available now. You find it at (URL) . Bye (23 years ago, 20-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: More on threads
|
|
(...) I recall that legOS's priority model is pretty rigid. If a thread with a higher priority never yields, threads with lower priority will never get any time. When I write legOS programs, I generally just have everything run at PRIO_NORMAL. That (...) (23 years ago, 19-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: More on threads
|
|
(...) Digging through tm.c gave me the impression, that main will indeed get no time slice. So I wrote another test program: ---...--- #include <conio.h> #include <unistd.h> pid_t worker; int work_task(int argc, char *argv[]); int main() { int i; i (...) (23 years ago, 19-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: More on threads
|
|
(...) ability to terminate but to run in an endless loop. But This is not true of an embedded system though which will have to run 'forever'. (...) priority of NORMAL+4. So, the (...) any time slice at all. NO time slice or just a very small chunk (...) (23 years ago, 19-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | More on threads
|
|
(...) Of course you are right. I think it is a bad programming style not to give your program the ability to terminate but to run in an endless loop. But what is the penalty for this bad style? I've done some investigations and here are the results: (...) (23 years ago, 18-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: thread class for legOS
|
|
(...) IRC, every method in C++ has an implicit parameter wich is the object itself; that's why you can't cast it. Try the following (does someone have a nicer solution?): Put runWrapper() outside the class: int runWrapper(int, char **th) { (...) (23 years ago, 18-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | thread class for legOS
|
|
I write a Thread class for LegOs with a simple interface like in Java or CommonC++. I'm using LegOs 0.2.4. Below are my work till yet. The problem is in the Method Start(). The line is marked with !!. The error message is at the end of the file. I (...) (23 years ago, 18-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Routing daemon with tcp/ip for RCX/legOS, Cybermaster/NQC
|
|
"Freddy" <mail-nowak@web.de> schrieb im Newsbeitrag news:GpzyB6.Kpt@lugnet.com... (...) A C++ class to build client application without knowing the LNPoI protocol is available for Windows and Linux now. (URL) (23 years ago, 18-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: threads - bug in the firmware?
|
|
(...) I would strongly suggest changing this to while(1) msleep(bignumber);. Otherwise you're hogging the processor doing nothing important, which could do bad things to any compute-intensive tasks you may have going. It'll also use slightly less (...) (23 years ago, 18-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: threads - bug in the firmware?
|
|
Hi Ross (...) you (...) What are the advantages and disadvantages of this method as opposed to the one I used? mike (23 years ago, 18-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: threads - bug in the firmware?
|
|
(...) Note also since bumper_task() is an infinite loop, and you never use pid1, you could save one thread by doing this: int main(int argc, char *argv[]) { pid2 = execi (&left_task, 0, NULL, PRIO_NORMAL+2, DEFAULT_STACK_SIZE); pid3 = execi (...) (23 years ago, 17-Jan-02, to lugnet.robotics.rcx.legos)
|
