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
MicroZed Hardware Design Micro Z custom driver
  • 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 325 subscribers
  • Views 243 views
  • Users 0 members are here
Related

Micro Z custom driver

asi
asi over 7 years ago

Hello,

I wish to write a C program in pulsar linux and communicate with my VHDL module in PL side.

I believe that I need to provide a driver for Amba AXI bus. I already watched the videos about linux device driver for the Z board, but it doesnt explain how is the patch written.It just generate a .ko file from the provided patch. Is there any tutorial to guide me how to go through the device driver for MicroZ and pulsar linux?

Best regards,   

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

    Hi ASI,

    When your VHDL is attached as an AXI peripheral to the AMBA interface, you can access the registers as a piece of memory space.  However, to access physical memory space under Linux, you either need to MMAP() into the PL memory space or, as you suggested, (and the best option in terms of system safety) to access physical memory space from a device driver.

    The patch you reference simply implements the code within the kernel source tree needed to build the drive driver that gets built into the .ko module.  There are lots of resources (several books) out there that are written to help people understand how to write a device driver.

    Here is some additional information from the Xilinx forum on device drivers:

    https://forums.xilinx.com/t5/Embedded-Linux/Create-a-Linux-Driver-for-a-custom-IP-on-Zynq/td-p/477628

    Best Regards,

    -Kevin

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

    Hi ASI,

    When your VHDL is attached as an AXI peripheral to the AMBA interface, you can access the registers as a piece of memory space.  However, to access physical memory space under Linux, you either need to MMAP() into the PL memory space or, as you suggested, (and the best option in terms of system safety) to access physical memory space from a device driver.

    The patch you reference simply implements the code within the kernel source tree needed to build the drive driver that gets built into the .ko module.  There are lots of resources (several books) out there that are written to help people understand how to write a device driver.

    Here is some additional information from the Xilinx forum on device drivers:

    https://forums.xilinx.com/t5/Embedded-Linux/Create-a-Linux-Driver-for-a-custom-IP-on-Zynq/td-p/477628

    Best 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