I have this Integrator/AP development board here in my office:
Initialising Boot Monitor System Information Block boot Monitor > i ARM bootPROM [Version 1.3] Rebuilt on Jun 26 2001 at 22:04:10 Running on a Integrator Evaluation Board Board Revision V1.0, ARM920T Processor Memory Size is 128MBytes, Flash Size is 32MBytes Copyright (c) ARM Limited 1999 - 2001. All rights reserved. Board designed by ARM Limited Hardware support provided at http://www.arm.com/ For help on the available commands type ? or h boot Monitor >
Does anyone beside me *ever* try to actually boot a recent kernel on this thing?
How do you do it? Do I need patched U-boots etc, or can I just load a Z-record image of vmlinux into RAM over the serial console?
Needless to say, ARM Ltd. has deleted the web pages for official support of this thing as far as I can see. I was going to try out a few patches affecting mach-integrator...
Yours, Linus Walleij
On Mon, Mar 21, 2011 at 11:17:19AM +0100, Linus Walleij wrote:
Does anyone beside me *ever* try to actually boot a recent kernel on this thing?
How do you do it? Do I need patched U-boots etc, or can I just load a Z-record image of vmlinux into RAM over the serial console?
Needless to say, ARM Ltd. has deleted the web pages for official support of this thing as far as I can see. I was going to try out a few patches affecting mach-integrator...
That's going back quite a few years... and yes, it wasn't trivial. How it used to be done was with a boot loader called 'milo' which read the kernel out of flash - you had to program it and the kernel using 'afu' via the debugger.
Looking at the various scripts I have around, the other way I did it was using Angel (and presumably armsd). I have this .angelrc file:
device /dev/ttyS3 options "9600 8N1" baud 115200 base 0x00008000 entry 0x00008000 #otherfile ramdisk_img.gz #otherbase 0xc0800000 r0 0x00 r1 21 exec .start-minicom
and .start-minicom is: #!/bin/sh exec ~/bin/start-minicom int
Not sure if any of this helps, but might provide some hints.