All of lore.kernel.org
 help / color / mirror / Atom feed
* Kernel hangs after "Loading Device Tree" after update
@ 2015-03-30 17:44 Albrecht Dreß
  0 siblings, 0 replies; only message in thread
From: Albrecht Dreß @ 2015-03-30 17:44 UTC (permalink / raw)
  To: linuxppc-dev

[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]

Hi all,

I have a strange problem on a self-developed MPC5200B system (more or less like the Freescale "Lite" board).  On that board, I use kernel 3.2.68 with my own machine init file, which is almost the same as for Lite (arch/powerpc/platforms/52xx/lite5200.c).  Everything works just fine.

When I use 3.18.9 with the same init file modifications and compiled with more or less the same .config, plus an adjusted DTB (e.g. rename the "fsl,mpc5200b-psc-uart" entries to "fsl,mpc5200b-psc"), the boot process from u-boot simply hangs after:

<snip>
## Booting kernel from Legacy Image at 01000000 ...
    Image Name:   Linux-3.18.9
    Created:      2015-03-30   7:23:52 UTC
    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
    Data Size:    1972101 Bytes =  1.9 MB
    Load Address: 00000000
    Entry Point:  00000000
    Verifying Checksum ... OK
## Flattened Device Tree blob at 01200000
    Booting using the fdt blob at 0x1200000
    Uncompressing Kernel Image ... OK
    Loading Device Tree to 007fa000, end 007ff2d9 ... OK
</snip>

Any idea what goes wrong here?  I recall that I used the same approach outlined above to move from 2.6.32 to 3.2, which worked immediately.  Might my U-Boot be too old (I use 2009.03)?

Thanks in advance,
Albrecht.

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2015-03-30 17:44 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-03-30 17:44 Kernel hangs after "Loading Device Tree" after update Albrecht Dreß

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.