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 /
Hi Joerg,
I opened https://sigrok.org/bugzilla/show_bug.cgi?id=1149 for this
issue so we can track it properly. Can you please add a complete
log to the bug tracker, including a short acquisition? I'd like to
know what happens with the driver at what point in time. Thanks!
-Soeren
On Sat,
Hi Soeren,
a log with data-information (ex. uart-infos) ?
pulseview -l 5 ?
I must change the threshold-level by the pulseview
device-config-button more then 0 Volt. If not there will be NO
trigger.
Jörg
Am Sat, 31 Mar 2018 23:05:40 +0200
schrieb Soeren Apel :
> Hi
Hi Uwe,
the bug for the default threshold is fixed in the Dslogic driver with
commit 86a1571 (api.c).
The problem is not the driver, but Pulsview can not take over this
condition.
Pulseview also queries values regarding -binding- in libsigrok:
sr: [253:34.373654] hwdriver: sr_config_get():
Hi,
On Sun, Feb 04, 2018 at 07:08:59PM +0100, Jörg wrote:
> the latest version of "pulseview" from the Git has the threshold mark L
> <0V H> 0V for the device driver Dreamsourcelab-DSlogic.
>
> I have read that in the driver is 1.5V default.
>
> Is this default value not read out from the
Hello,
the latest version of "pulseview" from the Git has the threshold mark L
<0V H> 0V for the device driver Dreamsourcelab-DSlogic.
I have read that in the driver is 1.5V default.
Is this default value not read out from the driver and set by PV?
greetings
Jörg
6 matches
Mail list logo