JColvin

Administrators
  • Content Count

    3211
  • Joined

  • Last visited

  • Days Won

    106

Posts posted by JColvin


  1. Hi @Tim S.,

    I asked about this and learned that the 512-bit version was originally planned, but never sold. The N25Q bit that was listed on the reference manual became EOL in February 2018

    The current part for this board is a MT25QL256ABA8ESF, though distributors may have the other flash chip. I took a look at the two datasheets for the different chips, but based on the serial number you provided I'm not able to determine which chip variant you have.

    Please let me know if you have any questions about this.

    Thanks,

    JColvin


  2. Hi @Joao Fragoso,

    I apologize for the confusion. The XADC pins are on bank 35 like the MIPI pins, but as per the Xilinx user guide for the XADC; they are only able to handle an input range of 0V to 1V (or -0.5 to 0.5V if you are in bipolar mode), so they are not able to handle the 2.5V LVDS logic. Additionally, to use the MIPI CSI-2 interface, the D-PHY physical layer is needed (as detailed in the Pcam reference manual and the XAPP894 from Xilinx). Since the Zynq 7020 chip (presuming you are looking at the Digilent made Zybo Z7-20) does not natively support the physical layer, though Ultrascale chips do support it natively. Because of this, the circuitry needed to be externally added in both the Pcam add-on board and on the Zybo Z7 itself (shown in more detail on page 2 of the Zybo Z7 schematic).

    Let me know if you have any questions about this.

    Thanks,
    JColvin


  3. Hi @josejose,

    The only example that we have that controls a board remotely uses the Pmod Wifi with a YouTube video and a thread on it here. However, this uses WiFi which you stated you would not be able to use. Some sort of bluetooth control would be the next choice (though you have to be within range to connect to the board), but we do not have an example for that.

    As both Dan and zygot have pointed out though, it will not be the easiest endeavor depending on your end goal.

    Thanks,
    JColvin


  4. Hello,

    Unfortunately yes, to use the Digilent made demo, you would need the license or the free trial of the TEMAC IP from Xilinx; this is stated both in the reference manual and the tutorial for the Microblaze servers. We do not currently have an alternate demo that gets around this limitation.

    Thank you,
    JColvin


  5. Hi @Joao Fragoso,

    We do not have a tutorial for this; the Pmod ports (at least for Digilent made boards) are tied to 3.3V logic so a normal Pmod port would not work for this. There are a couple of threads that discuss the hardware requirements here and here, with the takeaway being that you will need the LVDS capability (which at least the dedicated XADCs on the Digilent boards do not do). So it may be possible, but not likely and not straightforward to do.

    Thanks,
    JColvin


  6. Hi @TomF,

    I apologize for the delay. We don't have any specific advice for you regarding merging these two Xilinx made demos; as you have found and as this particular forum user on the Xilinx forums found, changing the order in which the interrupts are initialized can help things (though why this is the case I am uncertain of since all interrupts should be disabled while you are specifically enabling interrupts...). Xilinx will be better able to address this for you.

    Thanks,
    JColvin


  7. Hi @wooky,

    I apologize for the delay. Those of us at Digilent have not specificially looked into the compatibility of the FMC Pcam Adapter with the ZCU106. I would recommend reading the compatibility sections within the FMC Pcam Adapter Reference Manual, https://reference.digilentinc.com/reference/add-ons/fmc-pcam-adapter/reference-manual#carrier_card_compatibility, to see if the ZCU106 has been designed to meet it's specific needs or not.

    It may be possible to port the demo design, though the material we have was designed fairly specifically to the compatible Digilent boards (Zybo Z7) at least for the single Pcam demo (I haven't gotten to look into what is available for the FMC Pcam demo) as well as one of the IP's used being tied to specific versions of Vivado and SDK, so it would not be trivial.

    Thanks,
    JColvin


  8. Hi @Lina,

    I apologize for the delay. Digilent does not have any materials using an MX7 based board with FreeRTOS. It seems that MPLAB Harmony from Microchip has some material (such as the one here), though they all use an Ethernet starter kit, and I'm not certain how easily that could be adapted to the already included Ethernet hardware.

    Thanks,
    JColvin


  9. Hello,

    We (Digilent) do not have any formal examples or materials to be use Ethernet in RTL; we have some material that uses the Ethernet with Microblaze for a different Artix chip here that you could reference, though it will not be quite so straightforward to convert into RTL. Taking one of zygot's statements out of context, there are a lot more fine-grained details to worry about.

    Thanks,
    JColvin

     


  10. Hi @Spitzer,

    I learned for certain that Digilent did not get a hand in developing this new kit (hence the lack of Digilent's icon on the new kit). Could you let me know which chips had reverse or changed pinouts so I can get that updated on the store page and the Digilent Wiki? I will also work on getting a new kit tracked down so we can make note of any other changes that have occurred in detail.

    Thanks,
    JColvin


  11. Hi @Bill_H,

    I'm not sure which datasheet you happened to look at, but did you look at the one that we have in the Additional Resources section of the Pcam 5C Resource Center (link)?

    I'm not certain what you are referring to with regards for "the linux driver" but our demo application does not use a linux system.

    Thanks,
    JColvin


  12. Hi @rgc,

    Digilent does not have any formal tool to load a flash program onto a Cmod A7, nor does Xilinx as far as I am aware. If you are looking to program a Cmod A7 with a .bin file for flash, you will need to use one of the alternate solutions listed by our two community members above. If you just need to load a volatile .bit file though, you could use Digilent's Adept software to load it to the Cmod A7.

    Thanks,
    JColvin


  13. Hi @Spitzer,

    I took a look at our storefront as well, and it seems that the parts kit (while still maintaining the same storefront pictures, but changed the photos for the individual components) has a new version of the kit and links to Analog Devices reference page on the kit here: https://wiki.analog.com/university/tools/adalp2000/parts-index. Based on this, I would presume the kit and the included components are selected by ADI, though I do not know this for certain.

    I do not have this new kit myself, but I have reached out to some of my co-workers to see if they have it and can confirm the pin arrangement of the ADTL082.

    Thank you,
    JColvin


  14. Hi @varunnagpaal,

    I asked one of our design engineers about this and they let me know the following:

    "Based on the information that was provided the pin mapping appears to be correct. There’s a lot of extra wiring there which will add additional capacitance which may end up causing timing issues, depending on how fast TCK is running. I’d try eliminating half the length of wire… probably by plugging the flywire that’s coming out of J2 directly into the pins on the HS3. Another thing I would try is reducing TCK which can be done by connecting to a Local Target in Hardware Manager (don’t use Auto connect) and selecting a frequency as shown in the image here (attached below)."

    Please let us know if you have any questions about this.

    Thank you,
    JColvin

     

    image001.png