 | | 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)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
Joe, [some reordering of comments for clarity] (...) The idea is to pick a certain number of functions that will fit in the upper RAM space (~2900 bytes) and put these functions in a seperate linker section (other than the default ".text" section). (...) (22 years ago, 13-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Control Register (0xf000)
|
|
Mark, This is very interesting. I have experienced strange motor behavior with programs on BrickOS before; I now wonder if this may have been the situation. I do not currently know enough about GCC to make the changes that you mentioned, but I am (...) (22 years ago, 13-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Motor Control Register (0xf000)
|
|
Seeing as how there's been little traffic here recently, I thought I'd post about something I found that's cleared up a little mystery (for me at least). It concerns the RCX register that is used to control the motors. This register lives at 0xf000. (...) (22 years ago, 13-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | how to calculate program size?
|
|
this has been asked before, but i cant seem to find the answer in my inbox. anyways, i was wondering how i could calculate the program size of the program on my rcx. im using legOS 0.2.4. any help appriciated kenneth johansen kennethj@stud.cs.uit.no (22 years ago, 5-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Release candidate brickos-0.2.6.08 avail for testing
|
|
After making this change everything worked perfectly, as far as I can tell. I had a lot of trouble trying to build the gcc cross compiler. With this build and the pre-build cross compiler from hitachi's website everything was very easy. Thanks! (...) (22 years ago, 5-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: controlling rcx with remote control
|
|
(...) No luck... It's for the lego remote... (22 years ago, 4-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP packet handler
|
|
(...) Hi :-) I had problem the same. After brushing code source per some days, I finished discovering that the problem was with the versions. I installed logOS 0.2.5 and everything functioned well. (22 years ago, 4-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Release candidate brickos-0.2.6.08 avail for testing
|
|
(...) I spoke too soon. There is a problem with cygwin and Makefile.Common in the new release. The host utilities are not built with -D_WIN32 which (of course) causes them to not work at all. In Makefile.Common there is a place where CFLAGS is set (...) (22 years ago, 4-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | I solved a small problem in lnp :-)
|
|
Hi :-) The problem is: When compiling programs made in language 'C++' using: # g++ myprogram.c -llnp The g++ would not compile and the follow messages appeared: /tmp/ccXFr7VZ.o: In function `main': /tmp/ccXFr7VZ.o(.text+0x95): undefined reference to (...) (22 years ago, 4-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Interruptions in BrickOS
|
|
Good questions! See responses below... "Martin De Wulf" <madewulf@ulb.ac.be> wrote in message news:H51ItF.Ax1@lugnet.com... <snip> (...) You may want to check out the latest (now called BrickOS) at (URL) For us, real-time properties of the platform (...) (22 years ago, 4-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Release candidate brickos-0.2.6.08 avail for testing
|
|
(...) I had essentially no problems with brickos-2.6.08 - aside from noticing at least a couple new headers I have to port to Pascal. configure worked like a charm. The only issue I encountered was regarding TOOLPREFIX. The way that I have my cygwin (...) (22 years ago, 4-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | LNP packet handler
|
|
Hi, i am a student at the technical university of Athens and i am currently working on a project utilizing legOS 0.2.6 and LNP under Linux 7.3. My first aim is to establish communication between the RCX and the PC. I installed all the software (...) (22 years ago, 4-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Interruptions in BrickOS
|
|
Hi, I'am a researcher of the Free University Of Brussels. We're currently working on embedded systems. We would like to generate code for embedded systems from a specification language which could be used for formal verification. We chose Legos for (...) (22 years ago, 4-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: controlling rcx with remote control
|
|
(...) I've been trying to find the same thing. I believe the latest version of BrickOS has the ability to read a remote control, but I haven't spent the time to figure it out, yet. Check this out: (URL) (22 years ago, 3-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | controlling rcx with remote control
|
|
Hello, I'm new to this newsgroup but I need help with an issue... I'd like to control my rcx (with legos) with a tv remote control or likewise. I'm not a happy owner of the standard lego remote control and therefore I can not use the patch from (...) (22 years ago, 3-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | error deleting program
|
|
Hi, Could anyone please tell me what I'm doing wrong? This is my problem: When I try to download the helloworld demo with: $./util/dll -v demo/helloworld.lx ,I get the following error message(s): opening tty... KeepAlive Init... KeepAliveSend: (...) (22 years ago, 2-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: brickOS & GNU Pascal (update)
|
|
(...) <snip> (...) Good work on this. Yes I believe we would like to add this support. We are crunched with trying to get what we want into this next release. We likely can add some of the Makefile mods in this release, maybe the Pascal Units as (...) (22 years ago, 2-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: versions of gcc/binutils/newlib
|
|
(...) GCC 2.95 versions and binutils 2.95 thru 2.10 appear to work. I believe readers, here, have also successfully used gcc 3.0 and 3.1 but not 3.2. The brickOS plan is to release brickOS-1.0.0 first. Then we will work on adapting the code to work (...) (22 years ago, 2-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | versions of gcc/binutils/newlib
|
|
Hallo, Which versions of gcc/binutils and newlib is brickos developed with? As I read in here and tested myself, it doesn't work with the most recent versions (gcc 3.2, binutils 2.13 and newlib 1.10). Do I need a newlib? The howto doesn't mention (...) (22 years ago, 2-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: brickOS & GNU Pascal (update)
|
|
(...) Pascal/OOP definitely adds a bit of overhead. It is possible that some of that overhead could be lessened by tweaking the Pascal headers. I'm going to fiddle a bit with a couple of different approaches to see what works best now that I have a (...) (22 years ago, 1-Nov-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: brickOS & GNU Pascal (update)
|
|
(...) Great work John! Do you have any comparisons of executable sizes between C/C++ and Pascal/OOP? ROSCO (22 years ago, 1-Nov-02, to lugnet.robotics.rcx.legos)
|
