element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • 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
PicoZed Hardware Design Unable to read MTD from PicoZed linux
  • 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 Verified Answer
  • Replies 2 replies
  • Subscribers 305 subscribers
  • Views 808 views
  • Users 0 members are here
Related

Unable to read MTD from PicoZed linux

Former Member
Former Member over 10 years ago

Hello,

I have a Picozed 7020 on FMC carrier, and am unable to find any mtd devices in /proc/mtd when booting petalinux or custom linux.

I can, however, see mtd devices when booting from the kernel that is already on the qspi flash.

In my custom project in Vivado 2014.2, QSPI is enabled in the processing system IP and is set to use single 4 bit SS on MIO pins 1-6, and the feedback clock is enabled (on pin 8 I believe). The project was created using the Picozed + FMC board definition files.

Is it possible the QSPI core is not located at 0xe000d000? What am I missing?

Here is the DTS file I'm using for petalinux:

zynq-7000.dtsi:

ttqspi: spi@e000d000 {
tttclock-names = "ref_clk", "pclk";
tttclocks = <&clkc 10>, <&clkc 43>;
tttcompatible = "xlnx,zynq-qspi-1.0";
tttstatus = "disabled";
tttinterrupt-parent = <&intc>;
tttinterrupts = <0 19 4>;
tttreg = <0xe000d000 0x1000>;
ttt#address-cells = <1>;
ttt#size-cells = <0>;
tt};

excerpt from system-top.dts:


&qspi {
#address-cells = <1>;
#size-cells = <0>;
tflash0: flash@0 {
ttcompatible = "micron,n25q128";
ttreg = <0x0>;
t// spi-tx-bus-width = <1>;
t// spi-rx-bus-width = <4>;
ttspi-max-frequency = <50000000>;
tt#address-cells = <1>;
tt#size-cells = <1>;
ttpartition@qspi-fsbl-uboot {
tttlabel = "qspi-fsbl-uboot";
tttreg = <0x0 0x100000>;
tt};
ttpartition@qspi-linux {
tttlabel = "qspi-linux";
tttreg = <0x100000 0x500000>;
tt};
ttpartition@qspi-device-tree {
tttlabel = "qspi-device-tree";
tttreg = <0x600000 0x20000>;
tt};
ttpartition@qspi-rootfs {
tttlabel = "qspi-rootfs";
tttreg = <0x620000 0x5E0000>;
tt};
ttpartition@qspi-bitstream {
tttlabel = "qspi-bitstream";
tttreg = <0xC00000 0x400000>;
tt};
t};
};

  • Sign in to reply
  • Cancel

Top Replies

  • zedhed
    zedhed over 10 years ago +1 verified
    Hi jhemsing, We discovered the same thing and are working with Xilinx on resolving this. So far, adding the correct flash device entry to the DTS seems to fix everything. -----------------------------…
  • zedhed
    0 zedhed over 10 years ago

    Hi jhemsing,

    We discovered the same thing and are working with Xilinx on resolving this.

    So far, adding the correct flash device entry to the DTS seems to fix everything.

    ------------------------------------


    The 2014.4 QEMU has changed the qspi flashs ids list, it is more correct than 2014.2, You will need to add the correct flash ID to the system_top.dts.

    Please add this to the system-top.dts.

    &qspi {
    flash0: flash@0 {
    compatible = "micron,n25q128a13";
    };
    };

    Build and boot and QEMU and you should be able to see the partitions.

    ------------------------------------

    I think the key part here was the "n25q128a13" string which more specifically matches the flash device on these boards.

    Can you give that a try and see if the MTD partitions appear for you?

    Regards,

    -Kevin

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Reject Answer
    • Cancel
  • Former Member
    0 Former Member over 10 years ago in reply to zedhed

    Kevin,

    It worked! The difference was just the "a13" as you suggested. Thanks you very much!

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
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