bklopp
-
Content Count
22 -
Joined
-
Last visited
-
bklopp reacted to an answer to a question:
Searching for Microblaze Interrupt Examples
-
bklopp reacted to an answer to a question:
Searching for Microblaze Interrupt Examples
-
Sorry I tried to do a lightning fast edit to mention that I'm looking for examples for either the Nexys4 DDR or the Nexys video. Trying to upgrade a cmod project to one of those boards is kinda a messy. I suppose I can just try to recreate it if you guys don't have any examples for those boards.
-
I was wondering if you guys had any sweet examples using microblaze interrupts and interrupt handlers. I've been having some bad luck with my own project. Instead of getting into the details of my broken project here, I figure I'd just ask for a working example to see where I'm going astray. Thanks in advance! Edit: I'm specifically looking for exmples for either the Nexys video or Nexys 4 DDR.
-
bklopp reacted to an answer to a question:
Attempting to Program Nexys Video SPI Flash With Microblaze C Code
-
It was in the working Vivado 2017.4 OLED QSPI project for the nexys video that you gave me a few posts up. I compiled the project and it happens to program the c code from flash much faster than if spansion was selected.
-
I'm wondering, why do you have micron selected instead of spansion, since it's a spansion chip on the board?
-
bklopp reacted to an answer to a question:
Attempting to Program Nexys Video SPI Flash With Microblaze C Code
-
bklopp reacted to an answer to a question:
Source Code in SDK
-
Cannot connect PYNQ-Z1 (Both Ethernet and USB Serial)
bklopp replied to timesup's question in Embedded Linux
I would try 9600 Baud and use teraterm instead. https://download.cnet.com/Tera-Term/3000-2094_4-75766675.html -
bklopp changed their profile photo
-
I finally got it working by following instructions from a forum post on xilinx forums: https://forums.xilinx.com/xlnx/board/message?board.id=EMBEDDED&message.id=43256#M43256 I'll look at your projects and figure out where I'm going wrong, since the fix recommended by the dude from xilinx only uses single spi mode (X1), so I imagine it loads quite a bit slower than it could. Because of that, I hesitate to mark this post as the solution. 1) Yes 2) Yes 3) Here are my cache settings. I'm a bit curious why the cache matters. Does the "hello world" application get loaded int
-
I regenerated the bit stream with the QSPI flash IP connected to 50MHz and set to Quad. Same result, nothing has been printed to the terminal. I notice that when I press the program button on the nexys video board, the done light (LD15) comes on after about 10 seconds . EDIT: Actually I do get the "SREC SPI Bootloader" output to the terminal, so that C code must be programmed to the spi because it is executing. I'm guessing the bootloader is supposed to boot the helloworld, but that just isn't happening for whatever reason. EDIT 2: I dug into the srec bootlo
-
bklopp reacted to an answer to a question:
Attempting to Program Nexys Video SPI Flash With Microblaze C Code
-
bklopp reacted to an answer to a question:
Attempting to Program Nexys Video SPI Flash With Microblaze C Code
-
I have been programming the Nexys video through the USB J12 port, I do have a JTAG HS2 on hand that I can use to program the board with. Do I need to use the JTAG HS2 for this to work? 1) Here is the block design, I am using the 100Mhz clock... that might be a problem: 2) I am able to run the hello world program by run as->launch on Hardware(system debugger) 3) I'm assuming your asking about the linker script: I'm rebuilding the project with the 50Mhz clock to try that out. Thanks.
-
I have been following this tutorial and have had no luck. I am uncertain about how to configure the QSPI IP, because the tutorial starts assuming that I have done that part successfully, so I am not even sure if this is the root of my problem. I have tried these two configurations of this IP, compiled them, and exported them to the SDK, and none of them solved the problem: I made sure JP4 is in the QSPI position. On step 3.1 in the tutorial, I can see that the FPGA is programmed successfully and I see the following output (since I chose not comment out the VERBOSE define as su
-
Awesome, thanks guys that worked for me. I also had to make sure the component definition name matched the "of_component=" name in the interface definition. For anyone with the same problem, here is the working interface definition in the board.xml file: <interface mode="slave" name="sysclk" type="xilinx.com:interface:diff_clock_rtl:1.0" of_component="sysclk"> <parameters> <parameter name="frequency" value="300000000"/> </parameters> <preferred_ips> <preferred_ip vendor="xilinx.com" library="ip" name="clk_wiz" order="0"/>
-
Since you folks an Digilent make these wonderful board files that make it super easy to connect components, I figured I'd make my own for a custom board. The problem is that my design uses a differential sysclock, whereas most Digilent designs use a single-ended sysclock. I have been pouring over the board file chapter in UG895 to figure out how to do this, but unfortunately I haven't found any examples or hints in doing so. A single-ended clock interface in the board.xml file looks like this: <interface mode="slave" name="sys_clock" type="xilinx.com:signal:clock_rtl:1.0" of_
-
I assumed the constraints were generated from the pin file, which is referenced by the board file.
-
jpeyron reacted to an answer to a question:
Nexys Video DMA Audio Demo is broken
-
I followed your suggestion and just downloaded Vivado 2016.4. I tested it and it works on that version.
-
It looks like the interrupt is never being triggered by the DMA. I put a breakpoint inside of the interrupt handler and it never hits it.
-
I created a new empty application project, imported the folders and files from the DMAaudio folder into my project. I could use some clarification on what you mean by "manually importing all the settings from the old one" What settings are you referring to? The settings under the Board Support Package settings? If so, which ones need changed to what? system.mss system.mss