 | | Re: LNP-problem...
|
|
That looks ok to me. But I'm no expert on LNP. Here's a clip I use. It looks a lot like what you're using. It seems there may be a problem with your receive code. I'm REAL shaky on that. What does fputs do? ---- char *s; s = "101"; if (strlen(s)>0) (...) (22 years ago, 21-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP-problem...
|
|
(...) ok this is the (relevant) code running on the rcx: int main(int argc, char *argv[]) { char *p; init(); execi(&PacketWatcher, 0, NULL, PRIO_NORMAL, DEFAULT_STACK_SIZE); execi(&Messenger, 0, NULL, PRIO_LOWEST, DEFAULT_STACK_SIZE); return 0; } (...) (22 years ago, 21-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
(...) It's the one I meant, thanks. Jürgen (22 years ago, 21-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Why...
|
|
Nick, Setting the timeslice to a low number (5ms is fairly low), negetively effects overall system performance. Time used by the operating system for task switching is taken away from applications. If a switch takes .5ms (for example) and you switch (...) (22 years ago, 21-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Why...
|
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ... is the minimum timeslice interval 5ms? I'm writing a program that needs a routine to be run every 1ms for a period of time. I did this by setting it as the timeslice handler, but then I needed to (...) (22 years ago, 16-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
(...) Yeah, I missed that, I'll add that to the notes. (...) Too bad they didn't document the hole well enough to make it obvious to the people at Lego, who apparently had no idea. They use "mov.w rx,@0xf000:16" all over the place instead of the (...) (22 years ago, 20-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
(...) Thanks for the suggestion... I think the change I made a few days ago included a note here also, but we might be talking about different spots. Let me know if not... kekoa@stanford.edu. -Kekoa (22 years ago, 20-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | LegOS/BrickOS on Mac OS X?
|
|
I was wondering if anyone had successfully ported the H8 compiler over to OS X? With an USB IR Tower, and the underlying Unix/BSD resources on the Mac, it would be an ideal development platform. I've tried compiling the H8 Cross compiler without (...) (22 years ago, 20-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP-problem...
|
|
Why don't you post the code you're using. Then we can tell you if it's a problem with the program. Steve ----- Original Message ----- From: Tom Wouters <aqua@no__spam.ulyssis.org> Date: Wed, 20 Nov 2002 17:21:47 GMT To: (...) (22 years ago, 20-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | LNP-problem...
|
|
hi there we seem to have a not so tiny problem with lnp, we can send messages from the tower to the rcx, but until now we have failed to get the rcx to send a message tot the computer, we have tried various versions of the legos kernel, none of them (...) (22 years ago, 20-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: BrickOS & Cygwin
|
|
(...) You bet. I've fixed this in CVS so it will be in our next test release. Thanks for reporting it. (This is why we do test releases ;-) Regards, Stephen -- Stephen M. Moraco stephen@debian.org (22 years ago, 19-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | BrickOS & Cygwin
|
|
I've downloaded and installed test release 09. Once again things worked very well. But there is one definite problem with this release (as well as 08) when running under Cygwin. In Makefile.Common the lines ifdef BUILDING_HOST_UTILS # ---...--- # (...) (22 years ago, 19-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
(...) As it is, it seems[1] that two of the three NAND gates in the 74HC10 are being used as a driver for speaker output (it's odd that it's two, not one though). So, this leaves one three input NAND gate to do the decoding. Now that I think about (...) (22 years ago, 14-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
<snip> (...) Ok, thank you for the explaination! I am thinking that the Memory Manager would need some rework to support this, since the start of memory is currently established at compile time. I will have to take a look at this (time allowing). (...) (22 years ago, 14-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
(...) I have implemented what Mark Riley has suggested. I submitted a patch to the patches section at the sourceforge project page. The changes are quite small but require some tricky tweaks to the build process. I have only minimally tested it and (...) (22 years ago, 14-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
(...) While you are at it you could also make a remark near the explanation of the f000 motor control register, and make it clear that this is a hardware function. When I started to use this extra memory in leJOS I missed the remark at the very end (...) (22 years ago, 14-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
(...) In that case, why didn't the RCX designers use an 8 input NAND to decode their addresses, to leave more of the RAM usable? Maybe there werent aware of this possibility? Jürgen (22 years ago, 14-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
It also turns out that there are 8 bytes of external RAM that peek through at addresses 0xff80-0xff87. Writes to these locations also affect the motor control register. I suppose there's a small advantage in using these registers to control the (...) (22 years ago, 14-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
(...) This is interesting. It makes sense that the memory backing these locations still works, but I never would have thought to try to use it. I will make a note of this on my pages. -Kekoa (22 years ago, 13-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
(...) Interesting, I never looked at that version. I think the one disassembled by Kekoa is 0309. Current versions of leJOS also use this upper memory to store part of its firmware (almost 3K). Jürgen (22 years ago, 13-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
