 | | Re: loading s/w —Kekoa Proudfoot
|
| | | (...) I belive LegOS breaks firmware deletion, in the sense that the "delete firmware" opcode is not supported by the IR routines, but I could be wrong about that. If you are using an AC adapter and no batteries, the easiest thing to do is to turn (...) (26 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
|
| | | |
| | | | | Re: loading s/w —Kekoa Proudfoot
|
| | | | | (...) I skipped something here. The assumption I made is that you want to load new custom firmware. If you want to load the Lego firmware, find the Firm0309.lgo file in your Mindstorms directory, and load that into the RCX exactly as you would (...) (26 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
|
| | | | | |
| | | | | | | Re: loading s/w —Richard Franks
|
| | | | | | (...) legOS has a software solution built-in - when you are ready to quit, hold down the on/off button and press the 'prog' button. Hope this helps! Cheers, Richard (26 years ago, 9-Apr-99, to lugnet.robotics.rcx.legos)
|
| | | | | | |
| | | | | Re: loading s/w —Markus L. Noga
|
| | | | (...) 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 —Lou Sortman
|
| | | | (...) 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 —Markus L. Noga
|
| | | | | (...) 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 —Kekoa Proudfoot
|
| | | | | | (...) 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 —Markus L. Noga
|
| | | | | | (...) That's what I am doing. Markus. (26 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| | | | | | |
| | | | | | Re: loading s/w —Luis Villa
|
| | | | (...) 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)
|
| | | | |
