Jump to content

JColvin

Administrators
  • Posts

    6,608
  • Joined

  • Last visited

Everything posted by JColvin

  1. Hi @Jeong cha, I have sent you a PM. Thanks, JColvin
  2. Hi @weaverdouglas22, Understood. The W1 and W2 labels on the BNC Adapter were chosen because that matched the labels of the two waveform generator channels shown on the plastic of the Analog Discovery 2 and 3. If you have a different labeling scheme in mind that would help make the product more intuitive to users, I would love to hear it so that I can pass it on to R&D. Thanks, JColvin
  3. Hello, I responded to your other thread here: Thanks, JColvin
  4. Hi @Dr.J, Unless I'm mistaken, both 3.3 V and 5 V are available on the USB104A7. The 5 V rail is the SYZ5V0 as noted in Table 1.2.1 in the USB104A7 Reference Manual: https://digilent.com/reference/programmable-logic/usb104a7/reference-manual#power_specifications. You can see this rail on the schematic on page 2 and page 12: https://digilent.s3-us-west-2.amazonaws.com/resources/programmable-logic/usb104a7/USB104_A7_sch.pdf. I'm not sure where you are getting the 1.2 Amp requirement for the 5 V supply, as it there is explicitly no minimum current requirement listed in Table 9 of the SYZYGY Specification version 1.1.1 from September 2023: https://syzygyfpga.io/specification/, but as per Table 7.1.1 in the USB104A7 Reference Manual the 5 V rail will supply up to 1.5 A in total: https://digilent.com/reference/programmable-logic/usb104a7/reference-manual#zmod_port. The 1.2 V to 3.3 V is for the VIO supply voltage, which is within the recommended range also noted in the same Table 9 in the SYZYGY Specification 1.1.1. Please let me know if I am misunderstanding your question. Thanks, JColvin Edit: After re-reading, I see you were referring to the main landing page/Resource Center for the USB104A7. I have updated that page to better indicate that it is the VIO supplies specifically that are 1.2 to 3.3 V.
  5. Digilent also provides a board file preset that will correctly configure the Zynq block with its various on board peripherals, including UART, for you; https://digilent.com/reference/programmable-logic/guides/installing-vivado-and-vitis#install_digilent_s_board_files. When adding the Zynq block to the Block Design, you'll just need to check the Apply Board Preset box (visual in the Add a Zynq processor dropdown here: https://digilent.com/reference/programmable-logic/guides/getting-started-with-ipi#add_a_processor_to_a_block_design). Let me know if you have any questions. Thanks, JColvin
  6. Hi @Danny Cote, The most consistent way, of course, would be to power cycle the device. Which device and what version of WaveForms are you using? Normally, when you close the WaveForms GUI, the device (more or less) becomes immediately available to use in a separate application or script. Thanks, JColvin
  7. Hi @concept, 1. No, you do not have to unsolder it. There are tri-state buffers that disconnect the FTDI chip from the onboard JTAG nets when the FTDI chip is not open in Adept or Vivado; there are also some series resistors in place to protect circuitry from being damaged, though of course it is up to the end user to avoid deliberately creating drive conflicts. Figure 5 in the JTAG SMT3 Reference Manual shows the basic layout approach: https://digilent.com/reference/programmers/jtag-smt3/reference-manual#example_2interfacing_a_zynq-7000_while_retaining_the_xilinx_jtag_header. 2. You can use a standard straight 6-pin 100 mil header. The staggered layout is so that you can maintain electrical contact without having to solder an external header in. 3(ish). I personally don't often use J8, mostly because a lot of the designs I end up working with implement UART, and I already have a convenient connection to the host computer through J10 with the USB-JTAG circuitry. Let me know if you have any questions. Thanks, JColvin
  8. Hi @Anthocyanina, Thank you for the feedback; you have been heard. I will be sure to communicate this to the team for future T&M devices. Please let me know if you have any additional feedback or questions. Thanks, JColvin
  9. Hi @CJtech2023, Which Digilent product do you have? Your screenshots indicates that you might have the Nexys 4 DDR board, but you also mentioned having an Artix-7 15T FPGA, which is not present on any of the Nexys boards. I want to make sure I do not give you faulty instructions to avoid any chance of accidentally damaging the device. Thanks, JColvin
  10. Hi @Chithambaram Veerappan, A Zybo Z7 will have a silkscreen labeling of "Zybo Z7" and only HDMI ports (the original Zybo had a VGA connector), but I doubt that will be relevant here. I am not familiar with the WaveShare JTAG module, but it looks to be based on (or maybe is) the original Xilinx Platform USB Cable, which might be compatible with the PS_POR_B pin on Zynq devices for the processor via the listed Halt pin, but I am not certain. This seems like the most likely culprit considering that you are having difficulties getting it to configure the ARM core processor side. This thread was for a different JTAG programmer, but you might have some luck following the recommendations in there: Thanks, JColvin
  11. Updating this thread that since the seats were purchased through NI (rather than Digilent directly), some additional communication has been done (not on this thread) to help resolve and clarify the seat activation issue. I also removed the serial number from the post to avoid any unwanted activations. Thank you, JColvin
  12. Hi @Rose, I have reached out to the engineers involved with this end of Multisim about your query. Thank you, JColvin
  13. The female host Pmod connector on the Basys 3 (and other Digilent products) is a Sullins PPTC062LJBN-RC, with 100 mil pitch between each of the pins. Thanks, JColvin
  14. JColvin

    Contact

    Hi @Allister, Digilent does not offer phone support. Support for Digilent products is instead provided here on the Forum, so that other users can find and see the public record of any troubleshooting that has occurred. That and with the nature of Digilent products, screenshots are commonly involved which is not conducive to voice conversations. Let me know if you have any questions. Thanks, JColvin
  15. Hi @SINAPTEC COMBLEZ, I don't have the exact dimensions of the hole in the PCB, but the pins that are used have a standard 0.025 inch (0.635 mm) square posts with a 100 mil (2.54 mm) pitch between the pins. An example of the header used is this one, https://www.digikey.com/en/products/detail/würth-elektronik/61304021021/4846885, albeit with a different number of positions and potentially a different pin length as I didn't check that detail. Let me know if you have any questions. Thanks, JColvin
  16. Hi @rpatel, The other differences between the JTAG SMT3 and the JTAG SMT4 besides the two extra UART channels on the SMT4 compared to the SMT3 and the difference in AMD software suite compatibility that I am aware of are as follows: SMT3 has separate variable voltage support for its UART channel (1.8 V to 5.5 V) SMT4 does not have variable voltage support for its 3 UART channels, instead using the 3.3 V Vdd supply SMT3 variable JTAG reference voltage ranges from 1.8 V to 5.5 V SMT4 variable JTAG reference voltage ranges from 1.8 V to 3.3 V SMT4 has both a PS_SRST_B pin and a PS_POR_B pin to perform software resets for Zynq platforms SMT3 only has PS_SRST_B Related to the above three, the DC Operating Characteristics (see the named section in each of their Reference Manuals) are correspondingly different A less expected change is that VBus_Detect on the SMT4 has a higher minimum voltage While the outside dimensions of the two modules are the same, the landing pattern and dimensions of the individual pads are, of course, different Thanks, JColvin
  17. Hi @Sheng, I have sent you a PM. Thanks, JColvin
  18. Hi @ahes03, I have sent you a PM. Thanks, JColvin
  19. Hi @MrBil, The only motor controller that Digilent has is the Pmod DHB1, so if you are set on using a Pmod form factor, that is what I would recommend. I am certain that there are various motor controller / driver / H-Bridge Raspberry Pi HATs that would also accomplish what you need. I don't know how many DC motors you want to control or what voltage & current those motors require (nor am I familiar with this sort of product offering at large) so I don't have any specific recommendations in that space. Let me know if you have any questions. Thanks, JColvin
  20. Hi @MrBil, The Pmod DHB1 is not a true direct replacement. A list of differences that I came up with is below: The 100 mil spaced pin header to connect to the host board is different (the Enable and Direction have switched places). The supported continuous current drain is slightly less -- 1.5 A per H-Bridge instead of up to 2 A per bridge. Correspondingly, the peak is also less. The supported motor voltage is less -- 10.8 V rather than up to 12 V. The main benefit of the Pmod DHB1 is that it is a dual H-bridge, so it can drive two motors simultaneously (each at 1.5 A continuous). Like the Pmod HB3, it also supports motor feedback. Digilent otherwise does not have any true equivalent replacements for the Pmod HB3. Let me know if you have any questions. Thanks, JColvin
  21. In terms of not being reliably recognized by WaveForms, that is less normal. (the relay noises are normal as Attila indicated) Are you connecting the AD3 to your host computer (Windows?) with the included USB-C to C cable or going through a hub? What does your setup look like? Thanks, JColvin
  22. Hi @anatolianboy, I have sent you a PM. Thanks, JColvin
  23. Hi @Tom DeCasper, At this point I would be inclined to think that the power regulator is not functioning and would recommend getting a replacement presuming your are within the 1 year warranty, https://digilent.com/shop/shipping-returns/#warranty. If you purchased the product through Digilent directly, please send me a private message with the following information: - Order Number - Purchase Date - Serial number of the Basys 3 (located on the barcode on the underside of the device starting with "D") - preferred email address I will then work with the Digilent Sales team to start the RMA; they will contact you to confirm any additional details I do not have access to (such as address). If you purchased the board through a distributor (Digikey, Element14, Amazon, etc) you will need to contact them to determine their own replacement process. They will then work with Digilent as needed. Feel free to link to this thread as evidence of having done troubleshooting with a Digilent engineer. Thanks, JColvin
  24. Hi @Tom DeCasper, In principle, your setup sounds correct and the voltage is within the acceptable range (3.6 V to 5.5 V when the USB Host function is not being used), https://digilent.com/reference/programmable-logic/basys-3/reference-manual#power. I imagine this is not the case, but since I've seen all of the following situations more than once before, I want to confirm the following details: - If you are connected to a powered hub, the USB hub is hasn't been disconnected from the host computer (presumably it's still powered since you are getting power) - you are connected to the microUSB port on J4 (as opposed to the larger Standard A port on J2) - The microUSB cable is not plugged in upside down It's also good to do a sanity check of trying a different USB cable and USB port. I'm not anticipating these to be the issue since you are successfully measuring voltage on the JP2, but if your OS is not recognizing the attached device, it's good to double check you are not using a charging only cable. Let me know what you learn. Thanks, JColvin
  25. Hi @Maxxim, I received confirmation from the Engineering Services Manager that the part I mentioned, A3910EEETR-T, is indeed the part loaded on the board; no alternates or substitues are approved for this product. The 743 marking on your module is almost certainly some sort of manufacturing lot code that Allegro Microsystems uses, though I don't have any additional insight as to what it might indicate. The markings of the Impedance Analyzer module on my desk are 143 followed by a 10 on the next line. The only other thing I can think of that might be part of your query is the fact that the landing pad traces extend beyond the edge of the DFN package which is standard for this type of package. Let me know if you have any questions. Thanks, JColvin
×
×
  • Create New...