Bug 1343 - broken clock detection
Summary: broken clock detection
Status: RESOLVED DUPLICATE of bug 292
Alias: None
Product: libsigrokdecode
Classification: Unclassified
Component: PD: parallel (show other bugs)
Version: unreleased development snapshot
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Nobody
Depends on:
Reported: 2018-12-16 23:54 CET by fenugrec
Modified: 2018-12-17 00:24 CET (History)
0 users

doesn't decode properly with the parallel PD (498 bytes, application/vnd.sigrok.session)
2018-12-16 23:54 CET, fenugrec

Note You need to log in before you can comment on or make changes to this bug.
Description fenugrec 2018-12-16 23:54:01 CET
Created attachment 502 [details]
doesn't decode properly with the parallel PD

Arguably this issue could be caused by something strange or malformed in my capture file, not necessarily a bug in the parallel PD.

With the attached capture, either with PV or sigrok-cli, using the "nWE" signal as a clock, I fail to get a single annotation from the PD.

Weirdness begins if I assign nWE to the PD's channel "d7" : then it interprets nWE as a clock ! sigrok-cli and PV behave the same. Sample commands : (didn't bother assigning all channels, just a minimum test case)

1) doesn't work, should work
sigrok-cli -i parallel_nWE.sr -P parallel:d0=8:d1=9:clk=nWE:clock_edge=falling
===> no annotations

2) doesn't make sense
sigrok-cli -i parallel_nWE.sr -P parallel:d0=8:d1=9:d7=nWE:clock_edge=falling
===> "parallel-1: 01" (correct data wrt the nWE negative edge, but... d7=nWE??)

This is with libsigrokdecode-0.6.0-git-23db450.
Comment 1 fenugrec 2018-12-17 00:24:06 CET
Didn't initially see the connection. This is pretty much a dupe of #292.

*** This bug has been marked as a duplicate of bug 292 ***