On Fri, 02 Apr 2010 17:08 +0200, "Paul de Weerd" <[email protected]> wrote:
> Your timeout idea is interesting. The bootloader loads the kernel > image and then starts executing it. After this, the bootloader is no > longer active, who will do this timing out ? The kernel (or the > garbage that was loaded in its place) is the only code running at > this point. Probably naive of me to think that the bootloader could get some sort of return code (0 = OK). Maybe it's too late for it to do anything at that point. I don't know the process well enough to talk intelligently about it, just curious. <snip> > You seem to have a valid issue, but a proper solution does not appear > to be obvious to me. I take it you don't have two machines under your > control in these remote locations so you could exchange serial console > between the two ? (a USB to serial adapter on one machine connected to > the serial port of the other and vice versa) I've done this a lot. Usually it works very well. Old, low-power hardware can be used that no longer has mush purpose. Brad
