Posted
almost 7 years
ago
by
Uwe Hermann
We're happy to announce the release of libsigrokdecode 0.5.1. Tarballs are available from the Downloads page, as usual.
This is a "minor" release that doesn't change or remove any existing public API functions, so all existing clients will continue
... [More]
to work (without even the need to recompile).
The following new protocol decoders are now available:
ac97: Audio and modem control for PC systems
ds243x: Maxim DS243x series 1-Wire EEPROM protocol
maple_bus: Maple bus peripheral protocol for SEGA Dreamcast
morse: Demodulated morse code protocol
graycode: Accumulate rotary encoder increments, timing statistics
counter: Count number of edges
sda2506: Serial nonvolatile 1-Kbit EEPROM
rc_encode: PT2262/HX2262/SC5262 remote control encoder protocol
In total, we now support 85 different protocol decoders. If you're working on additional PDs, please send patches our way!
One of the more important changes to the backend is that the code has been changed to allow for multithreaded usage of the library (i.e., clients such as PulseView can now call libsigrokdecode API functions from different threads without any issues).
All protocol decoders shipped with libsigrokdecode have now been converted to the new PDv3 API that was introduced in libsigrokdecode 0.5.0. This usually means simpler and easier to understand protocol decoders as well as (quite massive, in some cases) performance improvements.
As mentioned in the 0.5.0 release notes, support for the old PD API has now been dropped, as all PDs have been converted to the PDv3 API. If you have any out-of-tree protocol decoders, please consider contributing them to mainline libsigrokdecode to benefit from such updates automatically. If that's not possible or desirable for some reasons, you can usually update your local PDs to the PDv3 API relatively easily (check the wiki page, or any of the 85 already converted PDs, for details).
See the NEWS file for a much more detailed list of changes, or browse the git history for even more details.
[Less]
|
Posted
almost 7 years
ago
by
Uwe Hermann
A new libsigrokdecode decoder that has been added a while back is graycode.
This PD allows decoding of gray code and rotary encoder protocols. Check out the source code for more details.
As usual there's a few sample files in sigrok-dumps and
... [More]
test-cases in the sigrok-test repository.
The decoder was contributed by Christoph Rackwitz, thanks a lot!
[Less]
|
Posted
almost 7 years
ago
by
Uwe Hermann
A new libsigrokdecode decoder that has been added a while back is graycode.
This PD allows decoding of gray code and rotary encoder protocols. Check out the source code for more details.
As usual there's a few sample files in sigrok-dumps and
... [More]
test-cases in the sigrok-test repository.
The decoder was contributed by Christoph Rackwitz, thanks a lot!
[Less]
|
Posted
almost 7 years
ago
by
Uwe Hermann
We're happy to announce the sigrok-firmware-fx2lafw 0.1.6 release. This is an open-source firmware that allows you to use almost any of the popular Cypress FX2 based devices as logic analyzers. It also supports a number of FX2 based USB
... [More]
oscilloscopes/MSOs like the Hantek 6022BE/BL or the Sainsmart DDS120.
The source code and pre-built firmware files are available from the usual place:
sigrok-firmware-fx2lafw-0.1.6.tar.gz
sigrok-firmware-fx2lafw-bin-0.1.6.tar.gz
This is a bugfix release (no new device support has been added), mainly fixing an issue that could cause non-working and/or prematurely aborted acquisitions with FX2 based logic analyzers on some systems (bug #655).
Additionally, FX2 based logic analyzers will now toggle pin PA1 during acquisition, and keep it high while idle. On fx2grok-tiny and fx2grok-flat devices there's a LED connected to PA1. Thus, those devices will visually indicate whether a firmware has been uploaded (LED will light up and stay like that while the device is idle). During any acquisition the LED will blink.
The NEWS file contains some more details.
[Less]
|
Posted
almost 7 years
ago
by
Uwe Hermann
We're happy to announce the sigrok-firmware-fx2lafw 0.1.6 release. This is an open-source firmware that allows you to use almost any of the popular Cypress FX2 based devices as logic analyzers. It also supports a number of FX2 based USB
... [More]
oscilloscopes/MSOs like the Hantek 6022BE/BL or the Sainsmart DDS120.
The source code and pre-built firmware files are available from the usual place:
sigrok-firmware-fx2lafw-0.1.6.tar.gz
sigrok-firmware-fx2lafw-bin-0.1.6.tar.gz
This is a bugfix release (no new device support has been added), mainly fixing an issue that could cause non-working and/or prematurely aborted acquisitions with FX2 based logic analyzers on some systems (bug #655).
Additionally, FX2 based logic analyzers will now toggle pin PA1 during acquisition, and keep it high while idle. On fx2grok-tiny and fx2grok-flat devices there's a LED connected to PA1. Thus, those devices will visually indicate whether a firmware has been uploaded (LED will light up and stay like that while the device is idle). During any acquisition the LED will blink.
The NEWS file contains some more details.
[Less]
|
Posted
about 7 years
ago
by
Uwe Hermann
libsigrokdecode yet again gained support for another protocol decoder: morse.
This decodes the well-known Morse code signals (recorded via oscilloscope or logic analyzer).
Have a look at the source code and/or the example file in the sigrok-dumps repo for details.
The decoder was contributed by Christoph Rackwitz, thanks a lot!
|
Posted
about 7 years
ago
by
Uwe Hermann
libsigrokdecode yet again gained support for another protocol decoder: morse.
This decodes the well-known Morse code signals (recorded via oscilloscope or logic analyzer).
Have a look at the source code and/or the example file in the sigrok-dumps repo for details.
The decoder was contributed by Christoph Rackwitz, thanks a lot!
|
Posted
about 7 years
ago
by
Uwe Hermann
If you're at this year's CCC Congress (34C3) December 27-30 in Leipzig, Germany, please feel free to drop by at the sigrok assembly.
We'll be there all 4 days of the congress (with the usual set of random test & measurement devices) for
... [More]
hackathons and random development discussions.
We're always happy to chat with users and contributors, hear about your feature requests and ideas for improvements etc. You can also bring your own devices, chances are we might be able to write drivers for some of the "simpler" devices right then and there, or at least grab some relevant information (photos, lsusb, possibly teardowns if you want).
Assembly location: Exhibition hall 2, c3nav (map). We have 4 seats (2 tables) near a wall.
[Less]
|
Posted
about 7 years
ago
by
Uwe Hermann
If you're at this year's CCC Congress (34C3) December 27-30 in Leipzig, Germany, please feel free to drop by at the sigrok assembly.
We'll be there all 4 days of the congress (with the usual set of random test & measurement devices) for
... [More]
hackathons and random development discussions.
We're always happy to chat with users and contributors, hear about your feature requests and ideas for improvements etc. You can also bring your own devices, chances are we might be able to write drivers for some of the "simpler" devices right then and there, or at least grab some relevant information (photos, lsusb, possibly teardowns if you want).
Assembly location: Exhibition hall 2, c3nav (map). We have 4 seats (2 tables) near a wall.
[Less]
|
Posted
about 7 years
ago
by
Uwe Hermann
If you're at this year's CCC Congress (34C3) December 27-30 in Leipzig, Germany, please feel free to drop by at the sigrok assembly.
We'll be there all 4 days of the congress (with the usual set of random test & measurement devices) for
... [More]
hackathons and random development discussions.
We're always happy to chat with users and contributors, hear about your feature requests and ideas for improvements etc. You can also bring your own devices, chances are we might be able to write drivers for some of the "simpler" devices right then and there, or at least grab some relevant information (photos, lsusb, possibly teardowns if you want).
This post will be updated with the exact location of the assembly as soon as we know the details.
[Less]
|