 | | Re: Library use in LegOS
|
|
(...) Not sure of the details, but the linker takes the .o file, and the symbol file LegOS.lds, created during the kernel compile, and produces two files; .ds1 & .ds2, which are then passed to makelx to produce the lx file. So it seems the linker (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: .lx format
|
|
(...) One other possibility is to not use the lx files at all - just stick to the srec format as (I think) LegOS used to (version 0.1.x?). A bit less efficient downloading the kernel all the time, but removes the need to dabble with lx format at (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Declarations in header files
|
|
Hi! This is very technical, but: does the declaration of an "extern inline const void" function really make sense? GCC accepts it, but that is a VERY lenient compiler. An extern function should be definition not have a definition, and 'const void' (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: .lx format
|
|
(...) So in effect, it is dependent on the gcc loader mechanism. Ungh! The idea of using two symbolsrec files: one could be kernel, the other the program. Would make sense for kernel call resolution. (...) I looked at it, and it mainly outputs (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Library use in LegOS
|
|
(...) OK. How are the calls to the kernel resolved? By the makelx program, or by some magical stuff in the linking. I can imagine compiling the kernel, getting a symbol table out, and then when compiling user programs, you use a linker DEFINE or (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Neural network for legOS... ??
|
|
Hi everybody I'm looking for a free neural network library, that I can use with legOS. Anybody knows where to look ?? Niels (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
