Problem porting 2.4.17 linux to MPC8260ADS

[Dan Malek]

Kamalesh B wrote:

> Iam porting Linux 2.4.17 on MPC8260ADS. I had already working
> Linux-2.4.1 version on MPC8260ADS board.

There should be very minimal changes required to support the 8260ADS,
just a few memory mapping initializations.  Everything else is generic
to all of the other 8260 boards that are supported.

> I had rather taken an tedious process of identifying the problem by
> glowing LEDs present on the board. I have identify the location of the
> problem.

Well....think about this for a moment......In order to flash the LEDs
you need access to the board control register.  Once you initialize
the MMU for Linux, these mappings are gone and you need to set them
up again within the Linux memory map.  There are several memory map
transistions during the start up of Linux.  Very early in the start
up code it enables the MMU and only maps a small portion of real
memory.  You won't be able to access LEDs after this point.

> I checked the value of cur_cpu_spec[0] pointer. It was zero.

How did you check this?  The processor is running with caches enabled,
this pointer is initialized during the start up.  If you dumped out
main memory after the crash, I doubt it was written out of the cache.

> I also tried commenting this line as this was not there in 2.4.1
> version. Here control went till this point in "head.S" code

Not a good idea.  There are subtle changes happening all of the time,
and the difference between 2.4.1 and 2.4.17 is quite a bit.

I suspect your access to the LEDs is crashing due to memory mapping
changes, and taking you down the wrong path.

As I said, there should be very minimal board specific changes
required.  A header file in arch/ppc/platforms, some updates to the
bootloader, ensure the IMMR is set to 0xf0000000 before calling the
kernel and you should have a console prompt.  If you want to access
other board control registers, they will have to be ioremapped()
somewhere in the kernel before you use them.



	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/