 | | Re: Compiler
|
|
Hi Lou, new binaries would be nice. I did create an archive, but I didn't feel like pumping those Megabytes over my modem yet. Mine is about 3.3MB, though - did your install script really strip all those executables? Markus. (26 years ago, 25-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
On the subject of licences: I always forget the details, coz they bore me, but as a result of working on Apache, I do know a few things: 1. There is an LGPL that is less restrictive than GPL. 2. GPL licences are not compatible with all other (...) (26 years ago, 24-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
(...) I am by no means an license expert, but I just happen to have been reading about the GPL, and the MPL is pretty similar, though there are, of course, differences. The doc that I read stated that you can apply the GPL only to the files that you (...) (26 years ago, 24-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Compiler
|
|
(...) That does appear to have been the problem after all. (...) I eventually managed to build egcs on a different computer and copy it over to mine. Markus -- if you want the binary (bzip2 cpio) of binutils and egcs, I could point you at it for (...) (26 years ago, 24-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
(...) Read the MPL again. It's not clear to me that you need to MPL all your code if you include unmodified source from something that is covered by MPL. But if you include MPL'd source, you certainly have to make it clear what code is covered by (...) (26 years ago, 23-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
(...) Yes, I believe GNU configure is covered by GPL. I already changed legOS licensing to MPL because Kekoa's math routines are MPL. I'm not sure if we may continue to use them if we change yet again. What's the status on menuconfig? Are those (...) (26 years ago, 23-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
(...) What about a simplified gnu 'configure' ? Or would using that scheme mean incorperating the GNU license as well? :) Richard (26 years ago, 23-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Compiler
|
|
I have discovered that the instructions for building the compiler on the legOS site have changed. They now say to build egcs, whereas they used to say to build gcc. This could, conceivably, be why I cannot build good files with 0.1.7, since I'm (...) (26 years ago, 23-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
Menuconfig would be a great thing. Xconfig would be even better, but I agree with Markus' concern about portability. The Linux kernel distributions get around the portability by simply providing all three config tools and letting you use the most (...) (26 years ago, 22-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: How do I convert light sensor data into image bmp?
|
|
(...) Sorry, but I don't understand. Adamski _______ <adamski2000@adamski...rve.co.uk> (26 years ago, 22-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
(...) Exactly. Can you say "make config"? Ah, no, that won't do. "make menuconfig", maybe? We'd have to stay portable, though. That rules out "make xconfig" :-( (26 years ago, 22-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
(...) That would be funky :) * Location of H8300 binutils * Location of perl (mergemap script) * Serial Port (RCXPORT) variable? * Compile Options? eg --disable-task-management ? That sort of thing? Richard (26 years ago, 22-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
How about a ./configure script? It just needs to ask two questions... write the answers in .config or Makefile.common or whatever suits your fancy and you're done once and for all. (26 years ago, 22-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Reworked Scheduler
|
|
I have gotten my scheduler changes to work. There is a patch against 0.1.7 on my legOS page ((URL) will apply most of the way against 0.1.6, but there are some bits that you will have to apply by hand due to differences in comments. I wouldn't be (...) (26 years ago, 21-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | How do I convert light sensor data into image bmp?
|
|
Hi: I would like to build a lego scanner using a single light sensor. I have found a number of sites which explain how to build them, however, I could use some assistance with how to convert the data collected into an actual image map. I understand (...) (26 years ago, 20-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
(...) That is true. (...) Yes, we do, but is that something the tasks need to worry about? If the kernel has buffered 3 datagrams since the last timeslice, the next 3 waits would return immediately, since their criterion (datagram ready for reading) (...) (26 years ago, 20-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS-0.1.7 released
|
|
I finally got my scheduler working on 0.1.6. Porting it to 0.1.7 wasn't too painful. But when I tested it (I have been testing with demo/tm-and-ir), I found that there is junk (not necessarily alphanumeric characters) displayed on the LCD. Thinking (...) (26 years ago, 20-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) Try delay(). It's the non-scheduler version of msleep(). If you have a version that's better calibrated, please patch delay() in conio.c to reflect that. (...) A branch to itself is probably the best you can do, as you need an atomic (...) (26 years ago, 20-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: H8300 Stack and SLEEP
|
|
Sorry I'm late. I believe this is not an issue with legOS. legOS only calls the ROM powerdown function at the end of its kmain() loop, where the stack pointer should be in the on-chip RAM area anyway. When sleeping in the idle task, legOS directly (...) (26 years ago, 20-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
(...) Yes, it's a start byte. Jacob suggested using 0xFn to identify protocol versions, 0xFF being the LEGO standard. (...) Actually, you wouldn't have to change much, just treat P_SUSPENDED tasks like they're P_WAITING and the condition failed. (...) (26 years ago, 20-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
(...) Cool! (...) I had been thinking along the same lines. (...) What is the ID? Is it for framing? Is it a byte that is not currently taken up by a Lego bytecode? Do we even care about colliding with Lego's communication protocol? (...) (...) (26 years ago, 19-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | mailing list / 0.1.7
|
|
Hi Jacob, maybe you should join the legOS discussion group. lugnet.robotics.rcx.legos is available via NNTP, WWW and email from www.lugnet.com. Ah, by the way, 0.1.7 is out. Markus. (26 years ago, 19-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
Hi Lou, I'm discussing datagram networking with Jacob Barrett currently. They have some people working on it. The idea is to provide 1 byte of address space, using a per-host hostmask, just like TCP/IP uses per-net netmasks. A host with address 0x10 (...) (26 years ago, 19-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | legOS-0.1.7 released
|
|
Hello, legOS is an embedded OS for the LEGO Mindstorms RCX. It can be programmed in C, assembler, and some language elements of C++. Preemptive multitasking, access to all 32k RAM and low-level hardware control are some of its most prominent (...) (26 years ago, 19-Mar-99, to lugnet.robotics, lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) It's what I'm doing for now in my debugger work. I haven't tried it out yet, though. (...) I carefully looked at the opcodes, and found that the shortest opcodes are all 2 bytes, and hand-coded the 2 byte instruction that jumps to itself. The (...) (26 years ago, 17-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) However, last night, I wrote a brute force (spin loop) msleep which works fine in the scheduler. I found that 800 iterations of an empty for loop with a 16 bit index comes pretty close to 1ms. Granted, I cheated a little, knowing that the (...) (26 years ago, 17-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) Oh, you're doing stuff inside the scheduler. Yeah, msleep doesn't work too well there :-) Yes, the pauses were only so I could see what was going on. Another thing you could do is print messages out the IR port; but I'm not sure how it would (...) (26 years ago, 17-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) I don't think it does. Of course, the source would answer definitively, but I also know that until I remembered to put the refreshes in there, I didn't get useful output. (...) I did that too. In my case, the lower byte was the priority (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) That's the method I've used. Just be sure to put an lcd_refresh() after the cputw() call - I can't remember if cputw() does the lcd_refresh() or not. Another thing I've done is write out a number where the upper byte indicates a position in (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: H8300 Stack and SLEEP
|
|
Kekoa wrote: <<snipped original description of problem>> (...) <<snipped description of tests>> Once again, Kekoa goes the extra mile and proves what many of us are happy to be merely confident about. Someday, I'd like to be reincarnated as a grad (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.pbforth, lugnet.robotics)
|
| |
| | Re: FW: H8300 Stack and SLEEP
|
|
(...) To be more precise, it applies to sleep mode and software standby mode as long as you set port 5 bit 2 to high before activating either mode. It does not apply to hardware standby mode, since that does not save registers or end with an (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | Re: H8300 Stack and SLEEP
|
|
(...) After talking with Ralph over the weekend, I suggested a test he might do to figure out if port 5 bit 2 really does what he suggested it might. I don't think he did this test, so I fired up my RCX and hacked it together. I verified that port 5 (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.pbforth, lugnet.robotics)
|
| |
| | Debugging
|
|
Do you guys have an established mechanism for debugging? I'm thinking of writing certain numbers to the display using cputw(). The idea being that the number frozen forever on the display will be the (approximately) last place the code was ok before (...) (26 years ago, 15-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Program Wanted
|
|
Does anyone have a program for the Recycler robot? Please help! Adamski _______ <adamski2000@adamski...rve.co.uk> (26 years ago, 15-Mar-99, to lugnet.robotics, lugnet.robotics.rcx.legos)
|
| |
| | FW: H8300 Stack and SLEEP
|
|
(...) Markus, (and anyone else listening) I think it applies to the RCX power_shutdown() function as described in Kekoa's reference. The key is that this function puts the external RAM into low-power mode. If you are not calling power_shutdown() or (...) (26 years ago, 15-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | H8300 Stack and SLEEP
|
|
Hi All, If this is old news, ignore it... I just figured out this weekend (thanks Kekoa) that the H8/300 stack pointer (r7) and the power-down function in the RCX have a close relationship. The stack pointer MUST be in the on-chip RAM area (0xFD80 (...) (26 years ago, 15-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.pbforth, lugnet.robotics)
|
| |
| | Re: Idle process
|
|
I guess my earlier posting got out after all. I got the message from the NNTP server telling me to register. That is why a slightly different version of my message appears later in the group. (...) I plan to keep the idle task, now that I understand (...) (26 years ago, 11-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
(...) The idle task actually has the lowest priority in my scheme, but there was some efficiency gained in making the task list loop around. If the idle task is always there, it makes for simplified code in multitasking startup if you rely on that. (...) (26 years ago, 11-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
Sorry this message is so late, I had to get registered for posting from my work address. (...) I, too, consider power saving to be a valuable (indispensible) feature. That is precisely the sort of thing that I feared I might be overlooking. Up 'till (...) (26 years ago, 11-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
(...) I, too, consider power saving to be a valuable (indispensible) feature. That is precisely the sort of thing that I feared I might be overlooking. Up 'till now, I had not worked on an embedded project which would benefit from using (...) (26 years ago, 9-Mar-99, to lugnet.robotics.rcx.legos)
|
