I found the issue in the devicetree, comparing my one with recent microzed 
board.
Nevertheless there is (at least) one thing, I don't understand.

in meta-xilinx/recipes-bsp/device-tree/files/common
there is zynq7-base.dtsi, which is not uses by all the devicetree files in this 
layer.

These are all using:
/include/ "zynq-7000.dtsi" - but this is not in .../common

Is this intentionally?

And it seems the number of Bogomips is only half of previous values (even after 
adding 2nd CPU)?

Regards
Arno


> Gesendet: Dienstag, 10. Januar 2017 um 08:31 Uhr
> Von: "Arno Steffens" <s...@gmx.li>
> An: meta-xilinx@yoctoproject.org
> Betreff: [meta-xilinx] xilinx 4.4 -> 4.6 kernel doesn't boot
>
> Keeping my previous system (yocto 2.1 uboot) I try to boot into recent 
> yocto2.2 (xilinx 4.6) kernel.
> It doesn't, last message is "Starting kernel ..."
> 
> I read that this has usually 2 reasons, mismatching bootcmd or MachineID.
> 
> I try to boot (working 4.4 kernel) with other machine id by setting in uboot
> "set machid 44".
> Although uboot confirmes this by :
> Using machid 0x44 from environment
> it boots. So I guess this might not the problem.
> 
> Found that indeed in devicetree something has been changed:
> 
> -             bootargs = "console=ttyPS0,115200 earlyprintk";
> +             bootargs = "";
> +             stdout-path = "serial0:115200n8";
> 
> So I changed this in my linux dts file, but result keeps same.
> I also try to modify my previous bootargs:
> 
> console=ttyPS0,115200 earlyprintk root=/dev/nfs nfsroot...
> 
> and omit the console and earlyprintk without an effect.
> 
> How can I debug this?
> 
> Best regards
> Arno
> 
> -- 
> _______________________________________________
> meta-xilinx mailing list
> meta-xilinx@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx
> 
-- 
_______________________________________________
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

Reply via email to