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