[meta-xilinx] meta-zynq

[Mike Looijmans]

Rather than just removing the things that seem to fail, you might want to take 
a look at the output and determine why they failed.

Bluntly removing "fpga-image" from the image will leave the PL unprogrammed. 
Imagine what happens when the drivers that NEED that logic (e.g. HDMI, audio) 
load and start probing on the AXI bus.

 From your logging, I gather that you did not make it that far, though. You 
are booting something completely different , e.g. there should be no ramdisk 
involved...


On 01/15/2014 02:16 PM, Edward Vidal wrote:
> Hello all,
> Following the direction in README and some
> These were errors that I was getting with fpga-image in my-image.bb
> <http://my-image.bb>
> ERROR: Function failed: do_compile (log file is located at
> /home/vidal/POKY/zynq_oe/build/tmp-eglibc/work/zedboard-oe-linux-gnueabi/fpga-image/5.AUTOINC-0a90b0d42e-r0/temp/log.do_compile.6643)
> ERROR: Logfile of failure stored in:
> /home/vidal/POKY/zynq_oe/build/tmp-eglibc/work/zedboard-oe-linux-gnueabi/fpga-image/5.AUTOINC-0a90b0d42e-r0/temp/log.do_compile.6643
> ERROR: Task 364
> (/home/vidal/POKY/zynq_oe/meta-zynq/recipes-bsp/fpga/fpga-image.bb
> <http://fpga-image.bb>, do_compile) failed with exit code '1'
>
> After removing fpga-image from my-image.bb <http://my-image.bb> creating a new
> patch file for u-boot-zynq and changing some md5sum in some recipes the
> command MACHINE=zedboard bitbake my-image generated the files to boot my
> zedboard.  BOOT.bin, autorun.scr, uImage, uImage-zynq-zed-adv7511.dtb (to
> devicetree.dtb) which were transferred to vfat partition. The file
> my-image-zedboard.rootfs.tar.gz was extracted on an ext4 partition.
> U-Boot 2013.07 (Jan 14 2014 - 18:54:23)
>
> 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
> **********************************************************
> I see that now the autorun.scr appears to be running.
> **********************************************************
> Rd Block Len: 512
> SD version 3.0
> High Capacity: Yes
> Capacity: 29.3 GiB
> Bus Width: 4-bit
> reading uImage
> 3121600 bytes read in 483 ms (6.2 MiB/s)
> reading devicetree.dtb
> 10562 bytes read in 19 ms (542 KiB/s)
> reading uramdisk.image.gz
> ** Unable to read file uramdisk.image.gz **
> ***********************************************************
> zynq-uboot> fatload mmc 0 0x00008000 uImage
> reading uImage
> 3121600 bytes read in 484 ms (6.2 MiB/s)
> zynq-uboot> fatload mmc 0 0x2A00000 devicetree.dtb
> reading devicetree.dtb
> 10562 bytes read in 19 ms (542 KiB/s)
> zynq-uboot> bootm 0x00008000 - 0x2A00000
> ## Booting kernel from Legacy Image at 00008000 ...
>     Image Name:   Linux-3.12.0
>     Image Type:   ARM Linux Kernel Image (uncompressed)
>     Data Size:    3121536 Bytes = 3 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 1fb5f000, end 1fb64941 ... OK
>
> Starting kernel ...
>
> undefined instruction
> pc : [<0000800c>]   lr : [<1ff777cc>]
> sp : 1fb65d70  ip : 00000000 fp : 00000000
> r10: 1ffae978  r9 : 00000000 r8 : 1fb65f48
> r7 : 00000000  r6 : 00008000 r5 : 1ffae978  r4 : 00000000
> r3 : 00002942  r2 : 1fb5f000 r1 : baefa2ee  r0 : 446b2c6d
> Flags: nZCv  IRQs off  FIQs off  Mode SVC_32
> Resetting CPU ...
>
> resetting ...
>
> All of my results are at https://github.com/develone/meta-zynq.git or
> git at github.com:develone/meta-zynq.git  on the kernel-3.12 branch.  I have my
> local.conf bblayers.conf a file which explains my chg test_looijmans_layer.txt
> and boot.txt. Any and help is appreciated
> Thanks
>
>
>
>
>
>
> 

Met vriendelijke groet / kind regards,

Mike Looijmans

TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) – (0)499 - 33.69.79
Telefax: (+31) - (0)499 - 33.69.70
E-mail: mike.looijmans at topic.nl
Website: www.topic.nl

Dit e-mail bericht en de eventueel daarbij behorende bijlagen zijn uitsluitend bestemd voor de geadresseerde, zoals die blijkt uit het e-mail bericht en/of de bijlagen. Er kunnen gegevens met betrekking tot een derde instaan. Indien u als niet-geadresseerde dit bericht en de bijlagen ontvangt, terwijl u niet bevoegd of gemachtigd bent om dit bericht namens de geadresseerde te ontvangen, wordt u verzocht de afzender hierover direct te informeren en het e-mail bericht met de bijlagen te vernietigen. Ieder gebruik van de inhoud van het e-mail bericht, waaronder de daarbij behorende bijlagen, door een ander dan de geadresseerde is onrechtmatig jegens ons dan wel de eventueel in het e-mail bericht of de bijlagen voorkomende andere personen. TOPIC Embedded Systems is niet aansprakelijk voor enigerlei schade voortvloeiend uit het gebruik en/of acceptatie van dit e-mail bericht of de daarbij behorende bijlagen.

The contents of this message, as well as any enclosures, are addressed personally to, and thus solely intended for the addressee. They may contain information regarding a third party. A recipient who is neither the addressee, nor empowered to receive this message on behalf of the addressee, is kindly requested to immediately inform the sender of receipt, and to destroy the message and the enclosures. Any use of the contents of this message and/or the enclosures by any other person than the addressee or person who is empowered to receive this message, is illegal towards the sender and/or the aforementioned third party. TOPIC Embedded Systems is not  liable for any damage as a result of the use and/or acceptance of this message and as well as any enclosures.
_______________________________________________
> meta-xilinx mailing list
> meta-xilinx at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx
>