ChipWhisperer-Husky Streaming Captures Corrupted While ADC Self-Test and Non-Streaming Captures Pass

Hello,

I am experiencing corrupted streaming captures on a ChipWhisperer Husky, while non-streaming captures appear normal.

Environment:

  • ChipWhisperer Husky
  • Tested with ChipWhisperer 5.7.0 and 6.0.0
  • Reproduced on two different Macs, using both terminal scripts and Jupyter Notebook
  • Firmware: 1.5 (latest_fw also reports 1.5)
  • FPGA build: 12/11/2024, 12:33

scope.adc_test() returns “pass”.

With the analog input disconnected:

  • Non-streaming 8-bit capture: values remain within 127–129
  • Non-streaming 12-bit capture: values remain around 2041–2068
  • Streaming 8-bit capture: abnormal values including 0, 60, and 255 appear
  • Streaming 12-bit capture: abnormal values including 7 and 4095 appear

The issue is reproducible at 5, 7.37, and 10 MS/s. FIFO errors also occur, including during a 20-million-sample streaming capture. The problem occurs in both 8-bit and 12-bit streaming modes.

Since the ADC self-test passes and non-streaming captures are clean, this does not appear to be caused by the probe, input signal, gain setting, or analog frontend.

Could you please confirm whether this is a known Husky streaming firmware/FPGA issue? If not, would this be considered a hardware fault requiring repair or RMA?

Thank you.

Hi, there are currently no known issues with streaming.

Do you have any other USB activity occurring during the streaming capture? That can cause the type of failure you describe. Also, ensure that Husky is directly connected to a USB >= 2.0 port on your PC (not through a hub).

If you still see the failures, run the following and share the output:

  1. Clear any errors with scope.errors.clear()
  2. Run a stream capture that results in errors.
  3. print(scope.errors, scope.adc.first_error, scope.adc.first_error_state)