• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by JColvin

  1. Alex, Is this the right link? None of the projects listed there seem to offer any support for Vivado... Thanks, JColvin
  2. Hi peason, Yes, the Cmod S6 will fit in a standard 48 pin DIP socket. According to the Overview section in the Reference Manual "There are 46 FPGA I/O signals [and a pair of Vcc and Ground] that are routed to 100-mil-spaced through-hole pins, making the Cmod S6 well suited for use with solderless breadboards". Also, the USB port is placed on the centerline of the board. Let me know if you have any more questions. Thanks, JColvin
  3. JColvin

    Pmod Ia Parts

    Hi stevew, The package size for both of the capacitors are 0603. Correspondingly, the package size for the resistor is 0402. We'll be sure to update the reference manual to include these sizes in case somebody does want to add their own oscillator, just as you do. Thanks, JColvin
  4. Hi James, There is an ethernet demo for the Genesys board available here, which should help show some of the basic concepts behind the Ethernet protocol. Which FPGA are you using? Thanks, JColvin
  5. Hi LariSan, I think it looks pretty good. There are only two other things that I would want to know when looking at this diagram, although I don't know if a pinmap diagram is designed to/ purposed for these things. The first thing I would want to know know in terms of signals is where the major communication pins are (that go with the default communication protocol on the PIC32MX150) such as SPI, I2C, and UART. The second thing, which ties in with the first, is what pins are specifically available on each of the Pmod headers and where they are located. For example, Header J1 has the default SPI port, as well as an external interrupt on DIP pin 7, and header J2 has the UART2 pins, a pwm capable pin, and SPI2 pins. Thanks, JColvin
  6. JColvin

    Computer Build 5

    Do you know what the issue with the power supply was?
  7. JColvin

    Nexys 3 With Pmodrf2

    Hi Marty, We do not have anything at this point in time for the PmodRF2. We do have a design for a Spartan 3 with the PmodRF1 at the bottom of but I'm not sure how portable this is to the Spartan 6 and PmodRF2. We would like to get a demo up and running for it, but we haven't had the opportunity to devote the resources to get the various software stacks from Microchip from C into VHDL. Let me know if you have any more questions. Thanks, JColvin
  8. Hi researchscholar24413, I apologize that your post didn't get addressed earlier. For SPI communication you would need to create a chip select, two buffers to hold the incoming data from the PmodAD1 and create a clock signal. One of our users, hamster, has given an example of how you might get SPI going with an analog to digital converter on this post here: Let me know if you have any more questions. Thanks, JColvin
  9. JColvin

    Pmod Ad5

    Please check out the multiple posts in this topic to find out the process for getting the PmodAD5 up and running.
  10. Hi Almost1, ADCs (Analog to Digital Converters) will give you an inputs of 0's and 1's, but because ADCs are an integrated circuit, you would not be able to change the on-board ADC from a 12-bit converter to a 1-bit converter. You could opt to read only 1 bit from the ADC, but it will still take the incoming analog signal and convert it into digital bits. It sounds like using one of the digital inputs on the Pmod connectors would be more suited to your application as it would report to you a '0' when there is no voltage and a '1' when there is a high voltage from your incoming square wave. As for the voltage reference, I don't believe you can change the internal reference for these digital inputs, but I'm more of a microcontroller guy so I'm not sure if would be possible to change those voltage references in an FPGA. The on-board ADC can act as a differential input, so you can compare an incoming signal to your reference signal to determine if the output should be 0 or 1, but there will be limitations on how much voltage you can apply to the inputs of the ADC. As for changing of frequency within your square wave, the Nexys 4 would just need to be fast enough to catch the rising edge of your incoming square waves, so as long as your incoming frequency isn't ridiculously fast, you'll be able to catch when the voltage changes occur via polling (or an interrupt method). Let me know if you have any more questions. Thanks, JColvin
  11. Hi yangz3, Unfortunately, DIgilent does not stock any SMA cables that you could use with the PmodIA. You would have to get an appropriate cable (Coaxial RF cable) from a place like Digikey or Mouser, or some other electronics supplier. If you're having trouble finding a cable that suits your needs, what you could do is get any sort of cable with a male SMA plug on one end and then strip the other end of the cable and attach your own clip to the (probably) red wire which is connected to the pin on the SMA plug. Alternatively, if you can secure a breadboard jumper wire into the hole on the SMA connectors on the PmodIA, you would be able to successfully measure any impedances because the outside "ring" on the SMA connectors are not actually used in the PmodIA design (as per their schematic). Let me know if you have any more questions. Thanks, JColvin
  12. Hi nlupugla, Apparently the Digilent Adept software that I was mentioning does not support connecting to an Atlys board through Ethernet; I apologize for any confusion that I may have caused. After talking with support, Digilent does not personally offer any software to gather information from an Atlys board, so we would not be able to offer support for the particular software you might happen to be using. Generally speaking though, this is what I learned from our support team: I hope this helps out! Thanks, JColvin
  13. Hi nlupugla, I believe it would be possible to get multiple Atlys boards connected to a PC if each board had its own instance of the Adept software. You would then be able to program all of your boards separately and receive data from them through their respective Adept screen in parallel. I'm not sure on the best practices for this or possible alternatives, but I will find out more information and get back to you. Let me know if you have any other questions. Thanks, JColvin
  14. Another fix that you could probably do is just get rid of the sys/ from the #include entirely, so that you only have the line #include <attribs.h> There only is one "attribs.h" file in all of MPIDE that I can find on my windows computer, and the OLED demo compiled just fine without the sys/, so I'm curious as to why the sys/ (or sys) was there in the first place.
  15. I just tried the windows version of that library with both slash directions and MPIDE seems to be happy with either direction.
  16. The older first library (oledlibrary1) can be removed from the project listing. The only difference between it and the newer library is that the newer one supports the chipKIT Cmod.
  17. Hi shrestha, I'm doing well. From what I remember of creating a PID controller it will certainly be easier with just one sensor, but presuming you are balancing a ball on a some sort of platform where you can rotate the board on two different axis' (e.g. the x and y directions), then I would recommend using two sensors with one lined up along one axis and the other lined up along the other axis. As for interfacing the PmodAD1 with the Nexys 3, I am personally not very familiar with VHDL or Verilog, but there are examples at the bottom of the Nexys 3 product page that demonstrate how you might implement SPI (in Verilog or VHDL) onto the Nexys 3 with the PmodACL and PmodJSTK demos. There is also another forum post that explains how you might implement SPI onto an FPGA in VHDL Let me know if you have any more questions. Thanks, JColvin
  18. Hi LariSan, The second newer library, oledlibrary2, is the correct library in order to use the PmodOLED with the chipKIT Cmod since it has the appropriate SPI pin declarations in its driver file. Are you sure that the PmodOLED is plugged into the chipKIT Cmod correctly? The two Pmod headers have a reverse orientation from one another, so it's easy to get something accidently plugged in backwards; I know I've done that. Let me know if you have any more questions. Thanks, JColvin
  19. Hi Rick, After looking at the Microchip DV102412, I believe you would be able to program it in MPIDE, by selecting the chipKIT WF32 as your board because it has the same chip (PIC32MX695F512) as the DV102412. However, the DV102412 does not have a USB port to plug into. If you have an FTDI chip, such as the FTDI232RQ available on Digilent's PmodUSBUART, you could then potentially program from MPIDE to the appropriate expansion pins (RX and TX) that you can find on the module (according to it's user guide anyway). The tricky bit and what will take some effort is checking to make sure that those UART pins on the expansion pin set go to the same UART port on the PIC32 port pins as the WF32, and then having to load the bootloader onto the chip. I have not personally tried what I have described, but I think it should work (at least in principle). It may be easier to program the Max32 through MPLABX (the MPLABX IDE that you mentioned) so that way both boards are programmed from the same IDE. Let me know if you have any more questions. Thanks, JColvin
  20. Hi, After talking with the support team, this particular project has been having issues when attempting to get it updated to newer versions of Vivado. As per their response, we're hoping to have a fix sometime in the near future. Thanks, JColvin
  21. If two of the wires need to be driven high or low in order to measure a coordinate direction, then no, there is not a way that you could measure the Y+ voltage and the X+ voltage simultaneously from your 4-wire display. The Pmods themselves do not need to receive any special coding; all they need is the analog voltage signal coming from one of the four wires and could theoretically be able to collect the Y+ voltage and the X+ voltage within 1 us of each other. The only potential issue that I can see (I don't know if you have addressed it already) is having the FPGA set an input reading your Y+ line, but a different FPGA line as an output powering the Y+ line when you are reading the X+, potentially creating a short circuit. I am not an FPGA expert, but there may be a way to set FPGA inputs to a high impedance state to help avoid any problems. Let me know if you have any more questions. Thanks, JColvin
  22. Hi Mike, As per Larissa's there are plans to make a Nexys4-Video board that will sport an Artix-7 and an HDMI port, but it isn't released yet. Thanks, James
  23. Hi Mike, Thank you for the feedback! As you probably know, we do offer a low cost board that has the HDMI I/O on it, the ZYBO-Zynq-7000 board, although I can't personally speak for how efficiently it is able to process the data with its on-board DDR3 memory. I don't know what the intentions are for the next Basys / Nexys models are in terms of a HDMI port, but I definitely think that would be a helpful asset since, as you say, there are multiple reasons why a digital port is much more appealing. Thanks, JColvin
  24. Hi shrestha, I have personally have not used the FTAS00-57AS4 before, but yes you would be able to convert the outcoming signals from the touch screen to digital signals through the PmodAD1. The only potential issue that I see with using the PmodAD1 is that this particular Pmod only has two analog inputs, so you would need to use two PmodAD1s in order to collect all four analog data lines from the the touch screen. What might be easier (in my opinion) would be to use a different module that is capable of collecting four different analog inputs by itself such as the PmodAD2 or the PmodAD5. The potential drawback with using these modules though is that each of the four analog inputs would be converted to a set of digital signals one at a time as opposed to all of them being converted simultaneously. This will inevitably introduce a small time delay between each of the data samples taken so that there is a chance that your finger or whatever is touching the screen has moved since the last acquisition of data. However, this time delay would be at the largest extreme would be less than 1 millisecond from the first to the last data chunk out of the four sets and most likely far less time, so it would depend on your application for how concerned you are about this time difference between reading your four analog wires. Two PmodAD1's on the other hand could collect and convert all four analog signals simultaneously. In terms of interfacing the Pmod with the Nexys3, you would need to provide the Chip Select line and the Serial Clock signal to the Pmod so that each of the 12 data bits are correctly clocked out of the with the first 4 bits acting as leading zeroes and the remaining 12 bits as the 12 bits of digital data, as per the AD7476A by Analog Devices that is present on the PmodAD1. The last bit, which I do not know the answer to, is that you would need to have a way to convert the bits of digital data coming into the Nexys3 into the x and y coordinates representing the screen is being touched. Let me know if you have any more questions. Thanks, JColvin
  25. The gearbox motor is designed to nicely plug in to the PmodHB5. So the pinout (based by color) is as follows: Black wire ---- Motor (-) Red wire ---- Motor (+) Brown wire ---- Vcc Green wire ---- Ground Blue wire ---- Sensor A Purple wire ---- Sensor B However, by nature of DC motors, you may switch the locations of the Motor (-) and Motor (+) (physically and/or mentally). What this will do is have your motor now run backwards when it was running forwards before and vice versa. Similarly, you may also switch the locations of Sensor A with Sensor B. What this will do is change which sensor reports information first to the system board, depending on which way your motor is rotating. As the user, you would find out by testing which sensor reports its information first when the motor is spinning a particular direction. Unfortunately, this pinout diagram is not available on the motor/gearbox page at this time; this will be amended soon. Let me know if you have any more questions. Thanks, JColvin