element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Software Application Development Linux Boot Crashes on MicroZed
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 4 replies
  • Subscribers 328 subscribers
  • Views 383 views
  • Users 0 members are here
Related

Linux Boot Crashes on MicroZed

Former Member
Former Member over 11 years ago

When I use the uImage and uramdisk.image.gz provide from "MicroZed Linux microSD Card Image Archive" I can boot. But if I clone from the Xilinx git repo and build:
...
make ARCH=arm CROSS_COMPILE=arm-xilinx-linux-gnueabi- xilinx_zynq_defconfig

make ARCH=arm CROSS_COMPILE=arm-xilinx-linux-gnueabi- UIMAGE_LOADADDR=0x8000 uImage
...
Whether I use the dts generated from SDK or the one provided (not much difference) I get:

...
smp_twd: clock not found -2
ERROR: timer input clock not found
------------[ cut here ]------------
Kernel BUG at c0570b6c [verbose debug info unavailable]
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
Modules linked in:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.10.0-xilinx-15024-gefc2750 #1
task: c058f408 ti: c0584000 task.ti: c0584000
PC is at ttc_timer_init+0x4c/0x38c
LR is at ttc_timer_init+0x4c/0x38c
pc : [<c0570b6c>]    lr : [<c0570b6c>]    psr: 200001d3
sp : c0585f78  ip : 00000000  fp : 00000000
r10: 0000002b  r9 : 413fc090  r8 : c0df5afc
r7 : c057aad0  r6 : f0004000  r5 : c0585fac  r4 : fffffffe
r3 : 600001d3  r2 : 00000001  r1 : 600001d3  r0 : 00000022
Flags: nzCv  IRQs off  FIQs off  Mode SVC_32  ISA ARM  Segment kernel
Control: 18c5387d  Table: 0000404a  DAC: 00000015
Process swapper/0 (pid: 0, stack limit = 0xc0584238)
Stack: (0xc0585f78 to 0xc0586000)
5f60:                                                       c0df5afc a00001d3
5f80: 00000001 c0df5afc c0585fac ffffffff c057aad0 c0df6000 413fc090 00000000
5fa0: 00000000 c0570a5c 00000000 c057fc9c 00000001 c0584000 c05c1640 c055bd98
5fc0: 00000000 c05586c4 ffffffff ffffffff c05582e4 00000000 00000000 c057aad0
5fe0: 18c5387d c058c3f4 c057aac8 c05901fc 0000406a 00008074 00000000 00000000
[<c0570b6c>] (ttc_timer_init+0x4c/0x38c) from [<c0570a5c>] (clocksource_of_init+0x20/0x44)
[<c0570a5c>] (clocksource_of_init+0x20/0x44) from [<c055bd98>] (time_init+0x1c/0x30)
[<c055bd98>] (time_init+0x1c/0x30) from [<c05586c4>] (start_kernel+0x1b8/0x300)
[<c05586c4>] (start_kernel+0x1b8/0x300) from [<00008074>] (0x8074)
Code: e250a000 1a000002 e59f02fc ebf9a890 (e7f001f2)
---[ end trace 1b75b31a2719ed1c ]---
Kernel panic - not syncing: Attempted to kill the idle task!

...
Is there a way to get a patch from the repo by the zed developers?

  • Sign in to reply
  • Cancel
Parents
  • Former Member
    0 Former Member over 11 years ago

    Previous fix leads to kernal panic after a few hours.

    Below is the entire ethernet description that seems to work fine.

    ttps7-ethernet@e000b000 {
    ttt#address-cells = <0x1>;
    ttt#size-cells = <0x0>;
    tttcompatible = "xlnx,ps7-ethernet-1.00.a";
    tttinterrupt-parent = <0x2>;
    tttinterrupts = <0x0 0x16 0x4>;
    tttlocal-mac-address = [00 0a 35 00 00 00];
    tttphy-handle = <0x4>;
    tttphy-mode = "rgmii-id";
    tttreg = <0xe000b000 0x1000>;
                            xlnx,enet-clk-freq-hz = <0x7735940>;
    tttxlnx,enet-reset = <0xffffffff>;
    tttxlnx,enet-slcr-1000mbps-div0 = <0x8>;
    tttxlnx,enet-slcr-1000mbps-div1 = <0x1>;
    tttxlnx,enet-slcr-100mbps-div0 = <0x8>;
    tttxlnx,enet-slcr-100mbps-div1 = <0x5>;
    tttxlnx,enet-slcr-10mbps-div0 = <0x8>;
    tttxlnx,enet-slcr-10mbps-div1 = <0x32>;
    tttclock-names = "ref_clk", "aper_clk";
    tttclocks = <0x3 0xd 0x3 0x1e>;
    tttxlnx,eth-mode = <0x1>;
    tttxlnx,has-mdio = <0x1>;
    tttxlnx,ptp-enet-clock = <0x69f6bcb>;
    tttmdio {
    tttt#address-cells = <0x1>;
    tttt#size-cells = <0x0>;

    ttttphy@0 {
    tttttcompatible = "marvell,88e1510";
    tttttdevice_type = "ethernet-phy";
    tttttreg = <0x0>;
    tttttmarvell,reg-init = <0x3 0x10 0xff00 0x1e 0x3 0x11 0xfff0 0xa>;
    tttttlinux,phandle = <0x4>;
    tttttphandle = <0x4>;
    tttt};
    ttt};

    tt};

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • Former Member
    0 Former Member over 11 years ago

    Previous fix leads to kernal panic after a few hours.

    Below is the entire ethernet description that seems to work fine.

    ttps7-ethernet@e000b000 {
    ttt#address-cells = <0x1>;
    ttt#size-cells = <0x0>;
    tttcompatible = "xlnx,ps7-ethernet-1.00.a";
    tttinterrupt-parent = <0x2>;
    tttinterrupts = <0x0 0x16 0x4>;
    tttlocal-mac-address = [00 0a 35 00 00 00];
    tttphy-handle = <0x4>;
    tttphy-mode = "rgmii-id";
    tttreg = <0xe000b000 0x1000>;
                            xlnx,enet-clk-freq-hz = <0x7735940>;
    tttxlnx,enet-reset = <0xffffffff>;
    tttxlnx,enet-slcr-1000mbps-div0 = <0x8>;
    tttxlnx,enet-slcr-1000mbps-div1 = <0x1>;
    tttxlnx,enet-slcr-100mbps-div0 = <0x8>;
    tttxlnx,enet-slcr-100mbps-div1 = <0x5>;
    tttxlnx,enet-slcr-10mbps-div0 = <0x8>;
    tttxlnx,enet-slcr-10mbps-div1 = <0x32>;
    tttclock-names = "ref_clk", "aper_clk";
    tttclocks = <0x3 0xd 0x3 0x1e>;
    tttxlnx,eth-mode = <0x1>;
    tttxlnx,has-mdio = <0x1>;
    tttxlnx,ptp-enet-clock = <0x69f6bcb>;
    tttmdio {
    tttt#address-cells = <0x1>;
    tttt#size-cells = <0x0>;

    ttttphy@0 {
    tttttcompatible = "marvell,88e1510";
    tttttdevice_type = "ethernet-phy";
    tttttreg = <0x0>;
    tttttmarvell,reg-init = <0x3 0x10 0xff00 0x1e 0x3 0x11 0xfff0 0xa>;
    tttttlinux,phandle = <0x4>;
    tttttphandle = <0x4>;
    tttt};
    ttt};

    tt};

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube