Bug 1634 - UART PD start bit is shown one sample too late
Summary: UART PD start bit is shown one sample too late
Status: CONFIRMED
Alias: None
Product: libsigrokdecode
Classification: Unclassified
Component: PD: uart (show other bugs)
Version: unreleased development snapshot
Hardware: All All
: Normal minor
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-29 19:08 CET by Diego Herranz
Modified: 2020-11-01 08:25 CET (History)
2 users (show)



Attachments
Start bit indication (7.88 KB, image/png)
2020-10-29 19:08 CET, Diego Herranz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Diego Herranz 2020-10-29 19:08:42 CET
Created attachment 696 [details]
Start bit indication

Using the UART protocol decoder, it looks like the indication of where the Start bit begins is shown one sample too late (see attached image).

I marked it as PulseView although I guess that the issue could possibly come from libsigrokdecode.

It's a very minor thing, but today I had to document when a UART transmission started precisely, and that 1 sample difference made a difference in this specific case.

Thanks!

Tested on:
Versions, libraries and features:
PulseView
0.5.0-git-1acc207
Qt
5.7.1
glibmm
2.42.0
Boost
1_60
exprtk
20200101
libsigrok
0.6.0-git-efce57d/4:0:0 (rt: 0.6.0-git-efce57d/4:0:0)
- glib
2.44.1 (rt: 2.44.1/4401:1)
- libzip
1.5.2
- libserialport
0.1.1/1:0:1 (rt: 0.1.1/1:0:1)
- libusb-1.0
1.0.20.11003-rc3 API 0x01000104
- hidapi
0.8.0-rc1
- libftdi
1.4
- Host
x86_64-w64-mingw32.static.posix, little-endian
- SCPI backends
TCP, serial, USBTMC
libsigrokdecode
0.6.0-git-f96f633/4:0:0 (rt: 0.6.0-git-f96f633/4:0:0)
- glib
2.44.1 (rt: 2.44.1/4401:1)
- Python
3.4.4 / 0x30404f0 (API 1013, ABI 3)
- Host
x86_64-w64-mingw32.static.posix, little-endian
Comment 1 Gerhard Sittig 2020-11-01 08:25:56 CET
This may or may not be considered a duplicate of bug 1337 and its 
annotation location part, which unfortunately was mixed with the 
robustness in the presence of invalid input data. The pulseview 
application just displays what the library specifies.

Am keeping this bug 1634 in place for its clearly addressing the 
specific issue, and providing a screenshot. Will adjust the category.