On Oct 1, 2005, at 1:57 AM, Kalle Pokki wrote:
> Yes I'm sure the code in Linux is right. It may be missing some
> initialisation it depends on, but anyway.
Did you mention in the past you have a custom boot loader? Is this
something
other than the PlanetCore boot rom?
> My board is an Embedded Planet EP8248 that came with a pre-installed
> version of Linux 2.4. That version works ok, though I don't know what
> modifications were made to the kernel. The source wasn't included...
I doubt they made any modifications to the generic driver. The only
thing
they may have done is added some board control register/GPIO to enable
the RS-232 transceiver. If you don't have their board initialization
functions,
though, this would be useful.
> Currently I boot with PlanetCore, load my own boot loader (I'm going
> to use it exclusively when my own custom board based on 8247 comes
> out) via tftp, and start the most recent kernel.org kenel from it.
What about just trying to boot the new kernel from PlanetCore boot rom?
Of course, if you are doing your own boot rom and have a board to bring
up,
you should have invested in something like a BDI2000 long ago because
it will
have paid for itself many times over by the time you are done :-) It
would have
also allowed you to debug this problem rather quickly.
You are going to have to investigate your processor state prior to
calling
Linux (HIDx registers, cache and MMU state, SIU configuration, etc) to
see
how it differs from what PlanetCore does. There are lots and lots of
options
on these processors, and one bit in one configuration register that is
incorrect can cause lots of grief.
-- Dan
