Greetings,

We are trying to do something simliar here, only the hardware we are trying
to get NetBSD/arm32 to run on is not quite an ebsa-285, but our own
hardware.  I am currently writing the firmware to load this kernel.  What
we are doing is loading an s-record over the serial port into RAM, and then
page aliging the various sections down at 0.  There are other entry conditions
that the kernel expects, which can be found in the initarm() routine in
ebsa285_machdep.c.  These conditions can be changed in there to match what
your firmware does.

Currently, I am having trouble enabling the MMU on our board.  The CPU
seems to hang everytime.  What are the exact steps for enabling the MMU
on the StrongARM, does anyone know?  I build my section table right before
attempting to enable it, and I am making sure the place I am running from
will be mapped the same once the MMU is on.  If I could get by this, I could
attempt to jump to the kernel entry point and begin to debug the kernel!
Any help is appreciated!  Thanks!

--
Kyle Mestery
StorageTek's Storage Networking Group


On Thu, 1 Oct 1998, Kazuki Sakamoto wrote:

> Hi,
> 
> I am trying to run the NetBSD-current(Sep 19) EBSA285 kernel with
> Intel EBSA-285. The Kernel which I made by cross-compiling is
> the following condition.
> 
> % arm-netbsd-size -Ax netbsd
> netbsd  :
> section       size         addr
> .text   0x129000   0xeffff020
> .data     0xd000   0xf0129000
> .bss     0x1f9a8   0xf0136000
> Total   0x1559a8
> 
> I tried to read this kernel by using angelboot and ARM SDK 2.1.
> But, both angelboot and ARM SDK stop when it begins to send this kernel.
> I think that bootloader to read kernel and initialize(device, MMU, ...)
> is necessary.
> 
> Please let me know how to run NetBSD/arm32 with EBSA285.
> 
> Kazuki Sakamoto
> sakamoto@cec.co.jp
>