 | | RE: NEW LEGO USB Driver
|
|
(...) Someone who's name I forget (you know who you are!) said definitely that hyperthreading cannot be simply disabled in BIOS - that Windows has to be reinstalled with a non-hyperthreading kernel. And to answer your musings in the first (...) (21 years ago, 8-Mar-04, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.robolab)
|
| |
| | RE: NEW LEGO USB Driver
|
|
As Mike pointed out, it is a hyper-threading problem. The reason for winXP not working, but W2K works, may very well be that W2K does not support hyperthreading feature, but WinXP does. I wonder if Mike or anyone does indeed disable the (...) (21 years ago, 8-Mar-04, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.robolab)
|
| |
| | Re: LegOS USB Support (for RCX 2.0)
|
|
Could you please send me all your files? (21 years ago, 8-Mar-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: USB tower/Linux/Firmdl not working nicely together
|
|
(...) Sounds promising. I can do some testing for you is you want. Is the code where you are working on available via CVS, perhaps I can do some coding too. Cheers Bart (21 years ago, 6-Mar-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: USB tower/Linux/Firmdl not working nicely together
|
|
Definitely interested in helping you test when it's working. Regards, Mark. (...) ---...--- The real purpose of books is to trap the mind into doing its own thinking. -- Christopher Morley Mark Syms <mark@marksyms.demon.co.uk> (21 years ago, 6-Mar-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: USB tower/Linux/Firmdl not working nicely together
|
|
Bart, (...) The problem is that USB tower on linux is not supported by firmdl3/dll at the moment. I'm working on that capability now. If I can, my intent is to have it work for 2.4 (user added driver) and 2.6 (built-in driver) kernels. The USB tower (...) (21 years ago, 6-Mar-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: [long] Interrupt programming, buggy code
|
|
On Tue, 2 Mar 2004 17:54:47 GMT "Mark Riley" <markril@hotmail.com> wrote: Hi Mark, (...) [snip] (...) [snip] And that was it, indeed! Many to you, as well as Ralph and Kevin who tried to help me. There shouldn't be much trouble for me I think (if we (...) (21 years ago, 2-Mar-04, to lugnet.robotics.rcx)
|
| |
| | Re: [long] Interrupt programming, buggy code
|
|
(...) Eh... Never mind this bit. I just had a gander at Kekoa's rcxlib and he already handles this correctly in debug_value(). Should've known! :-) Mark (21 years ago, 2-Mar-04, to lugnet.robotics.rcx)
|
| |
| | RE: [long] Interrupt programming, buggy code
|
|
Much better and more accurate answer from Mark - who knows a lot more about GCC that I do :-) I should stick to commenting on assembly language stuff. Ralph (...) <snippage> (21 years ago, 2-Mar-04, to lugnet.robotics.rcx)
|
| |
| | Re: [long] Interrupt programming, buggy code
|
|
Hi Benjamin, When you declare your ISR as an interrupt_handler, GCC terminates the function with an "rte" instead of an "rts". The ROM code that dispatches the interrupt to your function is already doing the rte so your function should not. Here's (...) (21 years ago, 2-Mar-04, to lugnet.robotics.rcx)
|
| |
| | Re: [long] Interrupt programming, buggy code
|
|
(...) All I can give you is guesses. There are pleny of gurus here who will know the answer. Do you know if the display_debug() routine or any of the things it uses depends on the interrupts you are taking over? If default interrupt handler provides (...) (21 years ago, 2-Mar-04, to lugnet.robotics.rcx)
|
| |
| | RE: [long] Interrupt programming, buggy code
|
|
Having fun yet :-) There are a few things you might want to keep in mind when writing ISRs for the RCX... First, avoid calling into the ROM from an interrupt handler. You never know how long they take, and you may in fact be hitting another OCIA (...) (21 years ago, 2-Mar-04, to lugnet.robotics.rcx)
|
| |
| | [long] Interrupt programming, buggy code
|
|
Hi all, I am currently programming the Lego RCX at low-level (plain C) using the GCC cross-compiler for Hitachi H8/300 and Kekoa Proudfoot's LibRCX. In fact, I'm designing exercises for students that learn micro-controller programming. Therefore, I (...) (21 years ago, 2-Mar-04, to lugnet.robotics.rcx)
|
| |
| | rcx communications
|
|
hello, for the needs of a robotic course, I am looking for programs for 2 rcx that will make 2 robots communicate and enable some "team play". if you have examples to send me, I will be pleased to get some help. my email: gros_chacal@hotmail.com (...) (21 years ago, 2-Mar-04, to lugnet.robotics.rcx.java)
|
| |
| | Re: Get/SetCommTimeouts
|
|
"Dick Swan" <dickswan@sbcglobal.net> wrote in message (...) I kind of suspected that .. but was not sure. I looked in the source of NQC and brickOS (and some programs I found on the Web) and they all seemed to use these functions regardless. But I (...) (21 years ago, 1-Mar-04, to lugnet.robotics.rcx)
|
| |
| | Where is prototype definition of packet_producer( ) ?
|
|
Thanks to those who have responded to my queries. Your info has been very helpful. Now I am trying to modify # of arguments to packet_producer() in program.c, but I am unable to find prototype definition in any .h files. Can someone tell me where it (...) (21 years ago, 1-Mar-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Get/SetCommTimeouts
|
|
"Shashank Date" <sdate@everestkc.net> wrote in message news:Htuzyn.6qG@lugnet.com... (...) parameters. I (...) The "SetCommTimeout" function only applies to "COMx" serial ports. You are trying to use it on a USB port! (21 years ago, 29-Feb-04, to lugnet.robotics.rcx)
|
| |
| | Get/SetCommTimeouts
|
|
I am trying to write a C program (using VC++ 6.0) to talk to RCX 2.0 on my Win XP (Home Ed) box. Everything seems to be OK except the get/set of Communication parameters. I cannot understand why. I have attached the minimal C program which does (...) (21 years ago, 29-Feb-04, to lugnet.robotics.rcx)
|
| |
| | Respondre el missatge: Use of lnp_addressing_write() in an RCX program.
|
|
You must send the packet to port 0 of the destination. The dest address is conformed by the address in the upper 4 bits and the port in the lower 4 of the char. So if you put address = 6 you are saying -> host=0 port=6 and you must send to host=6, (...) (21 years ago, 27-Feb-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Spurious bad readings from sensors
|
|
(...) Could it be noise getting into the analog power supply? If you're switching between brake and full power with the motor ports, it seems possible that some spikes could get through to the A/D converter. You might be able to test this by (...) (21 years ago, 25-Feb-04, to lugnet.robotics.rcx.legos)
|
