• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by JColvin

  1. Hi MitchG, I personally can't speak for the specs, but Digilent has created the Analog Discovery 2! You can check out an introduction video about it on our YouTube channel. Thanks, JColvin
  2. Yeah, it looks like from the wiki everything is still only in a test build stage, so I'm not sure when a stable release comes out since that'll be up to chipKIT.
  3. Hi cbg, This is something that comes up as a bug of sorts in Vivado (not because of the XDC file). From my understanding the WebPack edition of Vivado (presuming that is what you are using) does not natively come with support for those boards you're seeing (to help keep a lighter install), so you'll continually see those warnings which won't hurt anything, but are annoying as you pointed out. In terms of removing the errors, I asked around and it sounds like there are two possible solutions. One is to uninstall and reinstall Vivado, but install the System Edition rather than the WebPack. It would still be free like the WebPack and would only have the functionalities of the WebPack, but it would include support for those boards already so the errors should go away. Alternatively, you could try reinstalling the WebPack version and seeing if you can check boxes for those particular board types (the Kintex7 and the Zynq) during the "customization" of the installation process and that may help remove the errors. I am not sure as to which one would be the correct approach (I'd personally try WebPack with extra boxes checked) since that'll probably be a faster download, but I personally don't know if it will work as intended. Let me know if you have any more questions. Thanks, JColvin
  4. Hi you, Sorry for taking a little while to get back to you. I would recommend checking out our wiki where we have a demo for the XADC on the Nexys 4 DDR here. Let me know if you have any more questions. Thanks, JColvin
  5. Hi Itheoret, The place to go to make that recommendation will likely be chipkit.net/forum/ although from what I understand, there is going to be some movement away from MPIDE specifically (at least according to their wiki here) so we'll see how that all plays out. In the meantime, you are actually able change the text size in the little black console at the bottom of MPIDE (so I don't have to lean in to read it), the setting is hiding in a different file though. For me, its in the ../main_mpide_folder/lib/theme/theme.txt around line 24 in the "console.font" line underneath # GUI - CONSOLE. Naturally, you'll have to restart MPIDE to see the changes if you have it open, but such is life. Let me know if you have any more questions. Thanks, JColvin
  6. Hi keithkyle, As you noticed, it was built for Arduino 1.6.5, and since chipKIT boards do not specifically implement avr components, you can run into these sorts of errors every now and then. Within MPIDE, the util/delay.h library header file does exist, but I personally don't know how to make MPIDE find it nicely for you. Luckily, we should be able to nicely change the few lines of code that does need this particular library to an alternate delay that is natively supported in MPIDE. What you would need to do is find the mcp2515.c file and open it up with some sort of text editor such as notepad++. You will then need to either comment out or delete the "#include <util/delay.h> that is around line 30 of that file. Then you will need to go both lines 149 (or so) and 327 (or so) and change the "_delay_us" portion of the line to instead say "delayMicroseconds" while leaving everything else alone in those lines. Save your changes and then see what MPIDE thinks when you try to compile the program. Let me know if you have any more questions. Thanks, JColvin
  7. Hi Robert, As Bobby mentioned you need to unzip the file (the chipKIT Network and USB Libs-20150115 file) into your libraries folder for MPIDE. The error you're getting is produced when you copy that whole main folder into the MPIDE Libraries file. Instead, you need to open up the file you downloaded from the Digilent website, open the libraries folder that is inside, and then copy all of those folders (the ones you have shown in your first photo) into the MPIDE libraries folder. Let me know if you have any more questions. Thanks, JColvin
  8. I always thought the encoder on that page referred to the quadrature encoder made up of the two Hall Effect Sensors and capacitors on one side of the motor, in which case the datasheet for the Hall Effect Sensors can be downloaded from the manufacturer's website here. Thanks, JColvin
  9. JColvin

    Go pro 4

    Would what apply?
  10. Hi Roney, I didn't personally create that manual or library for the PmodIA, but I'll do my best to help you out. (the most up to date version of the reference manual, although it is still being worked on, can be found on our wiki here) As you noticed, what you'll first need to do is perform a calibration of the component in order to calculate the gain factor which will then be used in subsequent frequency sweeps. However, as the library currently stands, you are only able to perform a frequency sweep with a certain excitation voltage range (1V peak to peak). To use this default configuration, what you will need to do is apply your "ground" voltage (GND on the Pmod header, J1) to SEL (the J2 pin). We will then to connect a 100k ohm impedance (again, because of how the library currently is) between the J3 SMA connector and the J4 SMA connector. J3 is where the frequency is emitted from the PmodIA, and J4 is where the returning frequency is received by the PmodIA. You can connect to the SMA connectors by an SMA cable if you happen to have one, or you may use a single pin of those 100 mil spaced male pin headers that are commonly used with microcontrollers to put into the central pin of the SMA connector. Within the example code (you will need to use the library provided on our wiki here; I had to make a small change to the existing library that you originally were using to ensure the default setting worked correctly, you will need to make the same changes as before to work with your Arduino board) you will then need to perform the two point calibration (character 'c'). After that, you are free to attach your unknown impedance between the two central points of the SMA connector. However, (again because of this library that I am working on fixing so that the PmodIA can be used to it's full potential) the impedance will have to be between 6k Ohms and 10M ohms (the upper limit) in order to avoid saturating the ADC that is inside the Analog Devices chip (at least according to their datasheet). Let me know if you have any more questions. Thanks, JColvin
  11. Hi DoogieTech, I've asked some of our Applications engineers about this; they'll get back to you here on the forum. Thanks, JColvin
  12. Hi mindcircus, I've asked some of our Applications engineers about this; they'll get back to you here on the forum. Thanks, JColvin
  13. Hi nicanor5, I'm not sure that we have any demos available that take advantage of this, but I asked some of our applications engineers about this; they'll get back to you here on the forum. Thanks, JColvin
  14. Hi monzer0561, Do you happen to have your own custom sensors that you plan on using if you don't have the Lego Mindstorms NXT sensors? The NXT Sensor Adapter that Digilent sells does not have any sensors present on the board -- It was designed specifically to be an adapter so users could connect the Lego Mindstorm NXT sensors to a myRIO. Thanks, JColvin P.S. I moved this thread to a more appropriate section on the forum.
  15. Hi BlazeMicro, I have asked some of our Applications Engineers about this; they'll get back to you here on the forum. Thanks, JColvin
  16. JColvin

    Arty Power supply

    Hi Nick, You are correct, there is no "suitable power supply" available on the Digilent website; I have updated the reference manual to reflect this. I think there may at one point been such a power supply available, but clearly that is not the case anymore. I apologize for the confusion. As an intern, I do not know the answer to the second question. I am working on finding out an answer for you though and will get back to you here on the forum. Thanks, JColvin
  17. JColvin

    Hello! New FPGA user!

    Hi Mavin and welcome to our Forum! This certainly sounds like quite the project you have been tasked with for your final project. What I would recommend is checking out our Nexys 4 Resource Center where you'll be able to find a variety of resources. I would probably look at the GPIO demo and check out there code so see how the get an LED to turn on when a switch is flipped and see if you can rearrange the code so it instead starts working with the seven segment display. Let us know if you have any other questions. Thanks, JColvin
  18. Sweet, I'm glad you got that working out!
  19. Hi Jason, This question will be better suited in a different part of our forum. I've taken the liberty of reposting it in the Scopes and Instruments subsection here. Thanks, JColvin
  20. A user asked this in a different section of the forum but since I'm not seeing a way to just move specific comments, I'm re-posting the question here.
  21. Hi Tarik, I apologize for not getting back to you sooner. Rather than filling out the 4 filters that you were working on, you should instead put the memory type in the search bar underneath the "Selection Configuration Memory Part". You will want the 3.3V single version that will appear when you put the S25FL128S in the search bar. After clicking "ok" on this screen you will need to then select the .bin on the "Configuration file:" line and then click "ok" again. Let me know if you have any more questions. Thanks, JColvin
  22. Hi azn103, The Pmod's (at least the PmodRS232 and the PmodRS232X) are actually both designed as DCE devices. Let me know if you have any more questions for me. Thanks, JColvin
  23. That is correct. The Basys 2 is only compatible with Xilinx's ISE which uses .ucf files. However, the Basys 3 with it's Artix 7 chip can only be used with Vivado which uses the .xdc file. Thanks, JColvin
  24. Hi Bjorn, I looked around on Xilinx's website and it does seem that the Kintex does not include the hardcoded Ethernet MACs, but I'll ask a more experienced engineer for their thoughts and get back to you here on the forum. Thanks, JColvin
  25. Hi Michael, I have asked our Applications team about this; they will get back to you here on the forum. Thanks, JColvin