 | | Re: loading s/w
|
|
(...) The first instruction (at 03ae) places the stack in on-chip memory, assuming RAME bit of SYSCR is at its initial value of 1. Why not make rom_reset() disable interrupts, then do its thing? That would be the safest thing to do. -Kekoa (25 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) Well, if rom_reset() gets invoked near the end of your time slice, ROM has no time to reset the OCIA IRQ vector before the next timer tick. I'm not certain about the order in which ROM sets up data areas and IRQ vectors. legOS freely allocates (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) Assuming packets without large internal gaps, we could employ a timeout to wait for a packet transmission of unknown protocol type to end. At 2400 bps with 8E1 (LEGO, isn't it?), one data byte has 11 bits, so a space of 1.5*11/2400 s should be (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found
|
|
(...) Excellent idea. This would yield the default settings dead-on. (...) Scaling isn't about the final output. The final output is already in the standard format. Scaling is about shifting the raw sensor values displayed by the firmware six digits (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) Yes this will be a datagram only protocol for the time being. The LNP will allow us to do things like debugging and remote control. I have also invisioned something like a "shell" running on the legOS that you could either "telnet" in to or (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found
|
|
(...) Why doesn't somebody finish up the decoding of the ROM, specifically the routine at 14c0. This routine takes the raw sensor samples and converts them to usable values, including handling the temperature and rotation sensors. The standard (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) From what little I remember about the Lego protocol, here are some thoughts. *) On reception, some Lego packets may contain data which look like the beginning of a legOS native protocol frame. Most likely, the checksum would fail (once enough (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) What sort of safety are you referring to? Motors left running? My initial thought was of lost memory or data structures in an indeterminate state, but that would seem to be moot since you are restarting from the ROM, which will have forgotten (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) The interface is specifically datagram only. Dunno about packet reassembly; I doubt it as the philosophy is minimalism. The main advantage I see in it is the ability to change the degree of checking it does on your behalf to ensure packets (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found
|
|
(...) I suppose we could ask for help also to non-legos owners of RCX and rotation sensors. What if any of us posts a message in the robotics newsgroup asking for some reads of rotation sensors? Raw values can be read with the sandard firmware too (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
