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