On Nov 23, 2006, at 2:01 AM, Demke Torsten-atd012 wrote:

Hi Thoomas,

I see a similar problem when using of-tree. My debugging shows that the of-tree address given to the kernel is outside the memory region that can be accessed by the kernel at start-up (defined by CFG_BOOTMAPSZ), thus the kernel crashes very early without any output. (IMHO this is a bug.) If you are using CONFIG_OF_FLAT_TREE _and_ "disable_of" ist likely that you see the same behaviour, because in that case the "bootm" code still uses the of-tree address (char *of_flat_tree), after copying the standard bd_info data to that address. You could check the pointer that is given to the kernel for the board info data (line 967, parameter 1 of (*kernel) (...)) (or change (*kernel) ((bd_t *)of_flat_tree,... to (*kernel) (kbd,...)

Regards, Torsten

This seems like a bug.

Looking at the code I'm confused how this works at all. I dont see of_flat_tree getting setting to anything at all.

Can you guys try out Grant's patch "[PATCH] Allow CONFIG_OF_FLAT_TREE to boot a non-arch/powerpc kernel" and see if that fixes the issue when building w/CONFIG_OF_FLAT_TREE enabled. His patch should make it so that a bootm w/1 or 2 args that aren't a multiimage should boot arch/ppc style.

- k

...

-----Original Message----- From: u-boot-users-bounces@lists.sourceforge.net [mailto:u-boot-users-bounces@lists.sourceforge.net] On Behalf Of Thomas Schafer Sent: Mittwoch, 22. November 2006 19:56 To: u-boot-users@lists.sourceforge.net Subject: [U-Boot-Users] Booting ELDK 4.0 kernel on MPC8548CDS

Hi,

I'm using a MPC8548CDS eval system with u-boot 1.1.6 running on it. When trying to boot an ELDK 4.0 kernel, the board hangs immediately after decompression of the kernel. I've set the disable_of environment variable to avoid usage of the flat device tree.

The same kernel boots properly when using u-boot 1.1.3 which is delivered with the eval system.

Any hints would be appreciated.

Best regards,

Thomas Schafer

---

Kontron Modular Computers GmbH

Heinrich-Barth-Str. 1a 66115 Saarbrucken

Tel.: + 49 (0)681 / 95916 - 203 Fax: + 49 (0)681 / 95916 - 100 E-mail: thomas.schaefer@kontron.com

---

---

Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge

&CID=DEVDEV

...

---

U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

---

---

Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php? page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

Wolfgang,

Can you pickup and push Grant's patch "[PATCH] Allow CONFIG_OF_FLAT_TREE to boot a non-arch/powerpc kernel". It fixes an obvious bug with trying to boot use the old style boot mechanism that got broken with the mass of flat device tree patches.

- k

On Nov 23, 2006, at 1:38 PM, Dan wrote:

Kumar Gala wrote:

[snip]

...

Can you guys try out Grant's patch "[PATCH] Allow CONFIG_OF_FLAT_TREE to boot a non-arch/powerpc kernel" and see if that fixes the issue when building w/CONFIG_OF_FLAT_TREE enabled. His patch should make it so that a bootm w/1 or 2 args that aren't a multiimage should boot arch/ppc style.

• k

I was having a similar problem on my MPC8555CDS, this patch fixes the problem for me as well.

I was also having a problem with ethernet on this board. The TSEC driver in u-boot 1.1.6 seems to be broken (for this board anyway). I moved the PHY reset a bit earlier and it fixed it for me. I'll submit a patch in a moment.

cheers, Dan