Forum Managers
  • Content Count

  • Joined

  • Last visited

Everything posted by Bianca

  1. @FrozenW, Zybo Z7 can be powered through USB only, without a wall supply or a battery. Please look at the jumper position to be set between VU5V0 and USB like on the picture below. Check the markings on the board for the proper way to power the Zybo. You shouldn't have to use your Discovery to power the Zybo. Regards, Bianca
  2. Hi @venkat kulkarni Can see anything in device manager? Does it enumerate in any way when you connect the board? Bianca
  3. I couldn't really say if it's harder or easier but for the Pcam we already provide an IP, example projects and even a workshop documentation. You can see info regarding the camera, lens, projects and what we offer for it on the Pcam 5C resource center page: The IP and demo project are public on our github: Bianca
  4. Hello, Well, the FPGA is the same, so what you want to look at, are the other features like the memory, Audio, Digital I/O. Maybe you also want to use some buttons or switches at some point, and you want them on the board and not as expansion. Between PYNQ Z1 and Arty Z7, the only difference is that the PYNQ has a microphone and Arty Z7 doesn't, otherwise they are identical from the specs point of view. With this in mind, I will talk about the comparison between the Arty Z7 and Zybo Z7... They both have HDMI In and Out, but if you also want Audio codec you can find that on
  5. Hi @mati, You have a private message. Regards, Bianca
  6. Hi @Shalom, In case you want to match the output you'll use the 50Ohm jumper position in order to have adaptation. In this case your amplitude will be divided by 2. In the case you want to use the Gavegen just as a voltage source and don't want to reduce the amplitude, you can leave it to 0V. Regards, Bianca
  7. Hi Leo, That resistance seems to be R18, which is a 100k pull-up resistor for tckc signal... it's in 0201 capsule. Regards, Bianca
  8. Hi Sean, You have the DXF of the ZedBoard attached. Regards, Bianca ZED.DXF
  9. Hi Claudio, The same product will have different codes: 410-XXX, 210-XXX for different stages in the manufacturing process. For example on the PCB you'll see 200-338 that is assigned just for the PCB without the assembly. 210-338 was the assembled device, prototype that went for certification. 410 is the code for the assembled product + package, visible on the website. Since at the time we did the CE test the product was a prototype of the final revision, we used the internal 210-338. Regardless of the initial code, the product is identified with the numbers after the "-".
  10. Hi @[email protected] You have the declaration attached. Regards, Bianca Digital Discovery_CE.pdf
  11. Hi @satvik, Can you please tell me which ZedBoard revision are you using? You can find it labeled on the top side of the board right under the serial number. Thanks, Bianca
  12. Hi @warps, You have the declaration attached. Regards, Bianca Declaration of Conformity_Analog Discovery 2.pdf
  13. Hello, If you are talking about the original Arty or Arty A7, you have below a dimension PDF. Regards, Bianca Arty_Dimensions.pdf
  14. Hi @guoguodian, You have a private message. Regards, Bianca
  15. @rpudelko, Did you select the correct FPGA or board from the boards? This tutorial is made for the original Zybo. It should work but you had to select your own board. Zybo Z7-20 in your case, or if you worked with FPGA parts From the warning you received it seems to me that you selected the wrong part. Regards, Bianca
  16. Hi @iqhamid, please check this topic: Also, try to change the USB cable, try another USB port and not use an external USB hub, eventually you can try connecting it to a different computer to see if you have the same behavior. Bianca
  17. Hi @cnegrea, You have a private message, Regards, Bianca
  18. Hi Enrique, If you don't have the correct drivers, different USB cables won't help. When you open Vivado do a right click on the icon and select Run As Administrator and then try again to call the path. If it doesn't work, contact the person who administrates your computer to install the drivers. If it's your personal computer, try to enable the administrator account from Computer Management. Regards, Bianca
  19. @Fulano, You have a private message with a fix Bianca
  20. Hi @Fulano, Does your device enumerate in windows? Can you see something under device manager when you connect the board? Regards, Bianca
  21. Hi @Yuanlung, You have a private message. Regards, Bianca
  22. Hi @JohnnyG, You can use the board to solder components on it, it has direct connection to the user power supply so you can power your circuit directly from there. However, if you don't want to solder components we placed a small breadboard on the package. You can stick it on the adapter or just place it there. Normally you could use the flywires to connect to a breadboard, but since you don't normally need all the wires and many of them will just get in your way, we placed the right angle connector on the adapter that is directly connected to the Discovery and you can take just wh
  23. @cfowler, Please don't remove the fuse. I'll move the thread to private @asmi, You are right, this shouldn't have happened. I know we have issues with back powering through HDMI but it shouldn't be enough to keep the board working, or burn the fuse or other components. Bianca
  24. Hi @cfowler, Normally, Adept is not build to see the ZYNQ. The fact that it showed the FPGA part, still, shows like something is working. Please make sure that when you try to see the target on Vivado, Adept is closed otherwise Vivado would not recognize the device. If with Adept closed, Vivado still doesn't recognize the target, please check, if in device manager you have the device enumerated when you connect and turn on the board. It should appear as Serial Converter, if it doesn't show up at all or enumerates as unknown device or in some other way, please let me know. If it show
  25. Hi @edwin001, Normally, it should be able to provide the +/- 0.1% with the factory calibration. I can't tell what kind of event caused the device to have a not very accurate factory calibration on certain scales. The good news is that the device is not defective, however, it does imply that if you want to use the user calibration, you have to calibrate the ranges you might use. If you want to have all the the functionality, then all the ranges need calibration Best regards, Bianca