Actions
Forum Thread Details
  • State Not Answered
  • Replies 4 replies
  • Subscribers 358 subscribers
  • Views 395 views
  • Users 0 members are here
Related

compiling new kernel from xilinx master-next

hjo

I want to port the can4linux to the latest kernel tree. I downloaded and configured the kernel using:


make ARCH=arm clean
make ARCH=arm xilinx_zynq_defconfig
make ARCH=arm UIMAGE_LOADADDR=0x8000 uImage


the kernel compiles and loads from u-boot, but stops very early:

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x0
Linux version 3.10.0-xilinx-14840-g5ad0256-dirty (oe@heinz.site) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-49) ) #12 SMP PREEMPT Wed Aug 7 19:04:59 CEST 2013
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Generic DT based system, model: Xilinx Zedboard
bootconsole [earlycon0] enabled
cma: CMA: reserved 16 MiB at 1e800000
Memory policy: ECC disabled, Data cache writealloc


What can be the reason for stopping that early? I hope someone hast the answer.
Thanks.

   Heinz

  • 0

    Thanks to inpout from Xilinx I'm a step further.
    Kernel 3.10 ist starting up.
    I had to use the zynq-zed.dts. That was it.
    Now I'm stuck with the nest problem.

      xemacps e000b000.ps7-ethernet: eth0: no PHY found

    And I'm not bale to mount rootfs using NFS

    Heinz

  • 0 in reply to hjo

    solved this as well.

    I use ./arch/arm/boot/dts/zynq-zed.dts but changed the ethernet mdio section.
    Problem solved, kernel 3.10 runs now on my Zedboard.

  • 0 in reply to hjo

    It is good to know that it is possible to fix this problem that I have seen myself too. But this doesn't really fix my problem as I have no idea how. What exactly did you change in the ethernet mdio section of what file?

  • 0

    mdio {
                                    #address-cells = <1>;
                                    #size-cells = <0>;
                                    phy0: phy@0 {
                                            compatible = "marvell,88e1510";
                                            device_type = "ethernet-phy";
                                            reg = <0x0>;
                                            marvell,reg-init = <0x3 0x10 0xff00 0x1e 0x3 0x11 0xfff0 0xa>;
                                    } ;
                            } ;



    I hope this will do it for you.