New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Bug #1188 #8
Conversation
description https://hyperrealm.github.io/libconfig/ function https://sigrok.org/wiki/Building#Installing_to_a_non-standard_directory_using_LD_LIBRARY_PATH per working directory for the devices used create a parameter set. ! Multiinstallations ! The configfile is libsigrok.cfg in /home/user/.config/sigrok. example: // dreamsourcelab-logic dreamsourcelabdslogic = ( // fx2lafw fx2lafw = ( // saleae-logic16 saleaelogic16 = ( }; With the comparison working directory (cwd), the modified driver retrieves its data record and assigns its variables. Because this is all the settings made in libsigrok can be used in all frontends. Special "default": the directory comparison ends with "not found". If the data is set under default. Overwrite parameters with frondend sigrok-cli / PV implementation
Record lib in makefile compile & tested Open / Todo
|
my libsigrok.conf |
Output of timestamps and real date at session start without debug level (printf). DSlogic driver with trigger timestamp output. Triggerstamp I would like to have solved centrally at session.c . Unfortunately, processing at the intended locations depends on the debug level. So far only implemented in one driver. This change can be used to log long-term post-trigger events (eg, troubleshooting triggers that rarely occur and have a time reference to other environmental behaviors). Or even with decoder support signal behavior can be logged completely time. e.g .: ./sigrok-cli -i ~ / Downloads / dcf77_1800s.sr --channels DATA -P timing: data = DATA: edge = rising | awk 'NR% 2' | awk '{if ($ 3 == "s") print $ 2, SUM + = $ 2; else if ($ 3 == "ms") print $ 2/1000, SUM + = ($ 2/1000); else if ($ 3 == "μs") print $ 2/1000000, SUM + = ($ 2/1000000)} ' Output: (Differnz to the previous edge: total time (timestamp) to the first edge)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look promising, will test later on hardware, thanks! The struct contents did indeed change multiple times in the past (in the vendor software). The state we have right now in libsigrok was correct for DSView 0.95 but we now use the 0.97 firmware/bitstream so your fix is indeed correct.
Minor request: Please don't change the indentation, should still be 1 tab. "unsigned char" should remain "uint8_t" as well.
All other changes in this pull request seem unrelated to the DSLogic triggering issue (Bugzilla bug #1188) so those should be in extra branches and extra pull requests please. For the "driver read parameters from conf file (user space)" changes there's no need to re-post them as extra branches / pull-request though, I'm afraid that one will not be merged upstream for many reasons, including additional dependencies and more importantly architectural issues. You're free to use that one locally if you want of course, but it's not desirable for upstream unfortunately. |
Unfortunately, I'm not clear what is taken over immediately and for what I have to open a branch commit 920689c -> ??? 136ee78 conf, no branch, because no takeover bb16e54 I set up a branch and set a new pull request |
The #1188 fix is merged as 10481ef, thanks! |
NOTE: Once the device is connected and has entered the command mode (0x51), every following byte will be interpreted as a bit mask for switching relays. There is no way to leave the command mode! IMPORTANT: When reconnecting to the device (e.g. with sigrok-cli or SmuView) the connect will fail and the "query device"-command (0x50) will be interpreted as a bit mask and will turn on relays sigrokproject#1-sigrokproject#4, sigrokproject#6 and sigrokproject#8. You have to power cycle the device to be able to reconnect!
NOTE: Once the device is connected and has entered the command mode (0x51), every following byte will be interpreted as a bit mask for switching relays. There is no way to leave the command mode! IMPORTANT: When reconnecting to the device (e.g. with sigrok-cli or SmuView) the connect will fail and the "query device"-command (0x50) will be interpreted as a bit mask and will turn on relays sigrokproject#1-sigrokproject#4, sigrokproject#6 and sigrokproject#8. You have to power cycle the device to be able to reconnect!
NOTE: Once the device is connected and has entered the command mode (0x51), every following byte will be interpreted as a bit mask for switching relays. There is no way to leave the command mode! IMPORTANT: When reconnecting to the device (e.g. with sigrok-cli or SmuView) the connect will fail and the "query device"-command (0x50) will be interpreted as a bit mask and will turn on relays sigrokproject#1-sigrokproject#4, sigrokproject#6 and sigrokproject#8. You have to power cycle the device to be able to reconnect!
change wrong position for triggermarker ^ output/bits.c,hex.c,ascii.c
New margin by channelname