 | | Re: Assembly in my C-program
|
|
(...) If you want to drive directly the motors you should first disable motor handling in legOS (remove CONF_DMOTOR definition in config.h). Then you can create a high priority task that switches motors on and off writing in the motor output port. (...) (23 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Assembly in my C-program
|
|
(...) pulses (...) at (...) would (...) Hmmmm. This should be possible, but it's a bit more tricky with stepper motors - you have to allow for the speed-up and slow-down. Thus just calling motor_speed(50) would have to initiate a task that starts (...) (23 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Assembly in my C-program
|
|
Actually I am trying to control a stepper motor. So when i need to send 50 pulses fast, motor on and off takes same time because there same other tasks running at the same time. So it would be much quicker if I could just call motor speed (50), and (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Assembly in my C-program
|
|
(...) to (...) This should be performed by mapping a variable on top of the memory location, and NOT by inline assembly. (...) What is wrong with speed=0 for off and speed=255 for on? /jakob (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Assembly in my C-program
|
|
HI, I was wondering if I could write assembly code in my c-program. I would like to access the motor output port as a digital port and control when it is on and when off (possibly writting something like "mov.b r6l,@0xf000:16"). Or can I change the (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: .lx format
|
|
(...) We are going to use this solution. Seems simpler. /jakob (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Running IR in the background
|
|
(...) Congratulations! Could you post your source code here, to compare with the solution that we previously submitted to an almost identical question? We use an active light sensor reading in one taks, with a different task bangin zeroes using (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: .lx format
|
|
(...) We arrived at that solution independently here... it makes more sense. Also, since only the parts of the kernel we actually use need to be linked in, the result should be much smaller than a full kernel. Furthermore, the compiler we are using (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: .lx format
|
|
(...) We arrived at that solution independently here... it makes more sense. Also, since only the parts of the kernel we actually use need to be linked in, the result should be much smaller than a full kernel. Furthermore, the compiler we are using (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Library use in LegOS
|
|
(...) of (...) For the IAR compiler, this should not a problem. The libraries are optimized for minimal size, so we can probably use the standard libraires. And give our students the benefit of a full C lib. /jakob (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Neural network for legOS... ??
|
|
(...) Sorry Niels, but I would say just try it yourself, they're not that hard to do, failing that if you can find the source for a small ANN, then that stands a good chance of working, I'm running quite a powerful evolutionary algorithm on mine, (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Running IR in the background
|
|
Hannes, I got it to work last night. I'm modifying Markus Noga rover.c code (included when you download legos files) to include support for IR port and (passive) light sensor. Great code to look at if you're just learning C/C++. Basically, the (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Running IR in the background
|
|
(...) Commentary below. (...) I must have missed this one the first time around. lnp_logical_write() will block, but it should only block the thread it's called from. Put your send-zero loop in a separate thread and I think you should be set. (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Running IR in the background
|
|
(...) Huge coincidence that your message should be the first I see after not having read the newsgroup for almost a year. No, as far as I can remember I never got an answer. I am using mindstorms for my final project after not having a chance to (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Running IR in the background
|
|
Hannes, Did you ever get any help with your question (below)? I'm trying to use the IR port on RCX along with light sensor (passive) as collision detection device. Having the same problems you're having. Clayton (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
