• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by JColvin

  1. Hi T22, J18 was added to Rev E of the Max32 to provide additional access to the default I2C pins. The benefit of these two pins (in addition to the same signals already present on chipKIT pins 20 and 21 present on J4) is to allow the chipKIT Max32 to be in the middle of the I2C daisy chain, which is a generally desired physical feature for I2C. I believe this was the only hardware change implemented in the Max32. Let me know if you have any more questions. Thanks, JColvin
  2. I just got nearly all the sound effects (via a small piezoelectric speaker) that I wanted successfully added to the program: a charging sound, an explosion sound, and a losing the game sound. I'll add a superShot sound tomorrow and post the updated code.
  3. Hi, I got a response back from the sales team. They said that you'll need to wait for the combined kit to come out (there is not a definite timeline on this that I am aware of) in order to get the combined kit price. I'm sorry if this is an inconvenience for you. Thanks, JColvin
  4. That would be pretty sweet; I'll have to look into generating sounds from a pwm speaker that aren't musical notes. Or figure out the frequency values of the classic explosion and charging noises.
  5. I finally got some time to design my own Color Invaders project, originally inspired by Hamster's own Colour Invaders project. I ended up writing a lot of my own code for it since I have a personal thing about using somebody else's code in it's entirety, although Hamster's code obviously has a heavy influence on it's overall construction (thank you for posting it!). This game is similar to the classic Space Invaders game, or more closely related to Casio's Number Invaders on the calculator, where you have a stream of incoming invaders of a variety of colors coming down the WS2812 LED strip and you have to adjust the color of your missile to match the color of the first invader via the PmodENC (a rotary encoder). You can check out how I made the project as well as a small video showing some of it in action at http://www.instructables.com/id/Color-Invaders/.
  6. Hi, I talked to our guy that wrote a lot of the ZYBO demo and he said that you can get everything installed on a 4GB SD card, but once everything is all ready, you'll be left with relatively little room to add any extra programs onto the card, so we usually recommend using an 8 GB card so you have a lot more room to easily expand your project. Thanks, JColvin
  7. Hi Abdulrahman, Unfortunately, there are many possible reasons for a licensing issue. If you could provide some more information regarding the specific license you downloaded and the directions you are following, that may help us resolve your issue. Also, the Xilinx site has an extensive FAQ section which may be able to answer some questions you have in the mean time if you want to check those out. Thanks, JColvin
  8. Hi Filipe, It sounds like you're doing things correctly, but as a double check, where do you have your wires hooked up on the A0 and D0 channels? On the inside or the outside? The outside on both the DAC and ADC are connected to ground, so you would not ever see any changes in your output, whereas the inside pin (closer to the silk screen label) would be the actual input/output pin. Thanks, JColvin
  9. Hi, I have moved your question to a more appropriate section on our forum and contacted our sales team about this. Thanks, JColvin
  10. Hi Simon, Going off the forum post you linked to, you will need an 8 GB SD card since the setup requires more than 4 GB. The particular SD card I linked to is the one Digilent used for the development of the ZYBO project. As for the name of the partition, the name itself does not matter very much; it's more so that partition type needs to be correct. Let me know if you have any more questions. Thanks, JColvin
  11. Hi, You may also find this post helpful on creating a 400 MHz clock out of a 100 MHz clock. As for Vivado synthesizing taking awhile, that is (unfortunately) just going to be the case for programming any FPGA. Hamster explains the reasons here. Thanks, JColvin
  12. Cool! Thanks for sharing!
  13. Sweet! Thanks for joining our Forum Radoslaw! If you have any cool projects that you want to show off, feel free to post them in the Project Vault.
  14. JColvin

    Nexys 4 Ring Oscillator

    This isn't directly related to this particular post topic, but you can always upload an image to our Gallery and then link to it from the forum post if you're out of space to upload photos directly. Granted, this isn't quite the same as dragging a photo that you can see within the post, but at least it's something.
  15. JColvin

    PCB MS-8217

    Hi Jorge, We do not actually know the value of the capacitor C23 on the PCB since we do not have access to the schematic of this multimeter. I would recommend contacting Mastech, the company that makes this particular multimeter, here. Thanks, JColvin
  16. JColvin

    Xilinx CoolRunner II CPLD

    Hi, You can find the maximum clock frequencies on page 6 of it's datasheet from Xilinx. I'm not seeing that it has any on-board memory, although I could be wrong about that. Thanks, JColvin
  17. Hi Ryan, Which WebPACK are you trying to to use? The Vivado WebPACK or the ISE WebPACK? I know Vivado does not support the XC9500 CPLD.
  18. Hi, You can set the jumpers of MD2, MD1, and MD0 to the correct setting to enable I2C mode with a corresponding device address of 0x48. Here is a summary of the appropriate jumper settings from the PmodCLS reference manual. For Rev D boards, the jumpers MD2, MD1, and MD0 need to be loaded, unloaded, and unloaded, respectively. For Rev E boards, the jumpers MD2, MD1, and MD0 need to be unloaded, loaded, and loaded, respectively. Let me know if you have any more questions. Thanks, JColvin
  19. Hi Andres.Hortua, I presume you are talking about the Analog Discovery. Did you try using a different USB port/cable as recommend in the troubleshooting post? If your cable is especially long, that could be a potential issue as well. Thanks, JColvin
  20. Cool! We have the Digilent MakerSpace located in part of Digilent's building. The address for it is 1300 NE Henley Ct. Suite 3 Pullman, WA 99163 The MakerSpace is open when Digilent has it's doors unlocked during the normal business hours of 9am-5pm, although we can arrange other times if necessary. We'd love for you to come by if you get the opportunity!
  21. Hi scottcjordan, For your first question, the Chip Select numbers are pin 2 for the ADC and pin 5 for the DAC. I was able to determine this by looking at the analogShield.h file contained in the library that is available for download on it's resource center and by looking at the Analog Shield silk screen. The schematic shows numbers 3 and 6 since it does not start at an index of "0" like the software does. As for the second question; chipKIT boards all use 3.3V for their I/O voltage, and should correspondingly use the 3.3V jumper setting. An Arduino board operates at its own set voltage (either 5V or 3.3V), but you may use the IOREF pin, so that the Analog Shield appropriately uses the reference voltage the Arduino board inherently supplies. Unforunately, there is no easy way to determine the correct jumper setting from the schematic of the Analog Shield because as a shield, it is restricted to the operating voltage of the microcontroller board that it is plugged into; making it up to the user to look for the operating voltage of the microcontroller. Let me know if you have any more questions. Thanks, JColvin
  22. JColvin

    mem util

    Hi, We'll need a little more information before we can effectively help you. What is the mem util software associated with? Adept? What are you specifically trying to do? Thanks, JColvin
  23. Hi, How are you powering your motors? Are you using an external power supply? As for braking, there is no way with this hardware setup to dynamically brake the motors, but there are a few ways that you can emulate braking. You could use a lower PWM value on the "Mode" pin to induce the motors to run at an effectively lower voltage, consequently lowering their speed and emulating a "braking" effect. Alternatively, you could also just no longer provide any power to the motor by driving the "enable" pin to a logic high voltage state so that the motors would quickly coast to a stop. The fastest way to brake to the motors would be to start running them in the reverse direction that they are currently going in. Thanks, JColvin
  24. Hi Lefteris, I can't comment on all of your project (although it does sound cool), but in terms of programming an FPGA to non-volatile memory, you can check these two forum posts that explain how to get the bit stream stored on flash memory for Digilent FPGAs here and here.