 | | Re: loading s/w
|
| (...) rom_reset() does the trick, you'll need to #include "rom/system.h". I'm not sure wheter this is safe when multitasking. (26 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 (...) (26 years ago, 20-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 (...) (26 years ago, 20-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 (26 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
| | | | | Re: loading s/w
|
| (...) That's what I am doing. Markus. (26 years ago, 21-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 (...) (26 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
| |
