libsigrokdecode now supports the spdif decoder.
The Sony/Philips Digital Interface Format (S/PDIF) is a (nowadays standardized in IEC 60958) digital audio protocol that is used in various devices and supported by a number of ICs, such as the TI PCM2707 and many others.
A short description of the protocol is available on the respective wiki page, along with pointers to further reading.
Thanks a lot to Guenther Wenninger for contributing the decoder!
We're happy to announce that libsigrok now supports the Manson HCS-3xxx series of programmable power supplies (PPS).
Thanks a lot to Matthias Heidbrink for improving the driver and extending it to support more models in this series! See the model overview for more details. There are various rebadged versions sold by Conrad/Voltcraft, PeakTech, and probably other resellers.
All power supplies in this series have one channel only, featuring various voltage/current/power combinations though. They're connected to the PC via a (built-in) USB-to-serial IC (e.g. the SiLabs CP2102 in the Manson HCS-3202). A relatively simple ASCII-based protocol is used to communicate with the devices and control them.
You can control the power supplies e.g. via sigrok-cli like this:
$ sigrok-cli -d manson-hcs-3xxx:conn=/dev/ttyUSB0 --show
manson-hcs-3xxx - Manson HCS-3202 with 1 channel: CH1
Supported configuration options:
output_current: 0.000000
output_current_limit: 0.000000
output_enabled: on (current), off
output_voltage: 3.390000
output_voltage_target: 0.000000
$ sigrok-cli -d manson-hcs-3xxx:conn=/dev/ttyUSB0 --samples 2 -O analog
CH1: 3.300000 V DC
CH1: 0.000000 A
CH1: 3.380000 V DC
CH1: 0.000000 A
$ sigrok-cli -d manson-hcs-3xxx:conn=/dev/ttyUSB0 --config output_voltage_target=5.0 --set
$ sigrok-cli -d manson-hcs-3xxx:conn=/dev/ttyUSB0 --config output_enabled=yes --setThe code was tested on the Manson HCS-3202 and the Voltcraft PPS-11815. Please let us know if you are able to test any of the other devices the driver is supposed to support, and/or whether you experience any issues.
libsigrokdecode now supports yet another protocol decoder, rfm12.
This one decodes the SPI-based protocol of the HopeRF RFM12 and RFM12B wireless FSK transceiver modules. These devices can transmit and receive in the 433MHz, 868MHz and 915MHz bands (depending on chip).
Thanks a lot to Sławek Piotrowski for contributing the decoder (as well as an example file for sigrok-dumps)! We've also added a small test-case in the sigrok-test repository to be able to keep track of any potential regressions that might occur later.
So here I am hanging out at the local hacker space in Richmond. We, the group that meet up every Tuesday evening are small, yet perfectly formed. This evening Paul (MØTZO), a friendly radio ham, and co-founder of our group brought along an interesting device to encode GPS location data in APRS (Automatic Packet Reporting System) packets. These packets are fed into to a VHF radio transmitter which transmits the signal at 144.8 MHz. A network of receivers, run by amateur radio operators receives the packets, and streams them over the internet. An interesting device indeed.
Tonight we were just playing with Paul's GPS board, which contains a U-Blox Neo 6 GPS receiver. As with most GPS receivers, simply powering it on is enough to make it emit coordinates encoded in NMEA 0183 sentences transmitted over UART at 9600bps.
These are trivial to receive with an fx2-based logic analyzer and sigrok-cli:
$ sigrok-cli --driver=fx2lafw --config samplerate=50k \
--continuous -P uart:baudrate=9600:tx=0 -B uart=txWith the UART protocol decoder and the ASCII binary output, we can see the NMEA sentences:
Here we can see that we're locked on and receiving coordinates. "cat -v" is used to protect the terminal state from being clobbered by any errant binary data being emitted.
Yawn. Let's make this more interesting.
There is a very interesting package called gpsd. This is a GPS location server than can connect to various types of GPS devices, and can serve the position information over the network. And best of all, thanks to the power of UNIX pipes, we can feed the data from sigrok directly into it:
$ gpsd -N <(sigrok-cli --driver=fx2lafw --config samplerate=50k \
--continuous -P uart:baudrate=9600:tx=0 -B uart=tx)There are a variety of gpsd clients available. There's a nice ncurses based client, gpsmon:
And best of all, KDE's Marble integrates with gpsd. Here we see Marble, showing a live stream of location data captured by the fx2lafw firmware, decoded by sigrok, handled by gpsd, plotted by Marble on OpenStreetMap map data - a complete free-software stack! Pretty freetarded:
As in previous years various sigrok developers will be at the Chaos Communication Congress (31C3) in Hamburg, Germany. The conference takes place December 27th to 30th, 2014.
There will be a sigrok assembly (on all 4 days) with a few tables and chairs to allow for sigrok hacking and development planning, various demos and Q&A for visitors, and so on.
Apart from sigrok hacking the conference also features the usual set of awesome talks related to security, hardware hacking, and lots of other interesting topics that you shouldn't miss.
If you're interested in sigrok as user or developer, please drop by and say hello. Bring your gear (if possible) for reverse engineering and driver writing purposes. Chat with us, give us your suggestions which features you'd like to see, which devices you want to be supported, which protocol decoders you'd like to have, or even help us write some drivers/decoders!
We're happy to announce that libsigrokdecode now supports the am230x protocol decoder.
This PD decodes the custom protocol of the Aosong AM230x and DHT11 temperature and humidity sensors.
A short description of the protocol is available on the respective wiki page, along with pointers to further reading.
There are also a bunch of teardown photos of these sensors, in case you were wondering what those look like inside. Turns out they usually use some ST STM8S (or other) microcontroller and measure temperature and humidity "directly" without further ICs. The exception being the Aosong AM2303 which actually uses a Dallas/Maxim DS18B20 (1-Wire) sensor for the measurement.
Thanks a lot to Johannes Roemer for contributing the decoder!
We're happy to announce that libsigrokdecode now supports the pwm protocol decoder.
The PD was contributed by Torsten Duwe and Sebastien Bourdelin, thanks a lot!
This decoder will show the duty cycle of any signal, which in practice can mean various things. E.g. Class-D amplifiers can use PWM to encode audio data.
We have a test file in the sigrok-dumps repository containing audio data.
The decoder also supports a binary output facility which you can use to decode the audio (a direct export to WAV is planned as well, though).
$ sigrok-cli -i pwmtest.sr -P pwm:data=4 -B pwm=raw > PWM.raw $ sox -t raw -e unsigned -b 8 -r 64000 PWM.raw PWM.wav $ aplay PWM.wav
libsigrok now supports yet another multimeter, the MASTECH MS8250B.
This is a 4000 counts autorange DMM with USB connectivity (via an internal USB-to-serial IC built into the DMM).
Apart from the usual measurement ranges it also features a nice non-contact voltage detector functionality.
Thanks to Baruch Even for contributing and testing the code for this DMM (which is now part of the serial-dmm driver via a relatively small patch)!
We're happy to announce that libsigrokdecode now supports three new, closely related, protocol decoders: arm_tpiu, arm_itm, and arm_etmv3.
Here's a quick overview of the protocols that are decoded:
The data is captured on the SWO (TRACESWO) pin, e.g. on commonly available ARM SWD (serial wire debug) programmers/debuggers. Hint: libsigrokdecode also ships with an SWD decoder, if you're interested in that...
You can test the decoders with some sample files from the sigrok-dumps repository. If you optionally supply the location of ARM (cross-)toolchain utilities such as arm-none-eabi-objdump or arm-none-eabi-addr2line you can decode even more information, including source code snippets (see screenshot below)!
That opens up a whole new bunch of debugging possibilities; you can basically debug your code by not only tracing instructions but also tracing them in relation to other signals you're capturing with your logic analyzer at the same time (e.g. GPIOs you're toggling, UART, SPI, I²C, or whatever else may be going on in the system you're debugging)!
All three decoders were contributed by Petteri Aimonen (including sample *.sr files and a small test-suite for our sigrok-test repository), thanks a lot!
Happy debugging!
libsigrok now supports the BayLibre ACME device.
This a BeagleBone Black cape with an I²C-attached Texas Instruments INA226 current/power monitor and an I²C-attached TI TMP435 temperature sensor.
The sensors are supported in mainline Linux. The drivers expose a standard interface via the Linux sysfs pseudo file system, which the libsigrok driver uses.
The driver was contributed by Bartosz Golaszewski (of BayLibre), thanks a lot!
Bartosz will also present a Sigrok: Adventures in Integrating a Power-Measurement Device talk at the Embedded Linux Conference on March 24, 2015 (schedule) in San Jose, CA.
libsigrok now supports a new device class, tachometers! The first supported device of this type is the UNI-T UT372.
It's a USB-attached device (uses one of the WCH CH9325 ICs commonly found in UNI-T gear) that can measure RPM and counts.
The protocol of the device (now documented in the sigrok wiki) was reverse engineered by Mike Walters, using a somewhat unusual and quite interesting technique. Instead of the usual method of sniffing the USB traffic and then staring at hex numbers until things start to make sense, he used the following method:
After a first quick look at the USB traffic it was pretty clear that the packets usually look something like this:
070?<3=7<60655>607;007885
Now, instead of trying to figure out which bit and byte means what by looking at many of these packets, Mike instead generated his own packets that looked like the real packets from the UT372. He sent them to the vendor's PC software (via a custom-built "emulator" on a USB-enabled Arduino), which then interpreted and displayed the values and flags that it thought were sent by an actual UT372 device.
By randomly flipping bits in these packets and observing how the PC software's interpretation of the packets differed, Mike was able to figure out the individual protocol details a lot faster than using other methods.
Shortly after the protocol was known, Martin Ling wrote a libsigrok driver for the UT372 by hooking up a device-specific ut372 parser to the existing uni-t-dmm driver in libsigrok (which already handles the somewhat "special" CH9325 details).
Thanks a lot to Mike Walters and Martin Ling for their contributions!
It's been a while since the eeprom24xx protocol decoder was added to libsigrokdecode, but there hasn't been an "official" announce yet, so here goes.
The eeprom24xx PD can decode the I²C-based protocol of (almost) all 24xx series EEPROMs from various vendors.
Supported chips include for example the Microchip 24LC64 or 24AA025UID, the ST M24C01 or M24C02, the Siemens SLx24C01 or SLx24C02, and others. Various other chip families can be added relatively easily via chip spec entries in the decoder's lists.py file.
These ICs usually have only very few bytes of storage (e.g. 128 or 256 bytes), where the memory is organized into pages (the page size is e.g. 8 or 16 bytes). They usually support various types of accesses (command sequences) such as "byte write", "page write", "current address read", "random read", "sequential random read", "sequential current address read", and others.
Apart from a common command subset, some of the chips also support custom non-standard commands such as "set write protection" or "read write protection status" (on ICs that have write-protectable areas), and some others.
We're happy to announce that libsigrokdecode now supports the adns5020 PD, a decoder for the Avago ADNS-5020 optical mouse sensor protocol.
The decoder was contributed by Karl Palsson, thanks a lot!
It stacks on top of the common SPI PD and decodes ADNS-5020 specific registers reads and writes.
There is an example file in the sigrok-dumps repository if you want to test the decoder, as well as a test config in our sigrok-test repository.
We're happy to announce that libsigrok now supports the Maynuo M9812 digital load.
The driver was contributed by Aurelien Jacobs, thanks a lot!
It was written in a pretty generic way so that it probably also supports many of the other devices in the Maynuo M97 series of devices.
If you are able to test one of the other devices in that list, please let us know!
The hardware is attached via a (virtual) serial port and communication happens via a protocol on top of Modbus RTU (as documented in the user's guide)
There are also a bunch of teardown photos (plus links to the relevant ICs and their datasheets) of the device on the wiki page, if you're interested in that kind of stuff.
We're happy to announce that libsigrokdecode 0.3.1 has been released.
You can download the libsigrokdecode-0.3.1.tar.gz source tarball from sigrok.org/download as usual.
This is mostly a bugfix-release, the C library API was not changed. This means existing frontends that work with / are linked against libsigrokdecode 0.3.0 will continue to work just fine, without requiring relinking or recompiling.
However, some of the protocol decoders' output changed in ways which are not compatible with the state of the decoders in the last libsigrokdecode release. This means, if you're using any scripts to parse decoder output, or if you have any "private" protocol decoders that stack on top of one of those shipped with libsigrokdecode, you will have to do some adaptations. You're also encouraged to submit such decoders to be included in libsigrokdecode proper, of course!
In addition to all kinds of improvements and bugfixes in existing protocol decoders (PDs), you're probably most interested in what new protocol decoders are now supported (backported from git HEAD). So here's the list:
This adds up to currently 54 supported PDs in total.
Please check the libsigrokdecode NEWS file for the full list of user-visible changes in this release. As always, we're happy about bug reports, feature suggestions, comments about which protocol decoders you'd want supported next, or even better — patches :)
Happy decoding!
libsigrokdecode has had support for the jitter protocol decoder for a while now (it is already shipped with the recently-released libsigrokdecode 0.3.1), but this hasn't been officially announced yet, so here goes.
The decoder allows you to retrieve the timing jitter between two digital signals. This can be useful for a number of things, e.g. finding jitter/delay between a sender and receiver (be it wired or over some form of wireless communication), or for debugging your firmware interrupt setup by checking how much jitter you have between multiple consecutive invocations of the interrupt handler that should in theory always be equally spaced.
We also added a small test-case in our sigrok-test repository so we can ensure that the PD works fine (and continues to do so upon changes).
This protocol decoder has been contributed by Sebastien Bourdelin, thanks a lot!
Another protocol decoder that hasn't had an official announce yet is stepper_motor, a PD which decodes speed and position of a stepper motor.
The PD takes a "step" and "direction" pin as input.
You can select either steps or millimeters as unit for the decoder output.
As usual we also have a few sample dumps in the sigrok-dumps repository, and a few test-cases in sigrok-test.
The decoder was contributed by Petteri Aimonen, thanks a lot!
We're happy to announce that libsigrok now supports various weighing scales from KERN & SOHN GmbH.
The new kern-scale driver currently supports (and was tested on) the KERN EW 6200-2NM scale and all scales from the series which have the same protocol.
The scale can report the currently measured values (both unstable and stable ones) via the RS232 cable it ships with.
The protocol is a simple (14- or 15-byte) packet-based ASCII protocol containing the measured value, the unit (gram, ounce, etc.) and an indicator of whether the measured value is stable or not.
Support for other KERN scales with a different protocol can be added easily. Please let us know if you are able to test on other devices!
Usage example:
$ sigrok-cli -d kern-ew-6200-2nm:conn=/dev/ttyUSB0 --samples 10 Mass: 26.920000 g Mass: 26.920000 g Mass: 134.600006 ct UNSTABLE Mass: 134.600006 ct UNSTABLE Mass: 134.600006 ct UNSTABLE Mass: 134.600006 ct UNSTABLE Mass: 134.600006 ct Mass: 134.600006 ct Mass: 134.600006 ct Mass: 134.600006 ct
We're happy to announce that libsigrokdecode supports yet another new protocol decoder: mrf24j40.
This PD decodes the SPI-based protocol of the Microchip MRF24J40, an IEEE 802.15.4 2.4 GHz RF tranceiver chip.
As usual we also have a few sample dumps in the sigrok-dumps repository, and a few test-cases in sigrok-test.
The decoder was contributed by Karl Palsson, thanks a lot!
We're happy to announce that libsigrok now supports another PC oscilloscope, the Hung-Chang DSO-2100 (also sold under different brand names such as Voltcraft or Protek).
This is a 1999-era parallel-port based device with 30MHz analog bandwidth and 100MS/s samplerate.
The hardware (see also PCB shots) is somewhat non-trivial, it uses a QuickLogic FPGA, an Analog Devices DSP/microcontroller, some SRAM and Harris/Intersil ADCs. It also has some other properties or quirks you might be interested in.
The driver was contributed by Daniel Glöckner, thanks a lot!
Since this is the first parallel-port device in libsigrok, the build system also gained detection support for libieee1284, a cross-platform parallel port access library that the driver uses.