 | | Re: .lx format
|
|
(...) Look at legOS makefiles. The lx file is generated from two symbolsrec executables linked to different positions. The files are generated with a special linker script "legOS.lds". Maybe you can do the same with your compiler and use the makelx (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: code
|
|
(...) [etc.] Also, don't you use ROTATION_X instead of SENSOR_X once you get the rotation sensor set up on that port? I thought it was something like that. I'd also like to comment that this is dangerous. It's theoretically possible that your sensor (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: code
|
|
yego, The wait_event function takes an event function as the first parameter, not a sensor number. You need something like (forgive any errors - I don't have LegOS available at work) int rotation_event_3(wakeup_t data) { if (SENSOR_3 == data) return (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | code
|
|
Hi, I'm a newbie to c++ and legOS. Here is my code. Do you know what is wrong with it cause I don't. Thanks /* s.c*/ #include <unistd.h> #include <dmotor.h> #include <dsensor.h> int main(int argc, char **argv) { /* turn it on */ (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Library use in LegOS
|
|
Jakob "Fepp" Engblom <fepp@ieee.org> wrote in message news:GAr7Gr.2v3@lugnet.com... (...) handled (...) Each program gets it's own copy (...) Hmmmm. Not sure. Wish I knew more about compiler internals... (...) have (...) It's all custom written - (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS papers?
|
|
(...) I could do with some technical references for my bibiliography, and so after much searching[1], I can reveal that that AUC is Aalborg University, Denmark. Furthermore, most of the authors can be found in the Computer Science department: (URL) (...) (24 years ago, 25-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Linking failure when 'making' an lx file
|
|
(...) Syntax error: you are missing a parenthesis at the start, right after the if. But gcc should give a fat error at the ">" sign I believe. if( COND ) STATEMENT; if( (ul_var1 - ul_var2) > sizeof(uchar)) STATEMENT; (...) It is miraculous that the (...) (24 years ago, 25-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Memory Usage
|
|
(...) Having written a few embedded-systems compilers, I must say that using floating point on an 8-bit chip like the H8 is generally considered crazy. The values eat memory, and the libraries drawn in can get really large (at least for a production (...) (24 years ago, 25-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Library use in LegOS
|
|
Hi! Another technical question about LegOS: how are libraries like float handled today? Is there one copy linked into LegOS, or is each downloaded program equipped with its own copy? If I would use a different compiler, with a different set of (...) (24 years ago, 25-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: pass by refrence or value?
|
|
Some basic facts about C semantics: As already stated, globals MUST be volatile if they are accessed by more than one thread, otherwise reads and writes can be out of sync. What are the types of the variables involved? Scalar values like integers (...) (24 years ago, 25-Mar-01, to lugnet.robotics.rcx.legos)
|
