All Activity

This stream auto-updates     

  1. Past hour
  2. @dcc, This is really the backwards way to get something like this going. You should be proving your design in simulation before jumping into a design on hardware. Let me offer you an alternative. Here is a Verilog driver for talking to an SD card using SPI. If you have already chosen to use the AXI bus, you can find an AXI-lite to WB bridge here that will allow you to talk to this core. Even if you already have a driver you like, this documentation for this one describes how to set up the SD card to where you can talk to it, and provides examples of how to read and write sectors. Even better, there's a piece of C++ code which can be used as a simulator with Verilator. (Not sure if this would work with MicroBlaze or not.) You can then use Linux tools, such as mkfatfs and such, to create a file with a FAT format that you can use as a "simulated" SD card. When the simulation isn't running, you can mount the card on your system and check out/modify the files, and so know that things will work (based upon your experience with simulation) once you finally switch to hardware. Indeed, if you are willing to accept the risks, you could even interact with your SD card from the simulation environment itself. If you want an example of a set up that would control the SD card interface from a ZipCPU, you can check out the ZBasic repository which has such a simulation integrated into it. Indeed, there's even an sdtest.c program that can be used for that purpose. As for reading and comprehending the FAT filesystem, there's a FATFS repository that is supposedly good for use with embedded software. I haven't tried it, so I can't comment upon it that much. Alternatively, if you can control how the file system is laid out, you should be able to place a file of (nearly) arbitrary length a couple of sectors into the FS, and force the file to be use contiguous sectors. If you do that, then you've dealt with the most complicated parts about reading from the SD card. Just my two cents, and some thoughts and ideas along the way. Dan
  3. Today
  4. Hi @fangzr, I am not familiar with RTL8812au, but I managed to set up a ath9k dongle driver for the Zybo Z7-20 with petalinux. For the ATH9K it's easier because it has the driver in the kernel you just need to activate it. Regarding the RTL8812au all I can tell you from experience is that some Wireless dongles need additional firmware, like the ATH9K, which will be loaded in to the wireless automatically over USB, provided you set up your USB port to identify mass storage devices. These should be copied in to the corresponding folder on the rootfs of your target. Another critical issue is the driver dependencies, some Wireless drivers need to have certain Kernel drivers loaded in order for them to work, like the MAC80211 stack in the Kernel for instance. Please make sure that your driver is not depended on anything else. Based on the log you have sent us, I would start with this. -Ciprian
  5. thank you. I am not a very sophisticated programmer, but anyway I will let you know what sampling rate I achieved after doing it.
  6. Hi @JColvin, Thanks for the response ... I managed to figure it out eventually ... It's an HDL only project. Using Chipscope I was seeing that I could write different data (up/down count, etc) starting from address 0 and read that back correctly, but every time I opened the same SD on PC it wanted to format it. I was messing with the file system (which I don't need actually). HxD allows you to "opendisk" regardless of the file system, and also raw disk edit ... I found it on an MIT course. It's does the job. best, DCC
  7. vicentiu

    Nexys A7 not working

    Can you try connecting it to a different system, preferably a desktop? We have seen laptop usb ports that don't give enough power. Can you also try with another USB cable? Do you have access to a power supply to see if it turns on when supplied with external power?
  8. asd123

    Nexys A7 not working

    it is powered over USB, none of the led's on.
  9. Hello all who are reading this. I managed to get it working with this timing block. Constraints files can be found in the repository. Enjoy.
  10. asd123

    Nexys A7 not working

    it is powered over USB, none of the led is on.
  11. As @xc6lx45 recommends, can you try the board on another system with a different cable and see if you reproduce the issue? Do you have any other fpga board you can try on that system and see if Hardware Manager recognizes it?
  12. Hi, the difference may be that this board is bus powered. Most likely the USB cable and / or the PC side USB hardware are at fault, even if they work with other boards.There can be supply issues that border on Voodoo, e.g. caused by permanent changes in polyfuses on the host after tripping them once. You cannot "prove" that a cable etc works by testing it with another device (not stating this as a philosophical concept but as a lesson learned the hard way with a unit that went to customers...) If you would rig up a debug cable with an amperemeter in +5V, you would probably observe that the FT2232H USB chip draws ~80 mA once it's initialized by the driver, and this drops to zero when the chip decides USB is bad and it shuts down. There is AFAIK nothing that can be done about this in software or configuration.
  13. vicentiu

    Nexys A7 not working

    Is it powered over USB, or an external power supply? Are any of the led's on? Can you send us a picture so we can see the jumper positions?
  14. Followed your instructions and was able to obtain a screen shot of the failed connect process. Attaching it herewith .. Please let me know the next step. And just FYI, even now if I disable WiFi on my laptop, I can connect to the Localhost: 42315 server. Of course it uses the default profile for this.
  15. Timing sequence should be fine now (feel free to test out with this testbench). I've taken a look at the synthesized design and found something odd. For some reason these output signals are tied to ground (as if they weren't used..). There are other warnings as well which I found rather bizar.
  16. asd123

    Nexys A7 not working

    The Nexys A7 suddenly shut down when operating normally connecting to my laptop, and cannot be turned back on.
  17. TerryS

    Vivado free for Artix-7?

    Thanks for all the help. I was able to finish the Vivado install and get through the 'blinky' tutorial. Very nice documentation. It didn't exactly match the 2018.3 version of Vivado that I installed, but close enough to have me blinking an LED in no time at all. Terry
  18. Hi, I have a brand new Digilent A7-35T board I tried to program via the USB built in JTAG using Vivado 2018.2. The part intermittently shows up in Hardware Manager, but a seconds later disconnects. Sometimes it disconnects just being connected (opened) in Hardware Manager and sometimes during programming. It is even worse if I try to erase and program the QSPI flash. I also downloaded and installed the latest Digilent Adept 2 with updated drivers and observed the same behavior. I tried different USB cables, different USB ports directly on my PC, via a powered hub, but the behavior is always the same -- it intermittently disconnects and fails. The amber LED does however stay lit. In Device Manager I am able to see the FTDI UART. I did also see it enumerate as a Microsoft BallPoint Mouse -- whatever that is. With this exact same setup, PC, Vivado, USB cables, etc, I have been programming the Zybo Z7-20 and the Arty boards with several designs without any such issues. Please let me know if I missed anything and what are the next steps in getting the board replaced or fixed. Thanks.
  19. Yesterday
  20. TerryS

    Vivado free for Artix-7?

    Yep, my bad. I finally realized the download tool was reporting the rate in MBps (not mbps). So what I thought was only 1Mbps was really at least 8 times faster than that, which is about the limit of my rural internet service. The download is a whopping 18GB, which is going to take a while. Unfortunately, it kept stopping occasionally and reporting a file didn't download, and waiting for me to confirm and try again. So I couldn't just start the download and walk away. Anyway, I'm getting close. Thanks for the heads up on what to expect. It has been almost 20 years since I last did any FPGA work. Terry
  21. The Arty board has all the JTAG circuitry plus a USB UART on board. You don't need a special cable - just use a good quality USB to micro USB cable. In the Vivado IPI, when you instantiate a Microblaze core, the MDM is automatically added and connected by block automation. The Xilinx SDK debugger will automatically use the MDM for debugging. You don't have to do anything other than start your program in debug mode. It sounds to me like going through one of the numerous online tutorials would help you get your bearings. Digilent has several including this one.Prolific blogger Adam Taylor also starts a series of posts on the Arty here. And if you like watching videos, Jeff Johnson at FPGADeveloper.com has this one.
  22. I'm looking through Xilinx file pg115-mdm.pdf about the Microblaze debug module. If I use a Microblaze core, I'm sure I'll need some debug capability. But I'm not sure how the MDM can be used on an Arty board. MDM seems to be a JTAG-based debugger. I think it uses the FPGA's JTAG pins. I know the Adept2 utility uses the USB connection to access JTAG through the FTDI chip. But "JTAG debugging" isn't on the list of what Adept2 does. In the Adept SDK, I see information about an API to access JTAG. That would probably work, but I'd rather not be debugging debug system software while I'm trying to debug my Microblaze software. Another issue is if I use the existing USB cable for JTAG debugging, will I have trouble running the UART bridge interface? If I get a Digilent JTAG-HS2 and use that for JTAG, will that solve the problems? The Vivado software would know how to use the JTAG on this adapter for its debugger right? And the UART bridge would still work as usual. Do I have it right? Or am I missing something stupid. I just want to make sure there's no problem with Microblaze debugging that makes it too hard to use in my application. Thanks. Allan
  23. I'm glad to hear that you've made some progress, Raghunathan, and I greatly appreciate your patience. Nothing about your system tells me it would be interfering with the agent, so I need you to do some more digging for me. I'd like to see what the console output is when you try to add your OpenLogger. Before doing anything, visit the Settings page, and click Advanced. Click the Change Console Log button, and choose Console. Once you've done so, press Ctrl+Shift+i to open the Chrome Developer Tools, and make sure the Console tab is active. Run through adding the device until it fails again. You should see a bit more detailed information as to why it is failing in the Chrome Developer console. If you can share that with me as a screenshot or some other way, I would appreciate it. About the profile: You shouldn't have to select the last saved profile when launching WaveForms Live. Ideally WaveForms Live recognizes what profile your device has assigned to it and will load it up, but that doesn't seem to be working. If you could also give me the console output after entering the logger page (when WFL checks the device profile) and share that, we should get to the bottom of this issue as well. Thank you for your cooperation and patience, AndrewHolzer
  24. JColvin

    Vivado free for Artix-7?

    Hi @TerryS, Unfortunately, the download speeds you are reporting are due to your end (either your internet connection or your computer hardware), not Xilinx's end. Note also as a fair warning (since I believe this is your first time using Vivado) that even simple projects, such as LED blinking project that xc6lx45, will probably take more time than you expect as the Vivado software needs to program and set every transistor inside the FPGA. There is a nice comment summarizing what all the tools need to during synthesis, implementation, and bitstream generation here. But as @xc6lx45, a lot of the material looks more complicated than it actually is, mostly because it's a different language. Thanks, JColvin
  25. In the meantime I've found some errors in my timing module code. I will update as soon as I've rectified them.
  26. Hi there, I designed a small module that's supposed to feed timing signals into the rgb2dvi block provided by digilent. The code I wrote which produces this can be found here. The connections required in the block design can be seen below in the picture. The I/O planning is shown as well. I'm not getting any HDMI out of it. I checked the testbench and it produced the correct sequence of outputs. (When the VDE signal is high the screen uses the color rgb_in) Can anyone test this on his board or notice any flaws? If you run this on a zybo z7-20: To create the required clock signal use clock wizard (input 125 MHz clock on pin k17 and produce 148.5 MHz to the timing module) Thanks a lot in advance.
  27. Hi @dcc, I'm not certain how you are verifying that the HDL is writing to and then reading back from the SD card in a normal formatting style, but in general FAT32 is a widely used format for SD cards that has existing material for it. I am uncertain why you are using a special tool to write to the SD card though; from what I can tell the tool is Windows compatible, so why not just use the Notepad program which comes with Windows and save a .txt file with the data you are interested in reading to the SD card or just using Windows Explorer (the file manager) to move the file of interest onto the SD card? If you do have a header in your file, you will need to take account for that, though I do not know what you mean by "random file" in this case. Thanks, JColvin
  1. Load more activity