• Content Count

  • Joined

  • Last visited

About kb5pgy

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Affirmative. But, Vivado insists on not allocating DDR 3 memory space for code. Please just send me sample code to figure this out. I work on embedded systems for a living, and this is the most complicated means of trying to make an Arty S7 standalone. I have spent over a month on this.
  2. I found another issue. The bootloader is loaded upon reset, but when I attempt to create the linker script for the user application (step 2.3), the pop-up dialog does not allow me to put the code segment in the DDR. It is not an option for the "Place Code Section In:" pull down menu. It has to be a misconfiguration on my part in either the MicroBlaze or the MIG 7.
  3. Mine is the Arty S7-50. I was guessing on the offset value since it wasn't mentioned in the tutorial.
  4. Thanks. I was able to create an application with Quad-SPI and MIG 7 implemented, but I need to know what the FLASH_IMAGE_BASEADDR value is. I tried 0x00600000 to no avail. I first thought I had bricked it, but that was fortunately not the case.
  5. There is a missing step. How do you set up the DDR IP, specifically the "device_temp_i[11:0] input? The tutorial assumes you have a sample project, but where is the sample project? I cannot generate the bitfile, and doing the verification step leads to the following critical error: [BD 41-759] The input pins (listed below) are either not connected or do not have a source port, and they don't have a tie-off specified. These pins are tied-off to all 0's to avoid error in Implementation flow. Please check your design and connect them as needed: /mig_7series_0/device_temp_i
  6. First of all, I am not some hobbyist. I do this for a living in one of the most prominent centers of engineering in the world. I have also presented at NIWeek 2019. Here's the problem. I went through the video from the beginning to where the Hello World code is downloaded to the board. There was no output to the terminal via the USB connection, and the buttons did nothing. The outputs of the tool chain were as expected, but the code did not work. Period. There was also no already-compiled solution code that could be used as a reference for troubleshooting. I am at the end of my rope with this. I wanted to recommend the Arty S7 board for data acquisition purposes for projects not requiring the horsepower of the Compact Reconfigurable Input/Output, but I am forced to conclude that this is not a solution. To me, the S7 is a nice paperweight, but an expensive one. The one thing that impresses me with NI is that there is a large library of sample code, and I refer to that library when working a new project. Unfortunately, there is very little in the way of sample code for this board.
  7. I attended that seminar, and unfortunately, all I got out of it was a sense of frustration. It was rushed through, and I was unable to get Lab 2 "Hello World" working. I sent a note to the instructors on Zoom, but it was unanswered. It should have been made clear in the email soliciting this seminar that expertise in Vivado 2018.2 and Keil uVision 5 as prerequisites. I do not know if my issues were due to a configuration issue in my computer or due to a nuance that was not covered in the course workbook provided to attendees. I repeated Lab 1 and Lab 2 ten times with the same result: the output of the "Hello World" lab was not as shown in the workbook. I have requested an RMA for the materials purchased for that seminar, as they are useless to me now.