JColvin

Administrators
  • Content Count

    4045
  • Joined

  • Last visited

  • Days Won

    157

Everything posted by JColvin

  1. Hi Stefano, I have asked some of our applications engineers about this; they will get back to you here on the Forum. Thanks, JColvin
  2. Hi Nima, I have moved your question to the FPGA section of the forum where the engineer best suited to help you will be able to see and respond to your question. I have also asked some of our applications engineers for further input on this. Thanks, JColvin
  3. Hi Natsu, I have asked some of our applications engineers about this; they will get back to you here on the Forum. Thanks, JColvin
  4. Hi Paddy, I believe the support is actually in reverse, the ARC CPU's support certain JTAG cables. So if the ARC5 CPU does not recognize the JTAG HS2, you would need to contact Synopsis to see what could be done to add support for it. Thanks, JColvin
  5. Hi Greg, I personally don't know the answer to your question, but the engineer best suited to help you commonly checks the Scopes and Instruments sub Forum so you should hear a response back from them in a reasonable time frame. Thanks, JColvin
  6. Hi ttrostel, Thank you for sharing what you've found! I've let our applications engineers know that there is a need out there to update the appropriate documentation. I know it's been on the list to update so hopefully this will get it pushed higher up in priority. Thanks, JColvin
  7. For other users reading this thread, this question being handled on a different channel.
  8. Hi buckd, I talked with some of our applications engineers and they agree with Dan that there is potential for the FPGA to have become partially unsoldered. I would recommend contacting Digilent Support at support @ digilentinc.com for warranty and repair. Thanks, JColvin
  9. JColvin

    A lot of wf32

    Hello, I have asked some of our applications engineers about this; they will get back to you here on the Forum. Thanks, JColvin
  10. Hi Tuan, I have asked some of our applications engineers about this; they will get back to you here on the Forum. As a clarification though (I'll update the reference manual to make this more clear) the RXD and TXD are from the perspective of the embedded FTDI chip on the PmodUSBUART. So, Pin 2 (RXD) is data flowing from the host to the Pmod, and Pin 3 (TXD) is data flowing from the Pmod to the host. Thanks, JColvin
  11. Hello, I'm not seeing any of your images, but if your are doing this in simulation in SIMetrix, it may be best to contact their support team for their software since I doubt any Digilent employee is familiar with that particular software. Thanks, JColvin
  12. Hi buckd, That is strange phenomenon. Since you've been using it pretty extensively I'm going to guess it's not an xdc file problem. I'll ask some of our applications engineers to see what they think. I don't quite understand the touching the top of the FPGA acting as a button though. Do you mean that you can touch the FPGA and have an LED turn on or am I misinterpreting what you saying? Thanks, JColvin
  13. Hello, I have asked some of our applications engineers about this to see if they can provide some information about this. Thanks, JColvin
  14. JColvin

    Digilent USB - no connection

    Hello, I have moved this question to a more appropriate section of our Forum. I am personally not certain what you need to do next (I have asked some of our applications engineers for further input), but I do know that the Digilent USB JTAG Cable is not the standard USB cable; it is it's own programmer. Thanks, JColvin
  15. JColvin

    Newbie Question

    Hello, I have moved your question to a more appropriate section within our Forum. You do not need to have an additional board or shield in order to be able to run a servo or DC motor from a Raspberry Pi; it will be able to produce all of the necessary signals itself. Since you would be using LabVIEW (and LINX) to run the Raspberry Pi and interact with various devices, I would recommend checking out this tutorial series from LabVIEW MakerHub here. It is for the SparkFun Inventors Kit rather than the LabVIEW Interaction Parts Kit, but because of the way LabVIEW and LINX interact with each other, you will be able to develop the same code within LabVIEW, and tell LINX to target and program whichever board you are using. LabVIEW MakerHub has a tutorial series for getting LINX setup with a Raspberry Pi here. Let me know if you have any more questions! Thanks, JColvin
  16. Hello, Please check out this other question that I've moved to this thread for further responses. Thanks, JColvin
  17. Hello, I have moved your question to the Scopes and Instruments section of the Forum where the engineer best suited to answer your question can see it. In the mean time, I would recommend checking out these two threads here and here. Thanks, JColvin
  18. Hi Krizzle, It looks like you've done all of the right things that I am aware of. The engineer best suited to answer your question commonly looks at this sub-forum, so you should hear back from them in a reasonable time frame. Thanks, JColvin
  19. Hello, As a follow up question, what power jumper setting are you currently using on J3? I believe you will need to switch the jumper to the UART setting in order to be able to program the board successfully through MPIDE. Thanks, JColvin
  20. Hi Pasquale, Yes, that is correct; you are able to have a stand alone VI on the RPi2. Thanks, JColvin
  21. Hello, Unfortunately, Digilent does not have a Step file for that connector at this point in time. We would like to be able to have a step file it in the future, but I personally do not know when that will be. Thanks, JColvin
  22. Hi bellizima, Yes, both of those libraries do still use plib.h. In MPIDE (not the Arduino IDE) was able to comment out the plib.h and have all the code examples compile successfully (I only had to create an absolute value function for one of the libraries, the rest I could just comment out the inclusion). But, when I did the same thing in the Aruduino IDE environment (using Arduino IDE 1.6.9) while plib.h seemed to not be a problem I started running into a lot of compilation issues with int's vs uint8_t's and the like. I attempted to work around this for the Oled (since the Basic I/O Shield Oled and the PmodOLED libraries are the same since they use the same display) for awhile, but was unable to resolve all of the issues. If I get the opportunity, I'll try to restructure the PmodOLEDrgb library to be compatible with the PmodOLED and the Basic I/O Shield in the Arduino environment since it does not use plib.h and I'm hoping that there will be minimal tweaking to make sure the correct commands are sent. Otherwise, I would also like to add support for the "standard" SPI library rather than having it solely rely on the DSPI library since Pmods should be compatible with any system board. I doubt I'll have much time in the near future to work on this, but it is something that I would like to see done, so I'll see if time can be made for it. Thanks, JColvin
  23. Hi malkauns, I have asked some of our applications engineers about this; they will get back to you here on the Forum. Thanks, JColvin
  24. Hi Harm, I have asked some of our applications engineers about this; they will get back to you here on the Forum. Thanks, JColvin
  25. Hi woozle, I have asked some of our applications engineers about this; they'll get back to you here on the Forum. Thanks, JColvin