Comments on: Microblaze + Linux: Sample design of a custom peripheral https://billauer.se/blog/2011/08/microblaze-custom-ip-peripheral-axi4-cip-ipwiz/ Anything I found worthy to write down. Thu, 26 Mar 2026 13:15:15 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: lwei https://billauer.se/blog/2011/08/microblaze-custom-ip-peripheral-axi4-cip-ipwiz/comment-page-1/#comment-973 lwei Mon, 04 Aug 2014 12:34:38 +0000 https://billauer.se/blog/?p=1755#comment-973 Thank you very much! Thank you very much!

]]> By: eli https://billauer.se/blog/2011/08/microblaze-custom-ip-peripheral-axi4-cip-ipwiz/comment-page-1/#comment-972 eli Mon, 04 Aug 2014 07:01:57 +0000 https://billauer.se/blog/?p=1755#comment-972 The address range of each peripheral is set when it's connected to the bus in XPS (or Vivado's block builder). The AXI interconnect makes sure than any request that arrives to the peripheral is intended for it -- the peripheral doesn't need to make any address decoding. As a result, the peripheral doesn't need to know what its base address is. The address range of each peripheral is set when it’s connected to the bus in XPS (or Vivado’s block builder). The AXI interconnect makes sure than any request that arrives to the peripheral is intended for it — the peripheral doesn’t need to make any address decoding.

As a result, the peripheral doesn’t need to know what its base address is.

]]> By: Anonymous https://billauer.se/blog/2011/08/microblaze-custom-ip-peripheral-axi4-cip-ipwiz/comment-page-1/#comment-970 Anonymous Mon, 04 Aug 2014 06:56:03 +0000 https://billauer.se/blog/?p=1755#comment-970 I found that you did not use the C_BASEADDR in you verilog file, i want to know how you peripheral know that the data is for you peripheral.I am a student from China, is learning how to develop AXI4Lite Peripheral,please forgive my poor English! I found that you did not use the C_BASEADDR in you verilog file, i want to know how you peripheral know that the data is for you peripheral.I am a student from China, is learning how to develop AXI4Lite Peripheral,please forgive my poor English!

]]> By: eli https://billauer.se/blog/2011/08/microblaze-custom-ip-peripheral-axi4-cip-ipwiz/comment-page-1/#comment-852 eli Fri, 01 Mar 2013 10:06:17 +0000 https://billauer.se/blog/?p=1755#comment-852 This specific driver does nothing except loading itself. For interaction with a user-space program, you probably want it to stand behind a device file. Recommended reading: http://lwn.net/Kernel/LDD3/ This specific driver does nothing except loading itself. For interaction with a user-space program, you probably want it to stand behind a device file.

Recommended reading: http://lwn.net/Kernel/LDD3/

]]> By: Fred https://billauer.se/blog/2011/08/microblaze-custom-ip-peripheral-axi4-cip-ipwiz/comment-page-1/#comment-851 Fred Fri, 01 Mar 2013 08:29:55 +0000 https://billauer.se/blog/?p=1755#comment-851 Linux is new for me, and this howto is very helpful. Thank you!! By the way, do you know if it is possible to have access to this driver from the user application, like we can do with ioctl on char drivers, or is it limited to the kernel? Thanks. Linux is new for me, and this howto is very helpful. Thank you!! By the way, do you know if it is possible to have access to this driver from the user application, like we can do with ioctl on char drivers, or is it limited to the kernel?
Thanks.

]]> By: eli https://billauer.se/blog/2011/08/microblaze-custom-ip-peripheral-axi4-cip-ipwiz/comment-page-1/#comment-801 eli Tue, 09 Oct 2012 11:38:55 +0000 https://billauer.se/blog/?p=1755#comment-801 There are so many things that can go wrong, so I can't help you much here. As a side note, I don't necessarily agree with you on the ioremap remark: The standard way is to add an entry for your peripheral in Linux' device tree, and have the driver fetch the physical address from there. But for a on-off project, hardcoding the physical address of the peripheral in the driver is fairly acceptable. There are so many things that can go wrong, so I can’t help you much here.

As a side note, I don’t necessarily agree with you on the ioremap remark: The standard way is to add an entry for your peripheral in Linux’ device tree, and have the driver fetch the physical address from there. But for a on-off project, hardcoding the physical address of the peripheral in the driver is fairly acceptable.

]]> By: Nighseas https://billauer.se/blog/2011/08/microblaze-custom-ip-peripheral-axi4-cip-ipwiz/comment-page-1/#comment-800 Nighseas Tue, 09 Oct 2012 09:22:10 +0000 https://billauer.se/blog/?p=1755#comment-800 I want to implement this peripheral on zynq and have already create an IP to read the status of switches and control the LED on my Zedboard. It uses two 32-bit registers and works well. Now I need to control my peripheral through a Linux app. But this driver seems not corecct to zynq platform. I konw that an ioremap function should be used instead of of_iomap. And what else should I do to make it work? Expect for your replayment. I want to implement this peripheral on zynq and have already create an IP to read the status of switches and control the LED on my Zedboard. It uses two 32-bit registers and works well. Now I need to control my peripheral through a Linux app.

But this driver seems not corecct to zynq platform. I konw that an ioremap function should be used instead of of_iomap.

And what else should I do to make it work?

Expect for your replayment.

]]>