Popular Content

Showing content with the highest reputation on 11/21/14 in Posts

  1. 2 points

    Basys 3 Bitstream Generation Error

    I already figured out what my error was. If anyone else finds himself/herself in a situation where the bitstream file gives the errors I listed above, just enable the clock pins on the Basys 3 XDC file.
  2. 2 points
    The $10 license is device-locked, meaning that you can only run it on a single FPGA architecture as well as on one single computer at a time. When you generate a license file on the Xilinx website, you're prompted to select a device ID for your machine, e.g., a hard drive or a mac address, which means that unless you return the license to Xilinx via the License Manager, you won't be able to run Vivado with such a license on other machines.
  3. 1 point

    Waveforms For Linux

    We are working on a new cross platform WaveForms software. The beta version of this, supporting Windows, OS X and Linux, will be published soon.
  4. 1 point

    Zybo Rugged Plastic Case

    Hi Cristina, They are on order and we should have some in stock we can send you for samples! We will put them directly into NEW PRODUCTS when we receive them.
  5. 1 point
    Taking note that a cheap xtal is about 50 parts per million, so anything that gives 22.579,200 +/- 1,128.96 Hz (22,578,071 Hz to 22,580,328 Hz) should be 'close enough' to spec that nobody can tell (it makes the difference of 0.2s after playing audio for an hour...). Options a ) Use the clocking wizard to generate a PLL and end up with 22.580,645 MHz (0.23s of error after an hour) b ) Use a PLL Primative, with multiply 7, divide 31 and end up with 22.580,645 MHz (once again, 0.23s of error after an hour) c ) Use one PLL set to multiply 9, divide 35 to give 25.714,285MHz, and feed that through a second PLL at multply 36, divide 41 to get 22.578,397 MHz (0.13s out after an hour) d ) Use three PLLs, multiply 8 divide 25, multiply 21 divide 25, multiply 21 divide 25 to get 22.579,200 MHz - bang on (however I don't think that Nexys3 has enough clock management tiles for this...) e ) Exotic stuff - perhaps use a polyphase filter to resample the 448100 sample stream to different sample rate, perhaps 25MHz / 512 = 48.828,125 samples per second, then use a 25MHz I2S clock, which should at worst add 1 least significant bit of noise - but why would you bother? f ) Add an external clock source that is a more friendly frequency. If I ever need to do anything tricky with clocking, I find it better to use clock management primitives than to use the Clocking Wizard, as you get exactly what you ask for. Once you've done it once it is a lot quicker too!
  6. 1 point

    Pmodals - Ambient Light Sensor

    Thanks for your swift answers! The schematic I had checked before only showed ALS1 as part number for the phototransistor. This solves the mistery! Cheers, JP
  7. 1 point

    Pmodals - Ambient Light Sensor

    Hi jpcastellino, Actually, the part that you're looking for is the TEMT6000X01 by Vishay Semiconductor. Unfortunately, this is not listed on the schematic, but we will be sure to include it in our reference manual on our Wiki site for the PmodALS. Thanks, JColvin
  8. 1 point
    To get the Uno32 Pmod Shield to work you need to do the following: Make sure that in your main MPIDE folder where you originally installed MPIDE under the hardware/pic32/variants folder, you have the Uno32_Pmod_Shield with the C and H files (these are likely there already). If you do, (or do not have them), go to the product page for the Uno32 Pmod Shield, and download the board variants file available. If you did not have the C and H files, copy the "Uno32_Pmod_Shield" folder that you see from the download and paste it into the hardware/pic32/varients folder. Then, from the download, open up the readme text file. In the readme you will see a section that says: Copy this whole section and go to the boards.txt file that is available in the hardware/pic32 folder. Go to the bottom of that text file and copy this whole section in. Then, we need to make the following changes: The first is merely for convenience: underneath the top line of the section that we just copied into the text file which says type in the following: What this does is add the "chipKIT Uno32 with Pmod Shield" option into the chipKIT section when choosing your board in MPIDE. Next, and what makes all the difference, find the line (about 7 lines down) that says: Change this line to instead say: What this does is tell MPIDE to look for a linker script file that actually exists. Now, save this boards.txt file and close out any MPIDE program that you already have running. When you reopen MPIDE, you should see chipKIT Uno32 with Pmod Shield as a board option under chipKIT and the program which uses the Pmod Shield should now successfully compile, and more importantly, successfully run with demo code that uses any of the headers on the Pmod Shield. Please let me know if you have any questions.