JColvin

Administrators
  • Content Count

    3303
  • Joined

  • Last visited

  • Days Won

    115

Everything posted by JColvin

  1. Hi, The Ethernet PHY demo is getting close to completed once some timing constraints are ironed out to help keep the demo solid. The advanced microblaze design that Sam mentioned is also getting worked on; however, the person working on it has limited time to work on due to finals week approaching at the local university. We'll let you know when those are completed and available. Thank you for your patience, JColvin
  2. Hi ricardo_lara_gomez, Yes, because the PmodCLP uses a parallel communication style, the Basys board (the Spartan 3E 250K) will be able to communicate with it. Thanks, JColvin
  3. No, unfortunately, this goes beyond my realm of expertise, but I'll try to get somebody else to take a look at it. Thanks, JColvin
  4. Hi eron93, I would recommend checking out our Getting Started Guide for the Zybo in the "After the Out of the Box Demo" section. Thanks, JColvin
  5. Hi iratidance, I think I see your issue. In your 2channel main under the Write Data for your FSM you have the line where your cnt_1 does not go all the way up to the 16 bits. Hope this helps! Thanks, JColvin
  6. Hi neryggc, According to the schematics of the PmodAD2, there are no pull-up resistors on the Pmod. However, with a FPGA you may be able to program its own pull-up resistors on the IO pins. Unfortunately, I don't know enough about FPGAs to know how you might program that. You can always add the pull-up resistors externally though. Thanks, JColvin
  7. Hi GMA, What kind of motor are you attempting to run? A DC motor, stepper motor, servo motor? Thanks, JColvin
  8. Hi hadjovitch, With the PmodAD1, your Nexys 2 board will be receiving all digital signals from the Pmod and one does not generally filter a digital signal. You probably could do it with DSP, but that's well beyond my expertise. What I think would be the easiest to do is set up a small external circuit using discrete components that filters your analog signal before it is ever received by the PmodAD1. Then you wouldn't even need to worry about any additional lines of code. Let me know if you have any more questions. Thanks, JColvin
  9. Hi Paul, Yes, the pictures in reference manual should say J16 and J15 as you see on your board; it has the correct labels of J16 and J15 in the paragraph above, but I'll submit a change for the reference manual for accurate visuals. As for the jumper blocks, it sounds like you have the J16, J15, and JP8 in the right position (presuming you are debugging a PIC24, PIC32, or dsPIC33). Since it sounds like you are using an external programmer, do you have the jumper block on JP2 removed so you aren't using the onboard PIC32? Thanks, JColvin
  10. Hi odougs, Not as of yet. I'll email the support team again to help expedite the process though. Thank you for your patience. Thanks, JColvin
  11. I got a response from our chipKIT guy, he said the ADC on that particular chip is pipelined and so will only achieve the rated data output rate when streaming. MPIDE is currently set up for a single conversion and a lot of time is spent in code priming the pipeline. They are working on getting this more streamlined though. Thanks, JColvin
  12. Hi Boopathy, Waveforms does not currently support I2S directly but you can measure it indirectly: check this post on our forum Thanks, JColvin
  13. I agree, brick power supplies are a lot friendlier to use especially once you start getting into those higher voltage and wattage ratings. I've seen some 12V 36W wall wart (as we call the plug packs in the US) that would probably work nicely for the Zedboard, but we don't stock them. The only 12V power supply accessory I see is the PCIe one, but from what little I've looked at graphics cards, I know that PCIe power can get picky fast. I'll mention those brick power supplies to appropriate people here at Digilent though since I think there is a potential need for them. Thanks for the feedback!
  14. Hi Phil, I have forwarded your question onto our support team who will get back to you here on the forum. Thanks, JColvin
  15. Hi odougs, I have forwarded your question onto our support team who will get back to you here on the forum. Thanks, JColvin
  16. Hi c64, I personally don't know what the rate would be for 8-bit or how one would somehow adjust the internal ADC to only do 8-bits. The SPI clock should be fast enough to get that data rate though. As for the updated chip, it looks Microchip made the chip in production (as opposed to pre-production) earlier this April and the featured list and datasheet seem to list that at least 1 ADC can get up to the 500 ksps. I don't know the details on a corresponding Wi-Fire board on the Digilent side though. Thanks, JColvin
  17. Hi c64, I know the pre-production engineering silicon that comes on the Wi-Fire board had some issues including the ADC not being able to perform at the specified rates (see Microchip's errata and datasheet clarification). However, you should still definitely not be getting that slow of rate; I've contacted our chipKIT support about this and he should get back to me early next week. Thank you for your patience. Thanks, JColvin
  18. Hi Jo, The clock frequency of SPI will (most likely) be limited and determined by the on-board ATmega48 that is embedded into the PmodCLS. Looking at the datasheet, it appears that the chip has a default clock frequency of 1MHz. But since the SPI clock will need to driven a little slower to ensure that the Atmel chip is able to perform all of the necessary processing on the incoming information, it seems that the maximum SPI clock speed is 625 kHz, as per the example code that is available for the PmodCLS. Naturally, you can also drive the clock slower if you so desire. The power requirements for the Pmod will be dependent on both the ATmega48 and the LCD screen. The screen appears that it has a typical power draw of 16 mW (based on the typical supply voltage and current). The ATmega48 according to its Electrical Characteristics section will draw up to 3.5 mA of current at 3V, so about 12 mW, for a total power draw between the two of less than 30 mW. Let me know if you have any more questions. Thanks, JColvin
  19. Great, I'm glad it worked out for you.
  20. Hi rbharvs, It might be enough of a difference between boards to have that issue; the page for this demo looks very similar to the one for the Nexys 4 DDR, but maybe it's different enough. Let me know how it goes. Thanks, JColvin
  21. Yes, I think the file was accidentally stored in a location that was inaccessible to the public. I re-uploaded it in a different location though, so you should be able to download it now. Let me know if you have any more questions. Thanks, JColvin
  22. Hi c64, It was recommended to me that you try downloading one of the newer MPIDEs from 2015-01-30 or newer. These apparently have the MRF libraries incorporated into them. Let me know if you have any more questions. Thanks, JColvin
  23. Hi Hamid, I think I found the potential issue that you're running into, which for some reason is not mentioned at all inside the provided manual. The PmodLS1 has the small orange/yellow knob that is the gain factor for that Pmod and controls the sensitivity of the sensors. If it is rotated too far to one side or the other the sensors will be either too sensitive so that they are always on or too insensitive so that they are always off. I would try rotating the knob until those four LEDs on the PmodLS1 turn on again, indicating that they are sensing the infrared being reflected off the white(ish) floor. This should hopefully make your robots turn on since the code only lets the robots turn on when the button is pressed or if some of the light sensors are sensing something. Everything else about your design seems to be done perfectly. Let me know how it goes. Thanks, JColvin
  24. Hi Team21, As zygot mentions, the current draw will be dependent on whatever peripherals you are running with the ZYBO board. As a reference though, in the ZYBO reference manual it recommends that if you are using a 5V "wall wart" power supply that it is able to provide at least 2.5A of current. You could use a more powerful 5V supply that allows for higher current draws if needbe. If you are concerned about running too much current/power through your ZYBO power rails to power all of your peripherals that you have going on without running into overheating issues, I would recommend trying to power any external applications with their own separate power supply. If everything you are doing is already built into the ZYBO board, then I believe a 5V 4A wall wart power supply will be plenty for your needs, but a 5V 2.5 power supply might also work. Again, it depends on how much current your design requires. Let me know if you have any more questions. Thanks, JColvin