JColvin

Administrators
  • Content Count

    3410
  • Joined

  • Last visited

  • Days Won

    122

Everything posted by JColvin

  1. Hi azn103, You are correct in what you are seeing for the Pmods. The reason there is a difference in the first place is because a few years back the PIC32 microcontroller chip was changed so that the UART interface layout/organization changed, resulting the in the Type 3 to Type 4 change that you see. The tables in the document are only for the Pmods though; they do not define what the host header looks like, only what the headers on the Pmods themselves look like. A direct pin-to-pin compatible host would instead have the reverse of the pins -- i.e. RTS where there is a CTS and vice-versa, and a TXD where there is a RXD and vice-versa. Are just wanting to confirm how the Pmod pins are arranged or wanting to see overall how Pmods are designed to interact with the "outside world"? Thanks, JColvin
  2. JColvin

    Arty Board File

    Hi DoogieTech, I know the MIG has been fixed for the newer version of Vivado as indicated by this forum post, but I'm not sure about the older ones. I'll ask our application team about this. Thanks, JColvin
  3. Hi you, The Nexys4-DDR can be programmed through Xilinx's Vivado Design Suite. You can create an account with Xilinx and download the free WebPack version of Vivado here. Let me know if you have any more questions. Thanks, JColvin
  4. Hi mohammad, We (Digilent) did not create any of the drivers or software programs that are available Matlab so unfortunately, we are not able to offer any helpful support for your problem. There might be a community member here on the forum who has used the HDL coder within Matlab, but I am personally not aware of anyone who has done that. Thanks, JColvin
  5. Hi Yann, That is correct, there is not a way to configure the FTDI chip with our boards. Thanks, JColvin
  6. Hi Leon, Not necessarily. Sometimes the issue is with the Vivado cable drivers or even the USB cable itself. Check out this other forum post for some more information on this. Let me know if you have any more questions, Thanks, JColvin
  7. Hi shahabamo, I have asked some of our applications engineers about this who will get back to you here on the forum. Thanks, JColvin
  8. Hi Kevin, I have asked some of our applications engineers about this who will get back to you here on the forum. Thanks, JColvin
  9. Hi Emil, I have asked some of our applications engineers about this who will get back to you here on the forum. Thanks, JColvin
  10. Hi Leon, I have asked some of our applications engineers about this who will get back to you here on the forum. Thanks, JColvin
  11. Hi accel, I have asked some of our applications engineers about this who will get back to you here on the forum. Thanks, JColvin
  12. JColvin

    add ip in vivado

    Hi bahare, What sort of "earlier errors" does Vivado report? I imagine that Vivado would have listed some other errors in addition to this one. Thanks, JColvin
  13. Hi Tarik, Here is a post that explains how to program the SPI flash on a Basys 3 board from Vivado: What you'll likely need to change what memory you're searching for; according to ZYBO reference manual in section 4, this is S25FL128S. The reference manual also shows here, that you'll need to adjust a jumper to then boot the board from the SPI flash. Let me know if you have any more questions. Thanks, JColvin
  14. Hi Muminek, Presuming you already have the J16 jumpered in the UART position (which is usually the source of the error you're describing), there isn't going to be a whole lot you can do through MPIDE. If it is in fact the FlowCloud app that is using the Serial port which is not letting you program the board otherwise, the only thing I can conveniently think of is if the FlowCloud app allows you internally change which Serial (UART) port it is using on the chipKIT WiFIRE since the USB port on the board is hard-wired to Serial (as opposed to Serial1 which uses alternate UART pins available on the MZ chip). I do not know if this is possible with the FlowCloud app though. However, even if you do manage to do that, when you upload the Blink sketch from MPIDE, it is my understanding that it will overwrite any pre-existing code that has been uploaded to the board (excluding things like the bootloader and whatnot), so it would likely overwrite the FlowCloud app that has been preloaded. After doing some digging around on my own, it looks like (according to this page) that no configuration exists for the WiFi setup. It looks like you can change some of those settings as listed here. In the end though, I don't think you're going to be able to use MPIDE to program the board conveniently. The MPLAB X (developed by Microchip) looks like it could program the board without overwriting some of those settings, which is probably why they recommend using some sort of programmer like the chipKIT PGM. Digilent only manufactures the Wi-FIRE board though; the FlowCloud app was developed by Imagination and appears to be (I can't speak on this for certain) supported through their forum. Thanks, JColvin
  15. Hi Louis, I did some quick asking around to see if there was something that jumps out about this, but didn't find anything in particular. Since this is a driver developed by Xilinx (and what is having the issue), you will need to contact Xilinx support to receive the most effective help with the driver. Thanks, JColvin
  16. JColvin

    I2S L1

    I looked it up and found a little more information about it, it has a part number of 490-1028-1-ND, and it is actually a ferrite bead as opposed to an inductor. I apologize for the mis-information earlier. Thanks, JColvin
  17. If that is inside of your void loop function, then yes, that should (at least as far as I can tell) work out for you. Again, I haven't gotten to verify this myself, but I believe it should work out in principle. Thanks, JColvin
  18. JColvin

    I2S L1

    Hi JGRMSL, In this instance (and in most cases) parts labeled with an "L" on schematics traditionally indicate that part is an inductor. So on the PmodI2S, L1 is an inductor with a value of 2500 uH. Thanks, JColvin
  19. Hi Josh, I talked with the appropriate people at Digilent and they said yes, the ARTY board (from the Digilent website) will come with a Vivado Design Suite: Design Edition that is both node locked and device locked. Thanks, JColvin
  20. JColvin

    [Arty] Power Sequencing

    Hi Michael, I have asked some of our applications engineers about this who will get back to you here on the forum. Thanks, JColvin
  21. After looking into the SD library, when you call the begin() function for it (and do some digging in the folders) there is a line that resets all of the SPI settings to default. I personally don't know if the initialization of the PmodAD5 changes any of the SPI settings (which would then be all reset when you called SD.begin), but it may be worth a try to have the SD.begin() line be placed before all of the initialization of the A/D occurs. Let me know if this helps. Thanks, JColvin
  22. Hi Jrlin, I'm looking into this now. I keep getting a timeout error when I try to download the AD7193 library from Analog Devices so I can't look at that just yet, but I'm looking at the standard SD library and board files for the MX3 as well to see if anything jumps out at me from there. Thanks, JColvin
  23. Hi Mark, I re-looked at the spacing with some calipers and found the pitch between the pin 1's is 0.9 inches. I think the number Josh had before wasn't pitch distance. Thanks, JColvin
  24. JColvin

    Pmod

    Hi Brooke, Pmod boards do work with chipKIT boards. The idea behind Pmods is that they use a de-facto interface protocol such as SPI or I2C so they are able to communicate with any system (such as LabVIEW, chipKIT, FPGAs, or other microcontroller boards) that are able to use that communication protocol. You can find the most up to date list of Pmods and their related materials on our Wiki here. Let me know if you have any more questions. Thanks, JColvin