All Activity

I have a flash ADC built and I am trying to use my FPGA as the priority encoder. I need to connect the 3.3 and 0 V signals coming off of the comparators to my FPGA. I don't see any general purpose IO pins like an Arduino has so I was curious as to how I should connect the wires. Can I just use the PMOD ports for this purpose and alter the constraints/xdc file to map to whatever name I give them in the verilog code?

The output rate is about 1 kHz, and the range is +/-5V typically (though we've also tried +/- 10V). I configured the PCIe-DAS1602 for differential and that didn't seem to help. I am using comedi in Ubuntu to read from the board, and have been working to specify the input range as well.

and I need the complete kit

yes please

After applying that fix, I'm also seeing the last five bytes of the last packet be corrupted and need to look into it some more. At least with RECV_BUFFER_SIZE 200000, words_per_packet, 50000, packets 4. Updated main.c is attached. main.c

Hi @NAOUZ Could you restate your question? Are you looking for a Nexys A7 board that can use a 7-15 V external supply instead of a 5 V supply? Thanks, Arthur

Hi @Alturan Welcome to the forum. Storing data in block RAM (or just LUTs) and counting through addresses is a standard way of doing this kind of thing. Each SPI transfer sent to the DAC would have a new value - like your data_i signal would be a new piece of data read out of a BRAM at the start of every transfer, incrementing the address every transfer. You would use a separate counter to control when each new SPI transaction starts to control the sample rate - assuming a 100 MHz clock, you could get a 1 MS/s DAC update rate if whenever a counter counts to 100, a new transfer is initiated, although it looks like your controller currently takes 120 clocks to send out a transfer. You can even control the frequency of the output signal by changing how much the address counter goes up each transfer - adding 10 to a counter that rolls over when it goes above 255 lets you count through a lookup table 10x faster than adding 1 each time. I'd also recommend simulating your HDL as you go, before testing in hardware - using "if clk_divided = '1' then" instead of "if clk_div_counter = CLOCK_DIVIDER - 1 then" for the shift register enable is concerning - it's probably active for 5 clocks in a row, then idle for the next 5, rather than active for one in every five clocks, like I assume is intended. Check out this guide: https://digilent.com/reference/programmable-logic/guides/simulation. Thanks, Arthur

Hi @ericnstein, I have sent you a PM. Thanks, JColvin

Hi @tato0316 Welcome to the forum. MIO pins are not accessible through PL I/Os and don't get constrained - each MIO maps to a specific physical I/O on the chip. The Zybo's SD interface also doesn't have alternate paths on the PCB to FPGA I/O pins. You would need to access the SD card by using the PS, or maybe by controlling PS peripherals from fabric through the PS's AXI slave ports (assuming they're even addressable from there...). Depending on the end goal, maybe you could load the text file data into a BRAM instead, or even a couple of versions of the data, and bake it into the bitstream? Thanks, Arthur

i want such card with exactly the nexte specifications : ( Carte de développement FPGA technologie Xilinx FPGA part XC7100T-1CSG324C Logic Slices 15,8500 Block RAM (Kbits) 4,860 DDR2 Memory (MiB) 128 ClockTiles (with PLL) 6 DSP Slices 240 Internalclock speeds exceeding 450MHz On-chip analog-to-digital converter (XADC) Programmable over JTAG and Flash System Features USB-JTAG programmingcircuitry Poweredfrom USB or any 7V-15V source microSDcardconnector System Connectivity 10/100 Mbps Ethernet USB-UART Bridge Interaction and SensoryDevices 3-axis accelerometer PDM microphone PWM audio output TemperatureSensor 2 four-digit sevensegment displays USB HID for mice , keyboards, and memory sticks 16 Switches 16 LEDs 2 tri-colorLEDs 12-bit VGA output Expansion Connectors 4 PmodconnectorsPmod for XADC signals Réf : Nexys A7-100T )

Hi @Viktor Nikolov 500000 should be fine for a packet length - it fits within the 26-bit max of the DMA. I imagine you're also increasing the RECV_BUFFER_SIZE, since it doesn't sound like it's reporting errors - adding a return to the check in main would help debug: With fresh eyes, there's a bug in the code where the cache is handled - the ranges should be RECV_BUFFER_SIZE * sizeof(u32) bytes, rather than RECV_BUFFER_SIZE words. This would be obscured unless large enough values for the packet length and count are tried... Thanks, Arthur

Hi @ankit24, My name is Britt, I am on the team that manages Multisim Live. I've reached out to you via email to help solve the issue. Please continue this conversation there. -Britt

On our older machine we have 2 DT9812. Each card has 1 AI, AO, and counter. The counter uses the CounterTimerSubsystem with the following configuration. ctSS = device.CounterTimerSubsystem(0); ctSS.CounterMode = CounterMode.Measure; ctSS.StopEdge = EdgeSelect.GateFalling; ctSS.StartEdge = EdgeSelect.GateRising; ctSS.DataFlow = DataFlow.Continuous; ctSS.Clock.Source = ClockSource.Internal; ctSS.Clock.Frequency = 5000; ctSS.MeasureDoneEvent += CtSS_MeasureDoneEvent; Our new machine will need 3 counters, and up to 5 AI. However, the analog input isn't a solid requirement. We can read those elsewhere if necessary. I am aware I'll need to rewrite my code to use the universal library. That won't be an issue, as long as the driver can raise an event when the counter increments. Is there a reason so many DT models say "Not recommended for new applications."? If we knew why, we might be more inclined to use them.

Thank you, JRys.

Hi @rpatel, For the SMT4, I have been informed that the worst case for Vdd is 115 mA and the typical usage is 90 mA with JTAG running at max speed and UART running at 1 MBaud. The Vref current at 30 MHz is 12.5 mA typical and 35 mA max (unless you short the outputs, then Vref would probably peak out around 170 mA). You didn't ask about minimums, but when the USB controller is held in reset, the current consumption is ~20 mA. When it comes out of reset and enumerates on the bus it's ~87.5 mA. Let me know if you have any questions. Thanks, JColvin

@bsee, You have an existing application with the DT9812-10V, which is still available. How is the DT9812 used in the existing application, i.e. number of channels, sampling rate, subsystems? This information is necessary to match to an equivalent MCC device. Note that moving over to a MCC device will require rewriting your application with the MCC Universal Library.

Hi @Kevin.C, 3.22.19 is an "official" beta build (https://forum.digilent.com/topic/8908-waveforms-beta-download/) as opposed to a formal release (though the difference between a beta build and a formal release mostly boils down to the amount of documentation involved along extra hunting for bugs). I do not anticipate a formal release version to be made for at least a couple of months; it depends when a new Digilent Test and Measurement device comes out, but I have not seen any announcements as of yet. I will make a note to ping you once a release version has been made. Let me know if you have any questions. Thanks, JColvin

Hi @ankit24 I've reached out to our software team to see if we can track down your issue. Thanks for reaching out. Best, Arthur

The old machine used DT-Open layers. However, we're building a new machine, and these machines tend to last 20+ years. We're concerned about using a board that "isn't recommended for new applications" on a new machine. That's why I'm asking if the Universal Library can raise an event when a counter is incremented. If it can, that expands the range of products that might work for us. If not, I need to recommend to my electrical engineer to only select from your DT product range.

Thanks @JColvin. Do you know what the typical and max current usage is of the JTAG-SMT4 module?

Following up to see if anyone has any details about the typical and max current usage of the JTAG-SMT4 module.

Information about how to repair a USB-TC is not readily available, but I might be able to have them repaired. Please send me a private message with both device serial numbers and your phone/email/shipping address. The repair process takes 4-5 weeks. If it can be repaired, my customer service department will contact you.

You can add (+) another AXI GPIO to your block diagram, similar to how it was done for the button in https://digilent.com/reference/programmable-logic/guides/getting-started-with-ipi. Name the (make) external connection pio instead of btn. Constrain the desired IO pins as pio_tri_io[0]...pio_tri_io[7]. Name the block AXI_GPIO_PIO and finish the build by running block automation. Follow the guide to create the HDL header, generate the bit stream, and export the design wrapper. In your SDK app, add the following, like it was done for the buttons and LEDs. #define PIO_ID XPAR_AXI_GPIO_PIO_DEVICE_ID #define PIO_CHANNEL 1 #define PIO_MASK 0b11111111 cfg_ptr = XGpio_LookupConfig(PIO_ID); XGpio_CfgInitialize(&pio_device, cfg_ptr, cfg_ptr->BaseAddress); XGpio_SetDataDirection(&pio_device, PIO_CHANNEL, 0); //output //update the first eight GPIOs. XGpio_DiscreteWrite(&pio_device, PIO_CHANNEL, pio_data);

Hello @bsee. The DT9812-10V (Digilent SKU: 6069-410-131) is still available for purchase. The MCC Universal Library for Windows software does not support Data Translation (DT) devices. DT devices use DT-Open Layers library (OMNI Software). The DT9812-10V supports event counting, as do various MCC devices if the decision is to migrate over to other devices and API library. Which DT API was used to develop the application, DataAcq SDK or DT-Open Layers for .NET? Regards, Fausto

`rpm -qip digilent.waveforms_beta_3.22.19.x86_64.rpm` warning: digilent.waveforms_beta_3.22.19.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID eb58bc22: NOKEY Name : digilent.waveforms Version : 3.22.19 Release : 1 Architecture: x86_64 Install Date: (not installed) Group : Engineering/misc Size : 68199451 License : see /usr/share/doc/digilent-waveforms/copyright Signature : RSA/SHA256, Tue Apr 23 11:54:07 2024, Key ID 134da9ebeb58bc22 Source RPM : digilent.waveforms-3.22.19-1.src.rpm Build Date : Mon Apr 22 09:47:27 2024 Build Host : attila-u16-64 Summary : Digilent WaveForms Description : Digilent WaveForms Application, Runtime and SDK. Support for Digilent Scopes & Instruments products. looks fine to me! is this the official 3.22.19 release?