Jump to content

JColvin

Administrators
  • Posts

    6,673
  • Joined

  • Last visited

Posts posted by JColvin

  1. Hello,

    I'm not familiar with board you mentioned, but if the device uses a Xilinx Zynq 7010 (and otherwise has an appropriate JTAG topology) then it will be compatible as per the JTAG HS2 Reference Manual containing the list of compatible devices provided by AMD: https://digilent.com/reference/programmers/jtag-hs2/reference-manual#supported_target_devices.

    The main caveat I can think of is that the JTAG HS2 does not have a pin connection for the PS_POR_B to reset the ARM core processor, so you will be limited in that regard for debugging processes for the Zynq board, though you can still load bitstreams. The JTAG HS3 does have this pin however.

    Edit: I look up this board. There is a physical problem: the 2x7 JTAG header this board has uses 2.54 mm spacing rather than the 2.00 mm spacing that the Digilent JTAG HSx devices and the Xilinx development boards use. You would need some sort of converter to account for this physical difference. This thread discusses some of the options here:

    Thanks,
    JColvin

  2. Hi @Salvador G,

    The onboard FTDI chip on the Basys 3 allows for JTAG communication; that is how it can configure the FPGA: https://digilent.com/reference/programmable-logic/basys-3/reference-manual#usb-uart_bridge_serial_port.

    I do not know the specifics of your setup, but the Adept SDK (part of the Adept download: https://digilent.com/reference/software/adept/start) has a JTAG subsection that might be of help to you.

    Let me know if you have any questions.

    Thanks,
    JColvin

  3. HI @Obsidian,

    You have done everything that I would have attempted. I'm still on Windows 10, but I confirmed with the Adept developer that Adept will work on Windows 11 (or at least they have been using a fresh install of Windows 11 for over a year with no issues).

    What sort of processor are you running on? An x86-64 or an ARM?

    Thanks,
    JColvin

  4. Hi @Joe306,

    Xilinx/AMD curated and provided the following list of target devices that is supported by the JTAG SMT2, which does include the Versal ACAP: https://digilent.com/reference/programmers/jtag-smt2/reference-manual#supported_target_devices.

    As for your schematic, I don't see anything problematic. Your ESD diode based on its datasheet has low enough capacitance to not interfere with USB communication and it looks like you have appropriate protection for any in-rush current coming in on the USB., and otherwise more or less matches the example layout shown in Figure 12 in the Reference Manual, https://digilent.com/reference/programmers/jtag-smt2/reference-manual#application_examples.

    Let me know if you have any questions.

    Thanks,
    JColvin

  5. Minor follow up, I looked at the UG475 that zygot referenced, and best that I can tell from Chapter 6 Package Marking, the speed grade used to be its own individual line on the 4th row down, just below the lot code (detailed slightly more in Table 6-1). But based on figure 6-4 for the Artix FPGA (and the equivalent figures for the Kintex and Virtex FPGAs), this is the "Legacy Artix-7 Device Package Marking".

    I'm not certain when this change occurred, but it was a number of years ago as I have Basys 3 Rev C's (Rev D came out in 2021) both with the speed grade marking and without it.

    Thanks,
    JColvin

  6. Hi @dsdsd,

    From what I can recall, no Digilent device uses a FT2232HL. Digilent's programming solution is made exclusively for Digilent boards and so will not be able to restore a different development board from a different manufacturer.

    In terms of just generically erasing material, FTDI's FT_PROG application may be able to help you, though it is also likely a common reason for the many users that ended up posting on this thread to begin with.

    Thanks,
    JColvin

  7. Hi @Taksun,

    Digilent typically uses the FT2232HQ device (such as is mentioned in the Arty A7 Reference Manual here: https://digilent.com/reference/programmable-logic/arty-a7/reference-manual#usb-uart_bridge_serial_port).

    I have not done any research into the 56-pin variant, nor I am I sure by what you mean that it does not work as a Digilent programmer, as that seems to imply you have already attempted to configure the device, though I do not know how you would have done so.

    Regardless, I would not be surprised that with the reduction of pins comes a difference in pin layout as well as register configuration, so I would imagine that Digilent's programming solution as it currently exists would be incompatible with the FT2232H-56Q.

    Thanks,
    JColvin

  8. Hello,

    I had forgotten to update this thread with the reply I received a week later:

    Quote

    The Pcam 5C indeed has DOVDD = 1.8V and it uses the OV5640 internal regulator for DVDD. OV5640 automatically enables this internal regulator upon powerup; there is no other step necessary from software for this.

    Thanks,
    JColvin

  9. Hi @john-con,

    I can confirm that the Arty A7 and Basys 3 both use speed grade 1 components.

    I'm not certain off hand where you would readily determine this off of the chip labeling itself, but you can see the critical "-1" portion of the FPGA name in the right hand side of their respective Resource Centers, https://digilent.com/reference/programmable-logic/arty-a7/start and https://digilent.com/reference/programmable-logic/basys-3/start, of the "FPGA Part #" row.

    As far as I know, zygot is correct that only Digilent's Genesys 2 has a speed grade 2 part.

    Let me know if you have any questions.

    Thanks,
    JColvin

  10. Hi @arang,

    Not in the Protocol tool specifically, but you can adjust the drive strength, slew, and pull values of the IO pins either through the Supplies instrument or through the Settings -> Options -> DIOs tab.

    image.png

    I'm not certain what you mean by duty cycle specifically, but you can change both the System Clock frequency that the Digital Discovery uses at large though those same settings, or you can change the frequency of whatever protocol you are using through the (user typeable) dropdown within the Protocol tab of interest as well.

    Let me know if you have any questions.

    Thanks,
    JColvin

  11. Hi @idegani,

    As far as I am aware, it's not possible to have a particular configuration loaded on power up as the on-board FPGA will not maintain it's configuration once power is disconnected.

    The workaround that might work for you would be to use the "Continue" option for what the device does when WaveForms is closed within the WaveForms Device Manager. As long as the device is still receiving power (either over USB or via an external supply), the device will continue to operate in whatever configuration/state it was last set in. I routinely use this when I'm testing other devices but want to limit the total USB activity and ports I am using.

    image.png

    There are a couple of other threads that discuss this option here:

    Let me know if you have any questions.

    Thanks,
    JColvin

  12. Adding on to what zygot mentioned, you'll find that many mobile phones will also randomize their MAC address when connecting to a WiFi network by default (Android has some information on it here: https://source.android.com/docs/core/connect/wifi-mac-randomization-behavior), because (in my limited understanding of network operation at large) this would be a localized address within that subnet, so the odds of matching somebody elses MAC address within that same small amount of devices is quite small.

    Regardless, localized or unique MAC, you'll have a bad time if there is a match as the different communication frames will end up at the wrong device, so that neither device works properly.

    But that is about as far as my knowledge goes on this particular topic.

  13. Hi @CG73,

    The Analog Discovery 3 does not come with any sort of calibration certificate/report.

    However, the individual calibration values are stored within the device and can be viewed within the WaveForms Device Manager by clicking the "Calibrate" button. From there you also have the option to individually calibrate different instruments, or to reload the factory calibration as needed for your device. Digilent does not have any specific recommended calibration schedule. There is some additional information in the WaveForms Help tab here:

    image.png

    Personally, I recalibrate my device before I start doing a larger project with it.

    Let me know if you have any questions.

    Thanks,
    JColvin

  14. Hi @Jerin James,

    The Eclypse Z7 board does need to have the 12 V external power attached and board powered on before the corresponding FTDI chip and the downstream Zynq device to be detected by the Vivado Hardware Manager.

    Presuming you have it powered, is the Digilent Adept software, https://digilent.com/reference/software/adept/start, able to see the Eclypse Z7? (I'm asking specifically for Adept since the Vivado software suite uses the drivers that come from Adept, so this is the effective equivalent of installing the drivers from source).

    If Adept does not see the board either, what do you see in the Windows Device Manager / kernel output with dmesg (depending on the OS)? An example of what you should be seeing in Windows is in this post, and a similar one for Linux is here.

    Let me know what you find out.

    Thanks,
    JColvin

  15. Hi @Hiroaki,

    This is detailed some in the troubleshooting guide,

    but if you know that you erased the FTDI chip, you may be able to recover it from the WaveForms Device Manager. Go to the More dropdown and select ProgAD1,2,3,ADS,DD in the menu option and then follow the directions.

    I'm not certain what version of WaveForms you might be using since you are using the original Analog Discovery, but the latest version is freely available and supports it here:

    Let me know how it goes.

    Thanks,
    JColvin

  16. Hello,

    Digilent sells a compatible cable on our store here, https://digilent.com/shop/usb-a-to-micro-b-cable/, but in theory any micro-B cables that support USB 2.0 speeds should work fine. The two cables that I use daily at my desk don't have any branding marked on them. The benefit of buying/paying for shipping for the USB cable from Digilent would be that if you still experience disconnect issues is that it would quickly narrow down the possible points of failure.

    I don't know when/where you purchased the Cora Z7 (I don't have access to such data), but it's my understanding that when purchasing an FPGA from Digilent, you can optionally choose to add the appropriate USB cable for free to the purchase (the button for that is directly below the price listing; example on the Basys 3 page here: https://digilent.com/shop/basys-3-artix-7-fpga-trainer-board-recommended-for-introductory-users/). This looks somewhat easy to miss though, so I'll submit that as feedback to the web team.

    Thanks,
    JColvin

×
×
  • Create New...