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