• Content Count

  • Joined

  • Last visited

About kypropex

  • Rank

Recent Profile Visitors

1339 profile views
  1. Hi, I have a friend who has bought a Basys 3 and has done some great projects in HDL, but he wants to step it up a notch and try something with MicroBlaze. Although I'm willing to help him I don't have the time for it so I thought about sending him some tutorials on MicroBlaze and GPIO using block design and Vivado. The only problem is that there are no coherent tutorials for this and the ones I found to be decent where for EDK. To be clear I'm not looking for a board specific project, all I want is on tutorial which shows a beginner how to use a GPIO with MicroBlaze in Vivado. Do you have something you could recommend or a tutorial which you are working on? Anything compact and simple with MicroBlaze an AXI GPIO some SDK code and steps on how to set it up will be of grate help. Cheers, K
  2. Hi Ag, I based my design on the getting started tutorial from Digilent: Although I dislike and mostly advise against multiple tutorials, you might find some help there regarding the adaptation of your project to mine. I have not read the zynq book so I do not know if there are any differences between this tutorial or the other, being a simple project there should be little to no differences in the HDL (Vivado) part of the project. I recommend sticking to the SDK part because that seams to be working. Good Luck.... and my the odds be ever in your favor
  3. Hi Ag, First of I don't particularly understand where you have gotten your sources from, they seam to be a combination between several tutorials; I would recommend, choosing one tutorial and sticking to it and if it dose not work search for a new one (this is assuming I am right). The second issue is that I do not understand what is wrong, the board seams to be programmed correctly with the .bit file (this is basically the "compiled" version of what you did in Vivado) therefore the JTAG chain is initialized and the board has been identified. What is missing from the log is the programming of the .elf file (this is the compiled C project which you have written in SDK) to the board, this is a bit peculiar because the processor has been reset and configured, which usually happens when the elf is written (as far as I know). In order to program the .elf file on the Zybo board you have to right click on the project -> Run As -> Lunch on Hardware (System Debugger) (please refer to attachment 1 of this message). This is assuming you have not already done this. If none of this has been any help so far, I'll also attache a link to the project I have written In Vivado 2015.4 to test your .c file. The project works for me, on a Zybo board. I suggest you look it over and compare your project with mine. I'm curious about the answer to your problem, so please reply here if you have found the soulion to your problem. Best regards.
  4. You are right Hamster.... generally speaking for an user who is familiar with PLLs it is better use HDL primitives, it gives you more control over the code you are writing and it is easier to port from one project to another, provided you use the same FPGA. As far as I remember different FPGAs have different primitive functional models which makes it a bit confusing for somebody who is not familiar with this. The main reason for suggesting the clocking wizard was that, for somebody who is new to Digital Clock Managers in a FPGA it is easier to have a graphical user interface in which you just add the input frequency and the desired output frequency and not worry about adding output buffers and calculating the exact multiplication and division factor; this is done automatically by the wizard. It's also easier when you port your project to a different FPGA because the clocking wizard is not specific to a particular FPGA. Never the less, and I may be wrong here, it's less optimized then using HDL primitives. I would not by an external oscillator for this ... except if you want your project to be extremely precise. As Hamster said it shouldn't make much of a difference if its off by an approx of 0.02 MHz, it is a great opportunity to learn about clocking in a FPGA and it will cost you some time to learn it but it could save you a lot of time and money on the long run rather then always buying a oscillator when you are using an FPGA.
  5. Yeah.... well I've never used cygwin so I can't help you with this. I'm using a VM for the u-boot and kernel files and the making of the devicetree while using Vivado or EDK in Windows, seams easier for me. The other alternative was to implement a dual boot on my PC and work in Linux only... not particularly keen on this. Regarding the CROSS_COMPILE, I use the generic arm compiler and it seams to be working well.... CROSS_COMPILE=arm-linux-gnueabi- . This dose not require me to install SDK or Vivado on my VM. I can't remember seeing that particular error before. Did you configure the u-boot before you try to build it? (I presume you did, but better safe then sorry)
  6. Hi, As far as I know you have only one option. You have to implement a ip core called "Clocking Wizard" which can be found in the ip catalog. From there you can chose either to instantiate a mmcm or a pll and generate a specific clock. For further information I would strongly recommend to search for the clocking wizard product guide and read it.
  7. Hi, I would recommend that you make your own u-boot because otherwise you will not learn anything new about embedded linux. On the other hand you are right, there is some information missing and apparently the pdf is not up to date. A similar topic has been opened on this forum, which contains a more detailed description of the problem. Apparently the tutorial on indestructibles is being updated, as far as I understand. in order to simplify you search, two of the most common issues are: 1) There is no zynq_zybo_config in u-boot Sol: When you download u-boot from Digilentinc git you must use the master-next branch 2) Although you have the master-next version of u-boot you still can't find zynq_ZYBO_config Sol: you have to use lower case when you write zybo, the correct name is zynq_zybo_config As a general notice, when you are attempting to configure u-boot for a specific board, in this case Zybo, you can search in u-boot_folder/include/configs for a header file which must have the same name as the configuration file you are trying to make; in this case you are configuring zynq_zybo_config therefor there must be a zynq_zybo.h. If you are encountering other issues which are not mentioned in the tutorial on indestructible, other then the ones mentioned in the forum link which I have provided or other then the ones I mentioned, please provide a detailed description of the problem you encounter.The less vague you are the more specific help you are likely to get ... and people will be more inclined to help.
  8. kypropex

    Zybo Linux

    It worked. Thanks. The problem is I was hopping for a ramdisk included somewhere on the site, it would have been easier then searching for it on the ZED page.
  9. kypropex

    Zybo Linux

    Hi, I'm fairly new to embedded linux and I thought I'd start using my Zybo at it's full potential. So I've been following Kaitlyn Franz's tutorial on instructables and I got stuck at step 36, where you create the uramdisk.image. I can't find the initial ramdisk8M image nowhere. Could you please show me where I could find it?