 | | Re: thread class for legOS
|
|
(...) In the post you replied to saying "static doesn't matter", the proposal was: private: static int runWrapper(...) ; I then replied to your post, etc. Anyway, let's not degenerate into he-said-she-said. We're really just talking past each other (...) (23 years ago, 22-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: NQC 2.4 r1 released
|
|
Its been brought to my attention that Lego has already released the Mac SDK and driver for the USB tower (sorry I didn't see it!): (URL) should be able to post an updated version of NQC with USB support for Mac OS9 tomorrow. Dave (...) (23 years ago, 22-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: thread class for legOS
|
|
(...) In fact, neither of these suggestions will work with the code as it stands, because the runWrapper() function tries to call the Run() function, which is a non-static member function. You could pass a pointer to the class instance (this) in the (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: thread class for legOS
|
|
(...) Unless you define a function as a member function, there is no this parameter at all. In the example given, it was not a member function at all (nor should it be). I believe you are thinking of a static member function vs. a non-static member (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | RE: firmware
|
|
SDK 2 includes the latest version of firmware and tools to load it to the RCX. It's also included in the new RIS 2.0 CD The new RIS 2.0 is the one with the RCX 2.0 + USB InfraRed Tower + Latest firmware version (you could call it 2.0, yes) You can (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: firmware
|
|
this sdk 2 is the firmware??? -- Paula Berger E-mail: pberger@terra.com.br paula@inf.pucrs.br ICQ#: 71133278 "It's the end of something simple, and the beginning of everything else" -- ----- Original Message ----- From: "Robert Seifert" (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: firmware
|
|
(...) Firmaware is a kind of ?operating system? needed to be downloaded to RCX to allow it process programs. Physically it is file firmxxxx.lgo (where xxxx is a number ) located somewhere in directory tree created by RIS installation process. If you (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | 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: newbie
|
|
I'm not 100% sure, but when I used Spirit.OCX (VC, VB, Delphi, etc...) for some research, I was under the impression that it supported 3 types of interface: "Radio" (CyberMaster), "InfraRed" (RCX, Scout) and I think it was "Cable" or "Direct" or (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | firmware
|
|
People, What is this "firmware" that is supposed to be loaded into the RCX? Is there anywhere I can download it?? Thanks, -- Paula Berger E-mail: pberger@terra.com.br paula@inf.pucrs.br ICQ#: 71133278 (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | 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)
|
