rwarner wrote: > Martin Euredjian wrote: > >Why would one choose one over the other? > > > There is another option versus the ones above. I wrote my own as U-Boot > above appeared 'heavier-weight' then what is needed. Though i may have > missed something in the requirements of uCLinux start up. > 1. Initialize and provide access to RAM/ROM and peripherals > A. change PLL > B. change chip select registers for RAM/ROM > C. setup AIC > D. setup WDT as necessary > E. ensure other peripherals are in a quiescent state > 2. jump to 'stext'
That's good for a first stage bootloader. You might use it in a rolled out system where you only update to tested firmware, or when you have pins on the board to easily reflash it. Often it's useful to have a second stage with options to trap on a diagnostic serial port, present a prompt, boot an alternative kernel, read a file from the network and write it to flash, etc. Sometimes the second stage can be a small Linux kernel :-) -- Jamie _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
