[Basys3 autoconnect on Vivado 2023]

Hi @taitashaw,

I haven't worked with HLS specifically, but the troubleshooting steps for getting the Basys 3 successfully detected by the Vivado software is explained in more detail in this thread here:

As for the 2023.2 differences in terms of the flow differences between this and previous versions (since Digilent's guide for setting up a basic project with Vivado and Vitis is based on 2023.1 and earlier) I would recommend checking out Adam Taylor's post on the differences between the flow here: https://www.adiuvoengineering.com/post/microzed-chronicles-introducing-vitis-unified-ide.

Let me know how it goes for you.

Thanks,
JColvin

[NEW ADP 3450 Still having issues "DstmTransfer failed ERC: 3077"]

I wanted to let you know that I have seen your question, but I am waiting for the WaveForms developer (Attila, who was working with you on an earlier thread) to return to the office to offer more support as this particular set of errors that you have seen is outside my realm of knowledge.

The only thing I can readily think of that I don't believe has been directly brought up or clarified would be to use a USB port directly present on a computer as opposed to a USB hub that is also simultaneously supporting a number of additional devices.

Thanks,
JColvin

[Restore ZedBoard factory booting]

Hi @mvernengo,

What revision of the Zedboard do you have? Neither the Rev D nor the Rev F of the Zedboard that I have match the silkscreen image you posted with the Mode numbering (my two versions list the MIO numbers), though the jumper numbering (JP7..11) does match. My concern is that if the jumper numbering is identical that then the Mode[X] silkscreen labels would not readily line up with the orientation listed in Table 18 of the Zedboard User Guide that Avnet created here: https://digilent.com/reference/_media/reference/programmable-logic/zedboard/zedboard_ug.pdf.

Presuming the latter situation, your setup of Mode3 and Mode2 being set high would have the device boot from Quad SPI flash memory (which is based on Mode2 high, and both Mode1 and Mode0 low), which from my understanding is not loaded or prepared by default with the Out-Of-Box material. That would be loaded through the SD card image (Boot Modes 2 and 1 set to logic high), which you can find in the Zedboard Resource Center here: https://digilent.com/reference/programmable-logic/zedboard/start#additional_resources.

I would also put Mode3 to logic low to set the device to Cascaded JTAG rather than Independent JTAG so that you can more readily access the device as per Table 22 in above linked user guide.

As for the serial terminal not responding in readable characters, my gut reaction would be to double check the baud rate (by default Zynq designs use 115200 baud, but Tera Term uses 9600 baud by default).

Let me know what you find out.

Thanks,
JColvin

[How to download the files for ZedBoard AVNET Configuration and Booting Guide ("reference design").]

Hi @mvernengo,

I don't know which exact guide you are referring to (I'm not readily seeing it on the Avnet page, nor within Digilent's provided material), but the Out Of Box demo material is available in the Additional Resources of the Zedboard Resource Center: https://digilent.com/reference/programmable-logic/zedboard/start#additional_resources.

Thanks,
JColvin

[Subtract scope channels]

Hi @doggy,

The Analog Input Channels on the Analog Discovery 3 have overvoltage protection to +/- 50 V DC (or +/- 30 V RMS) as per the last row in the Vertical System table here https://digilent.com/reference/test-and-measurement/analog-discovery-3/specifications#analog_input_channels, so you should be fine (relatively speaking) with the +/- 24 V system, particularly if the supply is being inherently limited.

You are correct that when using the BNC probes each of the analog inputs will then be single ended. You can add a Math channel through the "Add Channel" dropdown on the right hand side and set it up to do C1 minus C2 like you asked about. There is some additional information about the Math Channels in Section 3.6 of the Scope section of the Help tab.

Let me know if you have any questions.

Thanks,
JColvin

[About PCAM_5C_SCH drawing]

Hi @RggBer,

I have reached out to an engineer more familiar with the Pcam 5C regarding the specifics on how the OV5640 chooses internal vs external powering (I can't readily find the answer based on the datasheet that I found online here), but they are out of office until next week.

Otherwise, there is a recommended power up sequence that is mentioned in the refererence manual here: https://digilent.com/reference/add-ons/pcam-5c/reference-manual#power-up_and_reset.

Thanks,
JColvin

[WaveForms Logic Analyzer: can't find a way to filter glitches?]

Hi @Alrie,

I'm not certain what you might have as a triggering setup, but presuming that these Chip Select glitches aren't the software unintentionally toggling the CS line and using something like a weak pulldown resistor doesn't work in your situation, you can use the Pulse/Timeout to have it only trigger low CS negative pulses that exceed some length of time:

Let me know if that works for you (or if it doesn't quite work for your system so we can troubleshoot further).

Thanks,
JColvin

[Shipped default images Zybo 7020]

Hello,

I responded to your other thread here:

Thanks
JColvin

[Shipped FPGA and Software boot images]

Hi @FPGADude,

The out of box demo is available in the Zybo Z7 Resource Center: https://digilent.com/reference/programmable-logic/zybo-z7/start#example_projects, which ends up pointing you to this thread:

Let me know if you have any questions.

Thanks,
JColvin

[Firmware Update failing on my ADP3450]

Un-hid the post so that future users that encounter a similar issue can also benefit from the above troubleshooting process.

[Power down sequence in a FPGA(Arty S7 board)]

Hi @Prabhat.kumar

My understanding (I have not explicitly verified this with the design engineer of the Arty S7) is that the board does not directly respect the recommended power-down sequence, only the power-up sequence that is mentioned in DS189: https://docs.xilinx.com/r/en-US/ds189-spartan-7-data-sheet/Power-On/Off-Power-Supply-Sequencing.

I imagine this was done partially because the datasheet does not say it "must" be followed (theory based on this thread: https://support.xilinx.com/s/question/0D52E000078vhPbSAI/for-spartan-7-poweroff-sequence-is-it-required-or-we-can-just-pull-the-plug-according-to-ds189-the-recommended-poweroff-sequence-is-the-reverse-of-the-poweron-sequence-does-not-say-its-required?language=en_US and https://support.xilinx.com/s/question/0D52E00006iHkiJSAS/power-down-sequence-of-artix-7-and-power-up-sequence-of-spartan-6?language=en_US) and partially because Digilent cannot readily prevent users from 'pulling the plug' to suddenly and unexpectedly disconnect power from the board.

Thanks,
JColvin

[Analog Discovery Studio: Can't calibrate oscilloscope and waveform generator puts out unexpected voltages]

Hi @Kornelis,

After zooming in and verifying that the offset isn't a weird visual artifact on the Scope plot (and triple checking the ground connections), I would personally go for another round of calibration since that should calculate any needed offsets.

Let me know how it goes.

Thanks,
JColvin

[Forum Guilelines]

I agree that the organization of content on the Digilent Forum (and various other Digilent owned websites) are not an ideal state. Peeking behind the curtain, it is a goal of ours to identify, prioritize, and execute on a number of documentation clean up tasks during our "spare time"; I'll make sure that Project Vault and Tutorials subforums are included in this effort as well.

Thank you for the feedback,
JColvin

[Is it possible to collapse (hide) the components of a bus in the logic analyzer]

Hi @sraasch,

You'll need to double-click on the minus sign (or plus sign if already collapsed) to change the visibility of the individual components within a protocol shown within the Logic Analyzer tool.

Let me know if I misunderstood your question.

Thanks,
JColvin

[Analog Discovery Studio: Can't calibrate oscilloscope and waveform generator puts out unexpected voltages]

Hi @Kornelis,

My initial reaction was that the probes would be the source of error, but based on your description and setup I'm less inclined to think that this is the case.

BNC probes do tend to have some sort of circuitry in them (though I am uncertain if this is the case for probes that don't have a 1x/10x switch), so you could potentially get a better measurement by not using a BNC probe from the Wavegen and instead just connecting to the MTE pin, but this really shouldn't matter for DC signals.

Within the WaveForms Device Manager, there is the option to choose to load the factory calibration settings within the Reset dropdown (more details are within the section 4 of the WaveForms section of the Help tab). If resetting the factory calibration and individually measuring the wavegen output directly with the DMM after power cycling the device (no oscilloscope connected) does not result in close/reasonable voltage outputs that can't be corrected through the manual calibration process, then I would be inclined to think that ADS is potentially damaged in some way.

Let me know what you learn.

Thanks,
JColvin

[Timeout error 5001 while using a custom command in LINX LabVIEW and Arduino IDE]

Hi @minhlmao,

Digilent has not worked with LINX for a number of years. The best available support for it would be on the NI LINX Forum, https://forums.ni.com/t5/Hobbyist-Toolkit/bd-p/linx-toolkit.

That being said, from what I vaguely recall about the Error 5001 timeouts (I don't have LabVIEW installed anymore), I would recommend that you double check the serial port connection (Baud rate, COM port number, etc) and as well as what pins you are trying to have LabVIEW manipulate to make sure there isn't any conflicts with the Arduino code.

Thanks,
JColvin

[Analog Discovery 2 Triggering]

Hi @KatharinaSt,

I'm not readily able to produce the scenario you are wanting to create; I get the same single biphasic "pulse" on the trigger, but can't readily get it to repeat itself with the same delay between pulses during the trigger condition.

The creator of the WaveForms software @attila might have some additional ideas on how get this style of waveform output to work, but it may be awhile before we get a response from him depending on his scheduled vacation over the holiday timeframe.

Thanks,
JColvin

[sampling rate for analog discovery 2 data logger]

Hi @analog123,

I don't think there is a way to get a better visualization while recording data, partially because recorded data is intended for post-processing rather than live viewing. As far as I am aware, you are not able to adjust the time parameters in the middle of an acquisition.

Are you looking for a particular condition to appear during the recording session (as opposed to just collecting the data for later analysis)? Depending on what you are looking for, you could likely set up an acquisition to collect data before and/or after a defined trigger condition (rising edge, pulse timeout, if it exceeds a voltage window, etc).

Thanks,
JColvin

[transposing high frequencies into the hearable audio range]

Hi @DaniS,

I'm not too familiar with the nuances of changing and playing back frequencies at a different pitch without it sounding distorted.

Based on what you described, I'm guessing that the intended role of the AD3 in this scenario is to collect the incoming audio data from an external source and then either process or send the data to be processed.

While the AD3 does have the ability to internally loop analog data between the Scope and Wavegen instrument, when 'forwarding' data from the Scope to the Wavegen you only have the ability to adjust the amplitude and offset of the signal; the time base is not able to be adjusted (as the acquired data getting transferred to different portions of the FPGA needs to stay consistent in size).

If the audio data is already recorded and stored on the computer, you could use the Play functionality of the Wavegen instrument to import and then play an audio file of your choice (although now with the ability to change the frequency of the imported file) but of course this would not be a continuous audio signal.

Realistically though, if you are wanting to dynamically and continuously change the frequency of an incoming audio signal or adjust the frequency "properly" you would likely be better served using different software than what Digilent offers.

Thanks,
JColvin

[sampling rate for analog discovery 2 data logger]

Hi @analog123,

To have more control over the sampling rate of the analog inputs, I would recommend that you use the Record mode feature of the Scope instrument.

You can either choose to Record to File (via the "Rec." option next to the Export button and below the Welcome tab), which will let you record data up to 1 to 2 MHz.

Or you can change the sampling mode from Repeated to Record to record data at a faster rate, but you will be limited to the buffer size of the Scope channel (8 Ki samples with the default configuration for the AD2) to use those higher sample rates, otherwise you'll need to drop the sampling rate to the 1 to 2 MHz for larger amounts of data.

This thread has some more information about recording with the AD2:

Let me know if you have any questions.

Thanks,
JColvin

[ADP3250 calibration]

Hello,

The reset operation you described in 2-1 ("Device manager" -> "Calibrate" -> "Reset" -> "Load Factory") is the correct method to change the calibration values to what the ADP3250 was loaded with during the manufacturing process.
If the factory calibration results are not satisfactory, then the first half that you described in 2-3 ("Device manager" -> "Calibrate" -> "Wizard") is the correct method to adjust the calibration values as needed for your particular unit.

Choosing the different Boot options is not needed for changing calibration values. As per the Help Tab documentation for the ADP3450/ADP3250 in the Boot Mode section, whenever the device is powered on from the off state, the Standard Recovery is started by default and then automatically transitions to either the Standard or U-Boot (Linux Mode) applications, depending on what has last been selected by the user.

Let me know if you have any questions.

Thanks,
JColvin

[Zybo Z7 MIPI Common Mode Voltage question]

Hello,

It was pointed out to me that the XAPP894 mentions that if external termination is used (which the Zybo Z7 uses the style shown in Figure 11), the common mode voltage can drop to 100 mV, which is what you are measuring.

Let me know if you have any questions.

Thanks,
JColvin

[Nesys 4 DDR Repair]

Hi @Fra,

Digilent does not offer any repair services for our products unfortunately.

If you want I can try to help you identify what components might have been damaged on the Nexys 4 DDR, but the catch of course that more than one thing could be damaged.

Hopefully it is just the fuse (0603SFV350F/32-2) that is at the beginning of the voltage entry point that has burned out. Otherwise, I would also also be looking at the J11, J14, and J15 test points (top of the board near the Xilinx silkscreen label) with a multimeter when you are attempting to power the board with a 5 V supply to see what voltages, if any, are being registered on the different derived supplies.

Let me know if you have any questions.

Thanks,
JColvin

[Gee, Another New User]

While it could be argued that this violates the rules as written, I'll allow it. 😋

[ADP3450 Probe Compensation Documentation]

Hi @zorgoban,

We don't have formal guide for doing performing probe compensation as of yet (I'll see if I can get that created before I am out of office for the holiday timeframe), but in general the process would be as follows:

- Connect a BNC probe to the Scope channel you want to compensate it for.
- Connect a BNC cable with some sort of minigrabbers or alligator clips to one of the Wavegen out channels (i.e. not a BNC probe with circuitry to interfere with the signal).
- Connect the positive ends of the two BNC cables and the ground clips of them together.
- Set the attenuation switch on the BNC probe to 10x.
- Open the WaveForms software and open the Scope and Wavegen instruments.
- Set the Scope channel you are compensating for to 10x (available through the Gear options dropdown on the right hand side) and the range to 1 V/div
- Set the Wavegen channel to square wave with some higher amplitude to "force" any over/undershoot to happen and some frequency rate between 1 kHz and 5 kHz. Set your Scope timescale to account for the square wave frequency that you chose.
- Run both the Wavegen and Scope instrument.
- If you see non-square square waves on the Scope, use a screwdriver to adjust the trimmer till you get the square waves to be square. I usually also zoom in on my timebase to get a better view of my signal, sometimes also adjusting the offset to see how clean of a square wave I can get with minimal overshoot.

How "perfect" it needs to be will depend on your application of course, but if you zoom so far in that you start seeing the effect of the rise time of the square wave, you've almost certainly gone too far.

Let me know if you have any questions.

Thanks,
JColvin