[meta-xilinx] kernel resetting at boot

[Edward Vidal]

Hello All,
Thanks for the help I was able to boot kernel using

BOOT.BIN
U-Boot 2013.07 (Jan 29 2014 - 10:07:38)

uImage--3.10-xilinx+gitefc27505715e64526653f35274717c0fc56491e3-r1-zedboard-zynq7-20140130012558.bin
--> uImage

core-image-minimal-zedboard-zynq7-20140130151638.rootfs.ext2.gz.u-boot -->
uramdisk.image.gz

uImage--3.10-xilinx+gitefc27505715e64526653f35274717c0fc56491e3-r1-zedboard-zynq7-ram-20140130012558.dtb
--> devicetree.dtb

Linux zedboard-zynq7 3.10.0-xilinx #1 SMP PREEMPT Wed Jan 29 18:28:34 MST
2014 a
rmv7l GNU/Linux
root at zedboard-zynq7:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                 8059      4795      2855  63% /
devtmpfs                247496         0    247496   0% /dev
tmpfs                   256880        32    256848   0% /run
tmpfs                   256880        28    256852   0% /var/volatile
Thanks again
Ed Vidal


On Wed, Jan 29, 2014 at 6:08 PM, Sipke Vriend <sipke.vriend at xilinx.com>wrote:

> Hi Edward,
>
> It looks like the u-boot you build is ok, but there is also a dedicated
> recipe for the 2013.07 version
> meta-xilinx/recipes-bsp/u-boot/u-boot-xlnx_2013.07.bb
> You can enable it simply by specifying only
> PREFERRED_VERSION_u-boot-xlnx ?= "v2013.07%"
> in your local.conf.
> So I would use that, unless you specifically want to build the latest on
> master
> of https://github.com/Xilinx/u-boot-xlnx, as the master branch
> might shift on you at any time.
>
> I think your problem might be related to the u-boot log entry
> > ** Unable to read file uramdisk.image.gz **
> I could not see any manual steps to load an alternative rootfs image.
>
> Did you remember to copy the ramdisk from the deploy/images directory?
> If not, that could be the issue. If you did it might be the wrong type or
> corrupt?
> From meta-xilinx/docs/BOOT.sdcard
> " RootFS: uramdisk.image.gz (core-image-minimal-<machine
> name>.ext2.gz.u-boot)"
> That's the one you need.
>
> Hope that helps.
> Cheers
> Sipke
>
> On 30/01/2014 3:54 AM, Edward Vidal wrote:
> > hello all,
> >
> > I just cloned poky and meta-xilinx.  Testing branch dora
> > added the following to my local.conf
> >
> > UBOOT_XLNX_DEV_BRANCH ?= "master"
> > PREFERRED_VERSION_u-boot-xlnx ?= "${UBOOT_XLNX_DEV_BRANCH}"
> >
> > The above 2 lines were needed to build a v2013.07 is that correct?
> >
> > MACHINE ?= "zedboard-zynq7"
> >
> > I built bitbake u-boot-xlnx and bitbake virtual/kernel
> > Generated a new BOOT.BIN
> > U-Boot 2013.07 (Jan 29 2014 - 10:07:38)
> >
> > Memory: ECC disabled
> > DRAM:  512 MiB
> > WARNING: Caches not enabled
> > MMC:   zynq_sdhci: 0
> > SF: Detected S25FL256S_64K with page size 64 KiB, total 32 MiB
> > *** Warning - bad CRC, using default environment
> >
> > In:    serial
> > Out:   serial
> > Err:   serial
> > Net:   Gem.e000b000
> > Hit any key to stop autoboot:  3  2  1  0
> > Device: zynq_sdhci
> > Manufacturer ID: 2
> > OEM: 544d
> > Name: SA32G
> > Tran Speed: 50000000
> > Rd Block Len: 512
> > SD version 3.0
> > High Capacity: Yes
> > Capacity: 29.3 GiB
> > Bus Width: 4-bit
> > reading uEnv.txt
> > 100 bytes read in 10 ms (9.8 KiB/s)
> > Loaded environment from uEnv.txt
> > Importing environment from SD ...
> > Copying Linux from SD to RAM...
> > reading uImage
> > 2858824 bytes read in 447 ms (6.1 MiB/s)
> > reading devicetree.dtb
> > 23080 bytes read in 20 ms (1.1 MiB/s)
> > reading uramdisk.image.gz
> > ** Unable to read file uramdisk.image.gz **
> > At the prompt  I enter the following 3 lines
> > fatload mmc 0 0x2A00000 devicetree.dtb
> > reading devicetree.dtb
> > 23080 bytes read in 21 ms (1 MiB/s)
> > zynq-uboot> fatload mmc 0 0x00008000 uImage
> > reading uImage
> > 2858824 bytes read in 445 ms (6.1 MiB/s)
> > zynq-uboot> boot, m 0x00008000 - 0x2A00000
> >
> > ## Booting kernel from Legacy Image at 00008000 ...
> >    Image Name:   Linux-3.8.11-xilinx
> >    Image Type:   ARM Linux Kernel Image (uncompressed)
> >    Data Size:    2858760 Bytes = 2.7 MiB
> >    Load Address: 00008000
> >    Entry Point:  00008000
> >    Verifying Checksum ... OK
> > ## Flattened Device Tree blob at 02a00000
> >    Booting using the fdt blob at 0x2a00000
> >    XIP Kernel Image ... OK
> >    Loading Device Tree to 1fb4c000, end 1fb54a27 ... OK
> >
> > Starting kernel ...
> >
> > data abort
> >     MAYBE you should read doc/README.arm-unaligned-accesses
> >
> > pc : [<1ff7624c>]   lr : [<1ff777d0>]
> > sp : 3ffffffc  ip : 00000000 fp : 00020205
> > r10: 1ffaeaf0  r9 : ae742afa r8 : 00800000
> > r7 : 00000000  r6 : 00008000 r5 : 1ffaeaf0  r4 : 00000000
> > r3 : 00005a28  r2 : 1fb4c000 r1 : baefa2ee  r0 : 11acb1b4
> > Flags: nzcv  IRQs on  FIQs on  Mode SVC_32
> > Resetting CPU ...
> >
> > resetting ...
> > Thanks
> >
> >
> > _______________________________________________
> > meta-xilinx mailing list
> > meta-xilinx at yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-xilinx
> >
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20140130/a30cfb2f/attachment.html>