JColvin

Administrators
  • Content Count

    4025
  • Joined

  • Last visited

  • Days Won

    157

Everything posted by JColvin

  1. Hi @nigelm, We are in the process of updating our material for Vivado 2020.1; I believe the materials for the Pmod IP library has been updated and is available here: https://github.com/Digilent/vivado-library/tree/feature/pmod_update. In terms of the specifically updating examples, a number of projects may be able to updated on their own by opening the project in 2020.1 and then running through the Reports->Report IP Status within Vivado and then upgrading those IPs (via the button of the same name at the bottom of the Vivado). If the project includes a Digilent made IP, we may need to update it ourselves if it not readily compatible with the latest version of Vivado. Thanks, JColvin
  2. Hi @Joseph Decuir, I have moved your question to a more appropriate section of the forum where the engineer most familiar with the WaveForms software will be able to see and respond to your question. Thanks, JColvin
  3. JColvin

    Pynq Z1 board files

    Hi @svaughn442, We don't have board files specifically for the Pynq Z1, though you can use the board files for the Arty Z7-20 which is a very similar board in terms of both specifications and layout. Please note that all support and materials for the Pynq-Z1 board are located on http://www.pynq.io/. Let me know if you have any questions. Thanks, JColvin
  4. Hi @perdue, What device are you attempting to detect? Thanks, JColvin
  5. JColvin

    Pmod OledRGB

    Hi @n3rdx, Nice! I'm glad you were able to get it up and running. With regards to the smaller (and larger) font, that is less easy to do. There are two reasons for this. The first is visual with regards to resolution; the character library (CharFont0.h; the chips in the Pmod OLEDrgb do not have any built-in character libraries) has each of the ASCII characters fitting in their own 8x8 pixel arrangement, nicely fitting into the 96x64 pixel display of the OLEDrgb for corresponding 12 by 8 character blocks. Changing the character library so that individual ASCII characters are smaller is difficult to make sure they are still readily distinguishable (lowercase and uppercase 'K' would be an example of this as well as the gap in a lowercase 'e'). The second reason would be how the individual characters are each stored. After doing the sprite work to get the characters smaller (perhaps in a 6x6 pixel frame rather than an 8x8) for the CharFont0.h file, you would need to adjust the DrawGlyph and AdvanceCursor funtions, the OLEDCHAR_BYTES #define value, to properly handle the smaller number of bits. This is also possible to do, but not necessarily an afternoon task depending on how you want to change the functions to handle this. Thanks, JColvin
  6. Hi @crash_override, I think this may be because the MSO Read VI doesn't actually "read" the analog data; the description states that it transfers the data from the instrument. I'm not sure if it then clears out the data from the Instrument, but since you are not getting new measurements, that may be why you are getting strange data. You may want to also include the MSO Run Vi (or however you have your voltmeter data measurement happening) to keep collecting new data, similar to how it is done in the image of the while structure I have attached. Thanks, JColvin
  7. Hi @crash_override, Yes, that is the input on the VI that I used. There may be a different way to do it (there is of course the more convoluted way of having LabVIEW call an external python script that uses the WaveForms SDK functions to control the Analog Discovery 2), but I imagine that's not quite what you are looking for if you are using LabVIEW; I'm not super familiar with the VI sets unfortunately. Thanks, JColvin
  8. JColvin

    Pmod OledRGB

    Hi @n3rdx, Within the wrapper->hw->drivers->PmodOLEDrgb_v1_0->src->PmodOLEDrgb.c you can find it's functions that call the Xilinx SPI functions (OLEDrgb_SPIInit on line 1017, WriteSPICommand on 1063, and WriteSPI on 1086. The Xilinx SPI functions themselves are in xspi.c in the same structure path as PmodOLEDrgb.c. For what it's worth, there is an example set of commands for what the Pmod OLEDrgb should do during start up; I don't know if the IP follows the commands in the same order, but it will at least let you know what bytes you would be looking for: https://reference.digilentinc.com/reference/pmod/pmodoledrgb/reference-manual#quick_data_acquisition. Thanks, JColvin
  9. Hi @wanag, I don't have access to an Analog Discovery Studio while at home to readily test this myself, but it is my understanding that each of the power switches present on the Breadboard Canvas (I presume that is what you mean by proto board) individually enable the four sets of power supply rails (3.3V, 5.0V, +/-12V, and the +/- variable rails) present on the Breadboard Canvas itself. To test the voltage rails, I would run wires from the + side of Oscilloscope Channel 1 to the desired point to measure, and then the - side to ground, similar to the mock-up image I attached (making sure that the piece of foam under than BreadBoard Canvas is removed). Is this what you did? Thanks, JColvin
  10. Hi @Siriusly?, I have sent you a PM with some instructions. Thank you, JColvin
  11. Hi @algailani, I apologize for the delay; I don't have a DMC60C motor controller at home with me to confirm this, but I believe the expansion port is in the rectangular section with rounded edges just above the Digilent triangle logo. It looks like there are two hex bolts on either side of cover that will need to be removed. Let me know if this is not the case. Thank you, JColvin
  12. JColvin

    Pmod OledRGB

    Hi @n3rdx, The typecasting complaint and the complaint of the unused variables with regards to the OLEDrgb SelfTest an be ignored (or at least we have consistently ignored them for the last few updates with no detriment). I don't have a SEEED Studio S7, but I created a couple of Microblaze projects for the Pmod OLEDrgb on one of Digilent's S7 boards (one using the on board DDR, one ignoring the DDR) and neither project encountered the *.o error; I cleaned and rebuilt the project multiple times to test this. I asked the engineer who's been running the updates and they let me know that have occasionally been getting that error and been doing the following: convert the OUTS variable of the makefile from using a *.o pattern to using addsuffix, basename, and wildcard function calls, which list out the object files that are output by the compiler on a C-source by C-source basis, instead of just finding any .o files in the working directory. I.e. replace OUTS=*.o with OBJECTS= $(addsuffix .o, $(basename $(wildcard *.c))) in the driver's makefile down in the BSP libsrc folder. They also broke the COMPILER call out of the libs rule and placed it in a %.o: %.c rule. I attached the makefile for the OLEDrgb in case you wanted to compare it to your own. Otherwise, they have been seeing similar issues and are working to resolve them. The file causing the bugs is typically placed at <platform>/microblaze_0/domain_microblaze_0/bsp/microblaze_0/libsrc/<pmod>/src/Makefile. For both of my Microblaze applications (I only used USB UART and the Pmod OLEDrgb IP cores as "extra" pieces of the Microblaze design) with 32 kB dedicated to the local memory of the Microblaze processor for both the DDR and non-DDR variants (16 kB cache for the the build with DDR) didn't use a lot of memory; the values that I have in my .elf.size file for the non-DDR variant is as follows: text data bss dec hex filename 20300 324 3480 24104 5e28 rgb-s725-noDDR.elf Thanks, JColvin Makefile
  13. Hi @shra1201, I apologize for the delay; I should have clarified that you needed to download the .zip from the release tab: https://github.com/Digilent/USB104A7-ZmodADC/releases. More details with specific instructions are available in the readme, available both in the downloaded zipfolder and on the Github page. Let me know if you have questions about this. Thanks, JColvin
  14. JColvin

    Pmod OledRGB

    Hi @n3rdx, I'll see if I can get a design made, though know that none of us at Digilent have worked with or have a MiniZed from Avnet so we won't be able to do any hardware tests. Could you provide a screenshot of your block design? It sounds like you're adding a microblaze design which I wouldn't recommend doing if you are already using a Zynq based board. In terms of the numbering scheme for Pmods, Pmod ports are designed with with 12 pins with the first four pins on the top row (1-4) being data pins, pins 5 and 6 being ground and Vcc pins, respectively, then pins 7-10 on the bottom row which are physically directly below pins 1-4, followed by pins 11 & 12 which is a second pair of ground and Vcc pins. Thanks, JColvin
  15. Hi @aadgl, I apologize for the delay. There are a couple of recently made tutorials that may be of help to you. The first one is a revamped version of the "How to store your SDK project in SPI Flash" tutorial that was updated to 2019.1 and uses the Nexys A7 100T (the tutorial lists the Nexys 4 DDR, the Nexys A7 is the newer branding of the same board) and goes through the process of adding DDR and Microblaze to the design. The other tutorial is for Vivado 2020.1. As a fair warning, this material is still being reviewed and refined, but does walk through adding DDR memory to Microblaze designs. Let me know if you have any questions. Thanks, JColvin
  16. Hi @P Ross Taylor, I'm not too familiar with the NI Virtual Bench functions, but you may want to take a look at the other VI's that are available for the Analog Discovery 2 (and are already part of the LabVIEW 2020 Community Edition if that is an option for you); there are some more details available in this thread here (though note that not all of the available device features are necessarily present in the VI sets): Let me know if you have any questions. Thanks, JColvin
  17. Hi @Sean Kelly, Unfortunately, it is Digilent's policy not to share the design files for our products. Let me know if you have any questions. Thanks, JColvin
  18. Hi @nagi, Digilent has not done this, but there are some basic instructions on how this might be done here: https://forums.sifive.com/t/build-sifive-freedom-in-windows-10-64bit-cygwin/1924, though as they noted at the bottom of their post it'll probably be more straightforward to use Linux. Thanks, JColvin
  19. Hi @laurent01, I apologize for the delay. What are the terminal settings that you have under Setup->Terminal? Thank you, JColvin
  20. JColvin

    Pmod OledRGB

    Hi @n3rdx, The material that we have on our GitHub for the Digilent Vivado library (unless otherwise specified at the top of the material) is MIT licensed: https://github.com/Digilent/vivado-library/blob/master/License.txt. So yes, you can use our material in your own application. In terms of changing the IP package, there are probably two critical warnings that you are encountering. One is a warning that the IP needs to be re-packaged with the new version of Vivado; you can get the current working branch for Pmods for Vivado 2020.1 from this development branch (no formal release yet) here: https://github.com/Digilent/vivado-library/tree/feature/pmod_update. The other critical warning would be that the subcore XCI files were last packaged with a different board than the one being used, but that is safely ignored. In terms of getting Pmods to work on the Minized, the main thing that the Pmod interfaces would be need to be added to the board file so that Pmod IPs can be readily added. Otherwise, Pmods communicate over some sort of standard communication protocol like SPI or I2C, so it is always possible to "bit-bang" out the needed communication. Let me know if you have any questions about this. Thanks, JColvin
  21. Hi @shra1201, There is material for the USB104 A7 and the Zmod ADC1410 available on our Github here: https://github.com/Digilent/USB104A7-ZmodADC. Let me know if you have any questions. Thanks, JColvin
  22. Hi @Laumont, I'm not personally familiar with the filter2D material but it looks like there are some extra commands and settings you can do for filter2D available here: https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841920/reVISION+Getting+Started+Guide+2017.4#reVISIONGettingStartedGuide2017.4-RuntheFilter2Dsampleapplication. Otherwise, it looks like there are some conversions available in the Color Conversion section in this OpenCV User Guide. Thanks, JColvin
  23. JColvin

    JTAG-USB Question

    Hi @PFuchs, I apologize for the delay; I have responded to your email that you previously sent to the Digilent Sales department with the needed details. Thank you, JColvin
  24. Hi @armandomisista, Can you let me know some more details on how the JTAG HS2 became broken? I and another engineer I asked about this have never heard of it failing so badly that the FTDI chip needed replaced. The EEPROM is separate from the FTDI chip though so if only the FTDI chip was replaced the module should still be fine. Thanks, JColvin
  25. Hi @crash_override, I presume you are using LabVIEW? I opened up one of the DigilentWF examples which use both FGen and MSO that come with LabVIEW Community Edition and was able to adjust the voltage used beyond 1.5V. Let me know if you have any questions about this. Thanks, JColvin