>Dave Borja writes:
>> I posted a while ago about angleboot problems with our
>> ebsa110 type board. Turns out I was able to get it to work
>> by cutting down the size of the data packet sent for the image
>> download. This was hardcoded at 2016. Cutting it in half gets
>> the download to work.
>
>This sounds like a problem with something not being able to fragment
>packets on ethernet correctly.
>
>> Getting things to boot is another matter. I compiled a kernel
>> (based on 2.2.12) with arm and brutus/sa1100 patches. Tried
>> building with the ebsa110 option and with minimal support (basically
>> just the serial ports, ram disk as initd, etc). We plunk this down
>> into base address 0x8000 and put the ram disk up there in 0x00100000.
>> Since we only have 8mb of memory and the ram disk is a little over 6mb
>> uncompressed, things are tight.
>
>I hope you're using either the Image or zImage files? Also, a 6MB ramdisk
>in 8MB isn't really going to leave much room at all for the user-mode.
>Do you get any kernel messages from the serial port? (and you did
>specify "console=ttyS0,19200n8" or similar during the build? Also,
>check that r0 and r1 are being passed the correct values.
Well, we want this to behave similar to the brutus, w/the console coming out
of ttyS1 since the first serial port is being used by angelboot. And,
I assume r0 should be 0 and r1 should have index for the architecture?
In any case, thanks for the input, we are certainly having our troubles,
mostly due to
us all being low on the learning curve (we lost our main embedded
systems man who flew off to a job at intel)...
We are concentrating on just getting this to boot. We need to figure out how
to map the dram and i/o space since the map is different from the ebsa110 w/
our dram starting at 0x40000000.
The sa110 is on a 32 bit bus along with the dram & flash. There's a CPLD
chip that
buffers the 16 bit isa bus. On that we've got a Natioinal Semi super i/o
where we
hang the standard perpherials (serial ports, parallel port, ide, GPIO
lines). Also there
is a cs89000 ethernet chip on the bus as well as the eprom w/angel.
Most of this may be a matter of patching the include/asm-arm *.h files to
get
the IRQs and memory map correct.. But we need to do some initialization for
that
super i/o chip. From reading the discussion on the bios,it's not clear where
to put this
According to Philip, head-armv.S should remain as platform independend as
possible.
but this seems to be the only reasonable place to put this. Should this be
in the bios
instead? For now, we just want to get booted....
Thanks,
Dave Borja
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
