Search the Community

Showing results for tags 'bug'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Test and Measurement
    • Measurement Computing (MCC)
    • Add-on Boards
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions
    • Archived

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 5 results

  1. Hopefully not too hard for someone else to repro. This is on a ADP3450, Win 11, Beta 3.17.20. I did not try an regress on earlier versions. Workspace and GIF attached. 1) Open my workspace 2) Record in Scope (required, will not crash if you just open the workspace and do step 3) 3) Change Math:Filter to a non-enabled channel (enabled channels work fine) 4) Product quits automatically and you lose your workspace changes. crash-changing-filter-source.dwf3work
  2. The oscilloscope channel signals don't stay aligned with the cursors, grid, and reference waveforms when zoomed out. The image "zoomed_in.png" has a signal (yellow), a reference waveform created from that signal (green), and two cursors. The signal and reference waveform are perfectly overlapping as expected. This is at 1ms/div. When I zoom out one step to 2ms/div, the signal becomes misaligned with respect to the reference and the cursors. In the third image, "badly_aligned.png", I have a capture of a periodic signal. I zoomed in on two of the pulses and placed the cursors in the middle of the pulses. When I zoom out, the cursors no longer look like they match up with pulses. Also notice that the cursor on the right appears farther away from the pulse than does the cursor on the left. The misalignment seems to be more of an issue toward the end of the full capture than at the beginning. This is an issue with both 3.16.3 and beta_3.16.23. I'm using Ubuntu 20.04.
  3. There appears to be a mistake in the WaveForms SDK Reference Manual supplied with the SDK. The document says: But the function actually requires the idxChannel AND idxNode, like this: I'm running the following code segment to get the different node options: num_channels = c_int() dwf.FDwfAnalogIOChannelCount(hdwf, byref(num_channels)) print(num_channels.value, "channels") for i in range(0, num_channels.value): print("Channel", i) channel_name = create_string_buffer(32) channel_label = create_string_buffer(16) dwf.FDwfAnalogIOChannelName(hdwf, c_int(i), channel_name, channel_label) print(str(channel_name.value), str(channel_label.value)) num_nodes = c_int() dwf.FDwfAnalogIOChannelInfo(hdwf, c_int(i), byref(num_nodes)) for n in range(0, num_nodes.value): node_name = create_string_buffer(32) node_label = create_string_buffer(16) dwf.FDwfAnalogIOChannelNodeName(hdwf, c_int(i), c_int(n), node_name, node_label) print(" ", str(node_name.value), str(node_label.value))
  4. Hey Digilent, I've successfully run the low_level_zmod_adc_dac demo on my board with a ADC and DAC ZMOD. I next decided to run the zmod_dac demo using both petalinux and baremetal. I was able to program the FPGA and also run the code, however every time it attempts to allocate a buffer to transfer the waveform via AXI DMA malloc is returning a 0/NULL value for the buffer address. If I am correct this means that malloc is unable to obtain memory. I'm running this demo as is directly from your git repo. The error that occurs due to this 0 buffer address varies, for petalinux it causes a memory violation error when it tries to copy the waveform to the buffer. For bare metal it copies fine, but then the AXI DMA copy never completes presumably due to the bad 0 address. Do you have any tips for me on how to get this demo running? If there is any additional information I can provide just let me know. I did find it curious that fnAllocBuffer takes an "addr" corresponding to the dmaAddr on the zmod but then doesn't use it for anything, could that be related? Thanks! void* fnAllocBuffer(uintptr_t addr, size_t size) { uint32_t *buf = (uint32_t *)malloc(size); return buf; }
  5. With WaveForms for Windows in docking mode, keyboard shortcuts don't respect focus. Instead of being delivered to the currently focused panel only, the keystrokes are sent to any random panel with a matching shortcut. Consider the following layout: [Supplies | Logic] ------------------ [Protocol | Script] With the Script panel in focus I'd expect Alt+F to open the Script panel's File menu, but it instead goes to Supplies. If I hit Esc and try again it now goes to Protocol, then to Script, then to Logic, and so on. What's more alarming is that if you stack some of the panels, keyboard shortcuts continue to be delivered to all—including the ones that are now hidden in inactive tabs. For example, if you take the above layout and drag Script on top of Protocol (with these two panels now becoming tabbed), select the Scripts tab, and hit Alt+F, the Protocol tab continues receiving this shortcut in spite of being completely invisible—and its File menu appears floating in the top left corner of the WaveForms window, detached from the invisible Protocol tab, so you can't even tell to which panel the menu belongs. This problem doesn't occur in any of the other window modes.