Quantcast
Channel: The ever-expanding world of sigrok
Viewing all 222 articles
Browse latest View live
↧

sigrok at the Chaos Communication Congress (31C3)

December 7, 2014, 3:21 pm
$
0
0

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!

 

↧
Search

New protocol decoder: Aosong AM230x / DHT11

December 28, 2014, 1:26 pm
$
0
0

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!

↧
↧

New protocol decoder: PWM

January 18, 2015, 11:42 pm
$
0
0

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

 

↧

MASTECH MS8250B supported

February 28, 2015, 1:21 pm
$
0
0

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)!

 

↧

New protocol decoders: ARM TPIU, ITM, ETMv3

March 3, 2015, 7:32 am
$
0
0

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 TPIU (Trace Port Interface Unit) is a stream formatter and multiplexer that combines data from several sources into one stream. It is used inside an ARM-based microcontroller or SoC to combine ITM and ETM trace output into a single port.
  • ARM ITM (Instrumentation Trace Macroblock) allows tracing of software events, and also with the help of DWT (Debug, Watchpoint and Trace) the tracing of exceptions and data watchpoints. It also supports periodic sampling of PC values.
  • ARM ETM (Embedded Trace Macroblock) allows tracing of every instruction executed on the CPU. Currently only ETM version 3 (the newest version, present in Cortex-M3 and other ARMv7-m) is supported.

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!

 

↧
↧

BayLibre ACME now supported

March 5, 2015, 2:18 am
$
0
0

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.

 

↧

UNI-T UT372 now supported

March 26, 2015, 1:41 am
$
0
0

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!

 

↧

New protocol decoder: 24xx I²C EEPROM

April 6, 2015, 11:25 pm
$
0
0

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.
 

↧
Search

New protocol decoder: Avago ADNS-5020

June 30, 2015, 4:38 pm
↧
↧

Maynuo M9812 now supported

July 9, 2015, 11:20 am
$
0
0

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.

↧

libsigrokdecode 0.3.1 released!

July 12, 2015, 2:58 pm
$
0
0

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:

  • adns5020: Bidirectional command and data over an SPI-like protocol
  • am230x: Aosong AM230x/DHTxx/RHTxx humidity & temperature sensor
  • arm_etmv3: Decode ETM instruction trace packets
  • arm_itm: Trace data from Cortex-M / ARMv7m ITM module
  • arm_tpiu: Filter TPIU formatted trace data into separate streams
  • eeprom24xx: 24xx series I²C EEPROM protocol
  • jitter: Retrieves the timing jitter between two digital signals
  • mdio: Half-duplex sync serial bus for MII management between MAC and PHY
  • mrf24j40: IEEE 802.15.4 2.4 GHz RF tranceiver chip
  • nrf24l01: 2.4GHz transceiver chip
  • pwm: Analog level encoded in duty cycle percentage
  • rfm12: HopeRF RFM12 wireless transceiver control protocol
  • spdif: Serial bus for connecting digital audio devices
  • stepper_motor: Absolute position and movement speed from step/dir
  • swd: Two-wire protocol for debug access to ARM CPUs
  • tca6408a: Texas Instruments TCA6408A 8-bit I²C I/O expander
  • timing: Calculate time between edges

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!

↧

New protocol decoder: Jitter

July 21, 2015, 6:08 am
$
0
0

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!

↧

New protocol decoder: Stepper motor

July 26, 2015, 8:08 am
$
0
0

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!


 

↧
↧

KERN scale series supported

August 31, 2015, 4:19 am
$
0
0

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

 

↧

New protocol decoder: Microchip MRF24J40

September 9, 2015, 7:33 am
$
0
0

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!

↧
Search

Hung-Chang DSO-2100 supported

September 16, 2015, 12:52 am
$
0
0

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.

 

↧

GW Instek GDS-800 series supported

October 1, 2015, 10:37 am
$
0
0

We're happy to announce that the GW Instek GDS-800 oscilloscope series is now supported in libsigrok.

These are devices ranging from 60MHz bandwidth up to 250MHz, with a samplerate of 100MSa/s (or 25GSa/s for equivalent-time sampling).

They have RS232 connectivity per default, but there are also options to extend them with GPIB or USB ports. A (publically documented) SCPI-based protocol is used for the communication.

The scopes are also sold under the Voltcraft brand name (and the code was actually tested on a Voltcraft DSO-6060C).

The driver was contributed by Martin Lederhilger, thanks a lot!

 

↧
↧

New protocol decoder: Modbus

October 6, 2015, 10:28 am
$
0
0

Yes, it's that time of the week again — libsigrokdecode supports yet another protocol decoder since somewhat recently: modbus.

In the current state the PD stacks on top of the UART decoder and decodes the Modbus RTU protocol. Support for e.g. Modbus ASCII may be added later (to the same PD), possibly also Modbus TCP or other variants (as an extra decoder).

Check the PD's wiki page or Wikipedia for some more info on Modbus in general.

As always, we have a few example files in the sigrok-dumps repo and some test-cases in the sigrok-test repo.

The decoder was contributed by Bart de Waal, thanks a lot!

 

↧

New protocol decoder: Qi

October 16, 2015, 7:03 am
$
0
0

Another somewhat recently added protocol decoder for libsigrokdecode is the qi PD.

This PD decodes demodulated data streams used by the Qi standard for communication from the receiver to the charging station. You can read more about the Wireless power consortium's Qi standard on Wikipedia.

As always, we have a few example files in the sigrok-dumps repo and some test-cases in the sigrok-test repo.

The decoder was contributed by Josef Gajdusek, thanks a lot!

↧

New protocol decoder: ir_nec

March 14, 2014, 12:05 pm
$
0
0

We're happy to announce that libsigrokdecode now supports yet another protocol decoder, this time: ir_nec. The PD has been contributed by Gump Yang, thanks a lot!

This is a decoder for the so-called NEC infrared (IR) protocol, a rather widely used protocol for remote controls (for TVs, VCRs, and lots of other things).

The protocol is based on a pulse-distance encoding, i.e., a 1 bit is encoded by a pulse and a long pause after that, and a 0 is encoded by a pulse and a short pause after the pulse.

The "payload" basically consists of an 8-bit address (which is a number that is supposed to be unique for a certain vendor / device), and an 8-bit command / code which identifies which button was actually pressed.

The 8-bit address is followed by the inverted 8-bit address, the 8-bit code is also followed by its inverse. This is (or can be) used for error checking on the receiver side.

You can read up on the protocol details in various online resources.

When the proper definitions for specific remote controls are added to the PD, it can also decode the actual remote control button in a more human-readable form e.g. "Matsui TV: Mute" vs. "Address: 0x40, command: 0x10", see screenshot for an example.



 

↧
Viewing all 222 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>