Hi Soeren, > log to the bug tracker, including a short acquisition? I'd like to > know what happens with the driver at what point in time.
your suspicion the driver could cause problems I also tracked. For this I use sigrok-cli. With the call: SIGROK_FIRMWARE_DIR = / usr / local / share / sigrok-firmware / dslogic_firmware ./sigrok-cli --driver dreamsourcelab-dslogic --config samplerate = 1M --samples 1000000 -l 5 I only get phantom trigger. Apparently, the DSlogic has not configured a usable (> 0V) threshold. The default threshold programmed in the driver is apparently not active. Only a call with threshold parameters: SIGROK_FIRMWARE_DIR = / usr / local / share / sigrok-firmware / dslogic_firmware ./sigrok-cli --driver dreamsourcelab-dslogic --config sample rate = 1M: voltage_threshold = 1.5-1.5 --samples 1000000 --channels 0 = TX --triggers TX = r -l 5 2> error_config_with_threshold.log 1> data_config_with_threshold.log shows success. I think the driver has a bug! Simple usage without threshold parameters leads to trigger errors! I can provide the logfiles. Jörg ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
