| Summary: | mpc8315e-rdb kernel of nightly build (20110121-1,Laverne release) boot failed | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Kernel | Reporter: | liang li <liang.li2> |
| Component: | kernel-tooling | Assignee: | Bruce Ashfield <bruce.ashfield> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Low | CC: | jiajun.xu, ke.yu, liangliang.wang, liming.wang, sgw, yi.zhao, yp.kernel.watcher, yp.watcher |
| Version: | 0.9 | ||
| Target Milestone: | 0.9.1 | ||
| Hardware: | mpc8315e-rdb | ||
| OS: | ppc | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
liang li
2011-01-28 01:57:29 UTC
the patch has been tested and passed on git master branch by liming,wang and bruce. thanks. Two questions: 1) which patch ? I sent a few on this in the background, but none of them should have been the fix. Since the loaddr on this boot implies that uImage from the kernel itself is not being used, but instead some of the poky constructed ones. Can someone compare the .bin being booted against the linux-fsl-mpc8315e-rdb-standard-build/arch/powerpc/boot/uImage ? Are they exactly the same size ? Is this a dtb or fdt based boot ? 2) can I see a dump of the uboot env ? (In reply to comment #2) > Two questions: > > 1) which patch ? I sent a few on this in the background, but none of > them should have been the fix. Since the loaddr on this boot implies > that uImage from the kernel itself is not being used, but instead some > of the poky constructed ones. > > Can someone compare the .bin being booted against the > linux-fsl-mpc8315e-rdb-standard-build/arch/powerpc/boot/uImage ? Are > they exactly the same size ? > > Is this a dtb or fdt based boot ? > > 2) can I see a dump of the uboot env ? Hi bruce, the method to solve this kernel problems (this is told by liming.wang): diff --git a/meta/conf/machine/mpc8315e-rdb.conf b/meta/conf/machine/mpc8315e-rdb.conf index e3f9d23..69f3dbe 100644 --- a/meta/conf/machine/mpc8315e-rdb.conf +++ b/meta/conf/machine/mpc8315e-rdb.conf @@ -14,3 +14,6 @@ MACHINE_FEATURES = "kernel26 keyboard pci ext2 ext3 serial" PREFERRED_PROVIDER_virtual/kernel = "linux-yocto" PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers-yocto" + +UBOOT_ENTRYPOINT = "0x00000000" + it is dtb based boot. liang li That is the fix that I sent Liming, but looking at the code it should have zero impact. UBOOT_ENTRYPOINT is only used on uImages that are created outside of the kernel build process. How are you building the dtb ? Manually ? I'm either going to have to run some experiments here (hence why I'm looking for the full boot instructions for what' you've done) or I'm going to need to get some debug code used in your build environment. So if you can enter your build & boot steps, I can start there. If that doesn't work, I'll get you to run some debug code that will show me why your uImage is being constructed incorrectly. (In reply to comment #4) > That is the fix that I sent Liming, but looking at the code it should > have zero impact. UBOOT_ENTRYPOINT is only used on uImages > that are created outside of the kernel build process. > > How are you building the dtb ? Manually ? dtb is given by Liming (not manually). > > I'm either going to have to run some experiments here (hence why I'm > looking for the full boot instructions for what' you've done) or I'm going > to need to get some debug code used in your build environment. > > So if you can enter your build & boot steps, I can start there. If that > doesn't work, I'll get you to run some debug code that will show me > why your uImage is being constructed incorrectly. steps: 1. set build env. 2. bitbake poky-image-minimal 3. from tmp/deploy/images get the uImage. build env : if you can ssh to the 128.224.158.136 (my machine) user : liangli passwd :3111llli2 dir: /home/liangli/poky-git-build_4 images: tmp/deploy/images (In reply to comment #5) > (In reply to comment #4) > > That is the fix that I sent Liming, but looking at the code it should > > have zero impact. UBOOT_ENTRYPOINT is only used on uImages > > that are created outside of the kernel build process. > > > > How are you building the dtb ? Manually ? > dtb is given by Liming (not manually). > > > > I'm either going to have to run some experiments here (hence why I'm > > looking for the full boot instructions for what' you've done) or I'm going > > to need to get some debug code used in your build environment. > > > > So if you can enter your build & boot steps, I can start there. If that > > doesn't work, I'll get you to run some debug code that will show me > > why your uImage is being constructed incorrectly. > steps: > 1. set build env. > 2. bitbake poky-image-minimal > 3. from tmp/deploy/images get the uImage. > build env : > if you can ssh to the 128.224.158.136 (my machine) > user : liangli > passwd :3111lli2 > dir: /home/liangli/poky-git-build_4 > images: tmp/deploy/images passwd :3111lli2 One last question .. the dtb. Where are you getting the dtb from ? (In reply to comment #7) > One last question .. the dtb. Where are you getting the dtb from ? It is given by Liming: server :pek-lpgbuild5 (128.224.153.35) file: /folk/lwang0/mpc8315erdb.dtb This hardware was not officially supported as part of 0.9, please move to 1.0 for tested and supported kernel with this hardware support. |