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 Device Tree fo Zynq 2014.4 (Linux 3.17)
  • 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 1 reply
  • Subscribers 328 subscribers
  • Views 158 views
  • Users 0 members are here
Related

Device Tree fo Zynq 2014.4 (Linux 3.17)

Former Member
Former Member over 10 years ago

Is there a "known good" device tree compatible with the current Zynq release?  As of 2014.4 they are using Linux 3.17.  The device tree needed for this is very different than the device tree for Linux 3.8 that ships with my MicroZed.

I have things mostly working, but I do have odd issues like my clock seeming to drift a lot.  This makes me wonder if there are settings that I'm missing or have slightly wrong.  Unfortunately, the device tree generator is not good enough to create a fully working tree, and I'm not confident where I need to tweak.

For example, the generator gives lines like:

     operating-points = <666667 1000000 333334 1000000 222223 1000000>;

and the factory provided device tree has lines like:

     xlnx,cpu-1x-clk-freq-hz = <0x69f6bcb>;
     xlnx,cpu-clk-freq-hz = <0x27bc86bf>;

These seem related, yet different.  There are lots of other differences and it hard to sort out which ones matter and which ones are correct.

  • Sign in to reply
  • Cancel
Parents
  • zedhed
    0 zedhed over 10 years ago

    Hi asigint,

    I suggest using the ZedBoard devicetree from the Xilinx 2014.4 release as the starting point.

    http://www.wiki.xilinx.com/Zynq+2014.4+Release

    I tried this on my end and so far this is working well for me.  There were two entries that I found which needed to be modified.

    The first is the memory entry which needs to be expanded to cover the 1GB RAM available on MicroZed:

    memory@0 {
      device_type = "memory";
      reg = < 0x0 0x40000000 >;
    };

    The second entry which needs some attention is the Ethernet phy entry which needs the reg-init string added:

    phy@0 {
      reg = <0x0>;
      marvel,reg-init = <3 16 0xff00 0x1e 3 17 0xfff0 0x00>;
      linux,phandle = <0x4>;
      phandle = <0x4>;
    };

    <EDIT>Although now that I look at it closer, that reg-init string does not appear to have any affect on the Linux kernel that is part of the official Xilinx 2014.4 release so you can probably safely ignore that.</EDIT>

    As for those entry differences that are hard to sort out, I agree that they are confusing but if you focus on the other device entries that are known to be different between boards then that should get you moving forward.

    Regards,

    -Kevin

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • zedhed
    0 zedhed over 10 years ago

    Hi asigint,

    I suggest using the ZedBoard devicetree from the Xilinx 2014.4 release as the starting point.

    http://www.wiki.xilinx.com/Zynq+2014.4+Release

    I tried this on my end and so far this is working well for me.  There were two entries that I found which needed to be modified.

    The first is the memory entry which needs to be expanded to cover the 1GB RAM available on MicroZed:

    memory@0 {
      device_type = "memory";
      reg = < 0x0 0x40000000 >;
    };

    The second entry which needs some attention is the Ethernet phy entry which needs the reg-init string added:

    phy@0 {
      reg = <0x0>;
      marvel,reg-init = <3 16 0xff00 0x1e 3 17 0xfff0 0x00>;
      linux,phandle = <0x4>;
      phandle = <0x4>;
    };

    <EDIT>Although now that I look at it closer, that reg-init string does not appear to have any affect on the Linux kernel that is part of the official Xilinx 2014.4 release so you can probably safely ignore that.</EDIT>

    As for those entry differences that are hard to sort out, I agree that they are confusing but if you focus on the other device entries that are known to be different between boards then that should get you moving forward.

    Regards,

    -Kevin

    • 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