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