Bug 1503 - Reading behind the communicated block bytes
Summary: Reading behind the communicated block bytes
Status: CONFIRMED
Alias: None
Product: libsigrok
Classification: Unclassified
Component: Driver: siglent-sds (show other bugs)
Version: 0.5.2
Hardware: x86 Linux
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-21 20:55 CET by meol
Modified: 2020-02-21 21:19 CET (History)
1 user (show)



Attachments
pulseview --driver=siglent-sds:conn=tcp-raw/192.168.10.44/5025 -D -c -l 5 (52.95 KB, text/x-log)
2020-02-21 20:55 CET, meol
Details

Note You need to log in before you can comment on or make changes to this bug.
Description meol 2020-02-21 20:55:14 CET
Created attachment 600 [details]
pulseview --driver=siglent-sds:conn=tcp-raw/192.168.10.44/5025 -D -c -l 5

Hi,

when connecting to a siglent SDS1202x-e and starting a recording in pulseview (probably no difference on cli tools) with -l 5, the ui stops responding after a short period of time.
The log output shows lines like these:

sr: [00:18.983311] session: bus: Received SR_DF_ANALOG packet (1448 samples).
sr: [00:18.983336] siglent-sds: 139008 of 140000 block bytes read.
sr: [00:18.983342] siglent-sds: Requesting: 992 bytes.
sr: [00:18.983391] siglent-sds: Received block: 15, 992 bytes.
sr: [00:18.983418] session: bus: Received SR_DF_ANALOG packet (992 samples).
sr: [00:18.983443] siglent-sds: 140000 of 140000 block bytes read.
sr: [00:18.983449] siglent-sds: Requesting: 0 bytes.
sr: [00:18.983455] siglent-sds: Received block: 16, 0 bytes.
sr: [00:18.983459] session: bus: Received SR_DF_ANALOG packet (0 samples).
WARNING: Received analog packet with 0 samples.
sr: [00:18.983485] siglent-sds: 140000 of 140000 block bytes read.
sr: [00:18.983489] siglent-sds: Requesting: 0 bytes.
sr: [00:18.983493] siglent-sds: Received block: 17, 0 bytes.
sr: [00:18.983497] session: bus: Received SR_DF_ANALOG packet (0 samples).


Lines after (including) WARNING repeat endlessly.

abraxa assumed in IRC, it might be a driver bug. I'm using the current version in arch linux. Excerpt from the attached log:

sr: [00:00.000238] backend: libsigrok 0.5.2/5:1:1.
sr: [00:00.000263] backend: Libs: glib 2.62.4 (rt: 2.62.4/6204:4), libzip 1.5.2, libserialport 0.1.1/1:0
:1 (rt: 0.1.1/1:0:1), libusb-1.0 1.0.23.11397 API 0x01000107, libftdi 1.4.
sr: [00:00.000271] backend: Host: x86_64-pc-linux-gnu, little-endian.
Comment 1 meol 2020-02-21 21:14:59 CET
minor difference between attached log and last comment: I used different memory settings, the excerpt is from a test with 140k.