 | | I'm being stupid. But how?
|
|
I've written a test program using the 19990330 LegOS snapshot[1], and it's misbehaving oddly. The program looks like this: (the headers are the result of my frobbing the LegOS headers to refer to <mindstorms/{legOS header}>...) #include (...) (25 years ago, 29-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: HOWTO v 0.1
|
|
(...) Not half bad IMHO. But why point egcs searchers at ftp://go.cygnus.com/...gcs-1.1.2/ ? The canonical site is ftp://egcs.cygnus.co...cs-1.1.2/. egcs-1.2 will be out fairly soon. There have been changes to the h8300 support, but the changes are (...) (25 years ago, 29-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Read me first! Re: case statement doesn't work- any clue?
|
|
Nevermind. Dangit. Forgot break statements like a moron. -Luis (...) ###...### God was my co-pilot, but we crashed in the mountains and I had to eat him. -bumper sticker ###...### (25 years ago, 3-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: case statement doesn't work- any clue?
|
|
(...) Doh! You haven't put any breaks between the cases. BTW, if LegOS can change the semantics of C its cleverer than I thought ... :-) Cheers, Ben. -- (URL) grandfather once told me that there are two kinds of people: those who work and those who (...) (25 years ago, 3-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | case statement doesn't work- any clue?
|
|
I'm trying to program some very rudimentary debugging stuff- just outputting variables to the screen. Basically, I want to use a switch/case statement to read an integer variable (in this case ID_number) which is then linked (by the case statement) (...) (25 years ago, 3-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Lego Network Protocol questions
|
|
(...) Oops, I must've just caught the tail end of the conversation. I assumed the standard [lame] lego protocol was being discussed, not a custom protocol. Sorry. Dave (25 years ago, 2-May-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | RE: Lego Network Protocol questions
|
|
With all of the talk about networking and IP embedding and such, and since I'm working on a proprietary '485 master/slave protocol for a client, I had to dust off a GREAT university text on networks. It devotes an entire chapter to ALOHA and slotted (...) (25 years ago, 1-May-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: Lego Network Protocol questions
|
|
(...) Dave, did you catch the crosspost from lugnet.robotics.rcx.legos? I think there were details discussed there that may or may not have amounted to a fairly specific proposal for a protocol for LegOS. Anybody care to summarize whatever was (...) (25 years ago, 1-May-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: Lego Network Protocol questions
|
|
(...) Transmit whenever you feel like it and hope you didn't obliterate data coming from the other direction. Rudimentary, but still quite effective given the typical use pattern with is host driven command/response. With RCX to RCX communication (...) (25 years ago, 30-Apr-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Lego Network Protocol questions
|
|
Hi all. I came to the discussions on the LNP a bit late and was wondering if the following questions had been discussed (I flipped through an old Communications course book and noted some thoughts): - Can we do Carrier Sense *whilst* we are (...) (25 years ago, 30-Apr-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: IS free()'s operation atomic?
|
|
(...) I agree, free() is not ISR safe. One thread can get preempted after the check but before the store, and a second thread can adjust mm_first_free, making the first thread's check invalid. -Kekoa (25 years ago, 29-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | IS free()'s operation atomic?
|
|
Hi all I think that free() operation in mm.c is not ISR safe in multitasking mode. This operation is not keep coherence about value of mm_first_free,is it? ---...--- in mm.c ---...--- // for task safe operations, free needs to be // atomic and (...) (25 years ago, 29-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Rom sensor read routine
|
|
In writing some sensor code yesterday/today (it's 6 am), I passed over the ROM sensor code at 14c0. The documentation has been put in the usual place. The rotation code is pretty simple: the expected state machine, with split points between the four (...) (25 years ago, 25-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) given (...) lego (...) [ stuff about lego/native collisions ] (...) of a (...) on (...) I was wondering, since people are considering using tags in the LNP frame to signify local to local messages, could we not also use this to "label" non (...) (25 years ago, 23-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) In my brief experimentation with rom_reset(), it does not actually clear the rom- rather it only starts the program over again (in main()). Is this intentional? I get this behavior when calling it from main- when calling it from within another (...) (25 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found
|
|
(...) This seems the best approach to me too. My problem is I don't know if I am able to do such a thing :-) (...) I know your site and know you've done a LOT of hard work to understand and explain both RCX hardware and original firmware code. Mario (25 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) That's what I am doing. Markus. (25 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) Hmm.. with a little hacking you could certainly detect logic errors. The main problem I think would be writing alternative C-Functions for the H8 assembler, which makes up legOS itself. You'd also need to create a simulator engine for legOS to (...) (25 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
