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