• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by jpeyron

  1. Hi qiny9, That looks correct for the setting. I believe the INIT_4A is used to enable the averaging as shown on pg 22. The XADC Software Support, page 82 also gives more information about this. It looks like you would also be able to use the XADC wizard as well described in here(the XADC wizard manual). cheers, Jon
  2. Hi qiny9, If you are wanting to use the averager in the xadc there is 16, 64 or 256 samples as shown below. If you are wanting to average at 128 samples then you will need to do that after the xadc like how D@n had suggested. cheers, Jon
  3. Hi Muqeet, Here is a link to the Terms and Conditions for Digilent products which includes information about warranties. Here is the reference manual for waveforms 2015 for the AD2, here is the reference manual for the AD2 and here is the reference manual for the Nexys Video. Also here is a link to our github for the Nexys Video as well. If you are concerned about accidental damage i would suggest to read the reference manuals for Waveforms 2015, the AD2 and the Nexys Video to help avoid this situation. cheers, Jon
  4. Hi Muqeet, Welcome to the forums!! Here is a link to some resources for FPGA's and Analog circuits using the Analog Discovery. Here has multiple tutorials for the Nexys Video and here has multiple tutorials for the Analog Discovery 2. Hope this helps! cheers, Jon
  5. Hi Hi TK SAIDI, Unfortunately, we were only able to get the VmodCAM to work in the 2 resolutions with the 2 different designs. You can get more information about the MT9D112 from here with a partial reference manual of the MT9D112. For more information about the MT9D112 I would suggest to request Micron for the full data sheet. thank you, Jon
  6. Hi TE SAIDI, Unfortunately, we were only able to get the VmodCAM to work in the 2 resolutions with the 2 different designs. I'm glad to here you were able to get the bram to work. You can get more information about the fifo,data transfer and potentially if you'd still need the video timing controller from here with a partial reference manual of the MT9D112. For more information about the MT9D112 I would suggest to request Micron for the full data sheet. thank you, Jon
  7. Mark, Please go to File->Preferences. Select upload for the "show verbose output during" and then click "OK". Next try to upload the program. Please take a screen shot of the console text like shown below and attach it to this thread. thank you, Jon
  8. Hi qiny9, The first thing i would suggest is to use an o-scope and see how much noise is coming out of the transimpedance amplifier. If there is some noise there is a function in the XADC to take an average of the input which is shown on page 45 in the XADC manual here. cheers, Jon
  9. Hi Mark, What OS are you running? What FTDI driver version do you have installed? I have screen shots of my driver and com port from the device manager. I am running windows 8.1. Do you have any other boards that you are able to use with the Arduino IDE? Im also curious about the the "error downloading" on the bottom of the board manager page. thank you, Jon
  10. Hi mark, Do you have either the chipkit core v1.3.0 or v1.3.1 as shown below? This new version included the update to the bootloader host application “pic32prog" which was causing this situation. thank you, Jon
  11. Hi digizybo, The usb port is enough for the hello world demo. Also you can use your cell phone cable as long as the cable also allows your cell phone to communicate to your computer. Some cell phone cables only do power and not communication as well. thank you, Jon
  12. Hi Digizybo, The USB A to Micro-B Cable(prog uart) will power the zybo for the hello world project. If you wanted to get a wall wart power supply you can find the requirements here on page 4. We sell a wall wart power supply here that can be used with the Zybo. thank you, Jon
  13. Hi chris, I'm not sure why you are having one part of the if else at 1.5us and the other at 458us using the _CP0_GET_COUNT() function but i would use the debugger in MPLABX and step into the send_strip function and see what is going on. I believe the 1.55 us would be start+38 and the .78us would be start+31 as shown below in the function. Here is a library for mpide that uses the uno32 and 24bit neopixels that might help. I know that they ended up using assemply with no-op's to get the timing down. Hope this helps! cheers, Jon void send_strip(unsigned int data) { int i; unsigned long long j=0x800000; for (i=0;i<24;i++) { if (data & j) { PORTFbits.RF1=1; start=_CP0_GET_COUNT() ; while(_CP0_GET_COUNT()<=(start+38)); //40MHz=> period is 25ns...neded this to be 1.55us PORTFbits.RF1=0; start=_CP0_GET_COUNT() ; while(_CP0_GET_COUNT()<=(start+31)); } else { PORTFbits.RF1=1; start=_CP0_GET_COUNT() ; while(_CP0_GET_COUNT()<=(start+31)); PORTFbits.RF1=0; start=_CP0_GET_COUNT() ; while(_CP0_GET_COUNT()<=(start+38)); }
  14. jpeyron

    Debugging with Chipscope

    Hi Deepika, Are you following the process described on pg 125 of the reference manual for chipscope here? Cheers, Jon
  15. Mark, I got the error you were describing if i did not choose a com port. Just to verify, you have already choosen the correct com port as shown below? Also i have included the chipkit blink which i was able to get working on a MAX32 a couple of minutes ago.
  16. Hi Boscoe, The Nexys Video is capable of having audio with the HDMI. We have not created any demo's or tutorials that incorporate the audio in the HDMI. One of our community members Hamster has many completed projects here. He has an hdmi with audio project using the Nexys Video here with the files here at his github. Hope this helps! cheers, Jon
  17. Hi Mark, First, make sure to have arduino 1.6.12(newest version) installed. Secondly, have downloaded the most current version of the chipkit cores. Also make sure that you have selected the correct board as shown below. Let us know if this does not fix the issue. thank you, Jon
  18. Hi roujesky, Unfortunately, we do not have experience with the bootloader for the Fubarino board. I would suggest asking your question on the Fubarino ChipKit forum here. The wiki here also has more information about the Fubarino board although i did not see anything describing the bootloaders specifics. cheers, Jon
  19. Hi 2425842447, You should have the firmware in a pm as discussed in the thread here. The issue appears to be resolved. If not please use this thread for further comments. cheers, Jon
  20. Hi Derek, I might have been reading the reference manual wrong. I have been searching and as of now I'm unable to find specifics to exact pulses per rotation it seems to be either 1 or 3. I was able to find two different projects that compute the rotations using the sa and sb and i have attached them below. Hope this helps! thank you, Jon
  21. Hi Derek, Sorry for any confusion the reference page for the PmodHB5 caused. I looked here to get more clarification of the magnetic encoder reference page here. thank you, Jon
  22. Hi Derek, Logic high is set to CCW as shown in the datasheet here. I took a screen shot of the life cycle. Also when the motor is mounted as part of this robotic kit to go forward it is CCW for one of the motors and CW for the other. While looking at the encoders datasheet it appears that you are correct with 3 pulses per revolution. thank you, Jon
  23. Hi D@n, My understanding is that Xilinx provides the JTAG user commands for each device in their documentation but you will still have to use SDK to talk to the jtag device chain. thank you, Jon
  24. jpeyron

    Short circuiting MDIO

    Hi yui202, Here is a thread that talks about possible damage and ways to potentially troubleshoot using the JTAG. Another way is to find a completed demo that uses the MDIO to test the boards funtionality. Unfortunately, i haven't been able to find one as of yet. For your second question, I am not aware of a program that automates test bench generation. Maybe someone in the forum community is aware of such a program. thank you, Jon
  25. Hi brycecrapse, While i look through your logs and see if i can find anything, what is you display settings from where you are supposed to be getting HDMI signal? thank you, Jon