sigrok - User contributions [en]

Talk:Libsigrok

2022-12-28T19:22:24Z

PeterMortensen: /* Broken links */ new section

== Broken links ==

The three links ending with ''"... API documentation"'' (e.g., ''"C++ bindings API documentation"'' ) are broken (IRC
2022-12-23T171629Z+0).

--[[User:PeterMortensen|PeterMortensen]] ([[User talk:PeterMortensen|talk]]) 20:22, 28 December 2022 (CET)

User:PeterMortensen

2022-12-16T22:51:49Z

PeterMortensen: /* Shortcuts */ Added an item.

==Recent activity==

===2020-01===

Getting insight into what happens with PC keyboards on the signal level and on higher levels (related to repurposing an old PS/2 keyboard (BTC 5349) as a macro keyboard, with the help of an [https://store.arduino.cc/arduino-leonardo-with-headers Arduino Leonardo]):

#For the keyboards listed below: Verify that all keys work (by capturing in PulseView and observe there is actually a signal. Note that the accent and umlaut key requires pressing a letter after).
#For the keyboards listed below: Capturing and submitting information for PS/2 PC keyboards (CLK and DATA), including during pressing and releasing and bidirectional traffic (PC initialising the keyboard, e.g. at connect and/or PC startup). Submit to Git repository "[https://sigrok.org/gitweb/ sigrok-dumps]": Keyboards (all European layout):
##BTC 5349 (102 keys IBM/AT type, corresponding to IBM Model M (Enhanced)). 100 mA (measured). Mechanical keyboard?
##Fujitsu/Siemens ([https://en.wikipedia.org/wiki/File:ISO_keyboard_%28105%29_QWERTY_UK.svg 105 keys] + 10 media keys (sleep, mail, play, stop, speaker controls, etc.). IBM/AT type. ?? mA.
##Microsoft ''"Natural Keyboard Elite"''. [https://en.wikipedia.org/wiki/File:ISO_keyboard_%28105%29_QWERTY_UK.svg 105 keys]. 500 mA (nominal).
##[https://en.wikipedia.org/wiki/Apple_Extended_Keyboard Apple Extended Keyboard II]. [https://en.wikipedia.org/wiki/File:ISO_keyboard_%28105%29_QWERTY_UK.svg 105 keys] + one power key. ??? mA. Mechanical keyboard. Uses [https://en.wikipedia.org/wiki/Apple_Desktop_Bus#Physical ADB], not PS/2 (physically similar, but 4-pin mini-DIN connector). A single pin for data and 'PSW' connected directly to the power switch. All communication is host initiated (polling).
#Consider adding regression tests for the PS/2 decoder. It will include if it handles the 2-3% clock frequency offset for the BTC 5349 (probably, as there is CLK, but that is not the case if decoding as the UART protocol decoder).
#Some higher-level protocol decoder work for PC keyboards (not decided on yet), e.g. identifying scan code sequences as the corresponding keys.
#Some hardware to allow an Arduino Leonardo to pose as a PC ([https://en.wikipedia.org/wiki/Open_collector open collector] outputs). To explore what commands various keyboards responds to and what modes they might enter (for example, Linux allegedly tries put keyboards into "Set 3" (the powerup default is usually "Set 2")). The three LEDs on the keyboard can also be used for user feedback for the macro keyboard.
#Existing content on the wiki, etc. regarding PC keyboards, etc.:
##Keyboards (none found, but are probably not supposed to exist, only actual capturing hardware(?)).
##[[Protocol_decoder:Ps2|PS/2 decoder page]]. Does not exist??
##''"The decode of some PS/2 (or USB) keyboard/mouse traffic could yield an ASCII text file of all the keys that were pressed on the keyboard."'' (on [[Protocol decoder output|a planning page]])
##Look in bug tracker for PS/2, keyboards, etc.
###Bug #1460 - [https://sigrok.org/gitweb/?p=libsigrokdecode.git;a=commitdiff;h=4370348c4fcdbd708715c35a38fdf06c9364d518 ps2: end data byte at rising clock edge of the stop bit]
##Look in Git log
### [https://sigrok.org/gitweb/?p=sigrok-dumps.git;a=commit;h=16931eb480ba5df923c1508f3d83719eddcc5ab3 PS/2 keyboard data submitted on 2019-12-21] (discovered on [https://sigrok.org/gitweb/?p=sigrok-dumps.git;a=log projects / sigrok-dumps.git / commit ])
##Look in IRC log
##Look in blog posts for info on PS/2, etc.
#Updating the wiki
##Add PS/2 low-level reference (details about the CLK signal) to the PS/2 protocol decoder page. IRC ref. [2020-01-07 01:49:07] and [2020-01-07 18:09:02] (UTC+1)). Add to the resources section. Is: http://www.nerdkits.com/videos/interrupts_and_ps2_keyboard/
##Add keyboard documentation, pictures (not decided on yet).
#Ideas:
##Deliberately send data to the keyboard with a parity error.
##Deliberately add noise to the signals (say, wide-band white noise by electronics means), forcing parity errors. This should force the receiver (keyboard or host PC) to respond.
##Send unknown commands to the keyboard. It should respond with 0xFE (in contrast to the normal 0xFA).
##Try all the keyboard commands in ''[https://www.win.tue.nl/~aeb/linux/kbd/scancodes-12.html Keyboard commands]''.
##For a keyboard that is ''both'' capable of USB and PS/2: Record the startup sequence when connected via PS/2 to a PC host. To see if there is any indication on the signal level of such capability.

Other:

#Updating broken links here. For example, for the CAN protocol decoder.

===2019-04===

#Building a Docker container for compiling sigrok-cli and PulseView. It is supposed to both run under Linux and Windows (x64).
#Testing a new driver by user ''droghio'' that should work for the [[Tektronix TDS2024B|TDS2024C Tektronix oscilloscope]]. Some placeholding:
#*Part of "lsusb -v" output: "Bus 008 Device 005: ID 0699:03a6 Tektronix, Inc."
#*Notes to self: the ''"[git://sigrok.org/sigrok-util util]"'' repository (for building and stuff) - [https://github.com/sigrokproject/sigrok-util read-only mirror at GitHub]. [https://github.com/sigrokproject/sigrok-util/blob/master/cross-compile/linux/sigrok-cross-linux Cross-built script].

===2018-04===

Submitting comprehensive sample data for CAN bus, both 11-bit and 29-bit messages, and corresponding test cases (mostly for regression test - especially regression for [https://sigrok.org/bugzilla/show_bug.cgi?id=1085 the 2018-04-12 fix to the decoding at the end of the CRC part]).

Notes to self:

# Original acquired analog data: C:\temp2\2017-12-23\CAN decoder, new stuff bit handling at the end of the CRC segment\Data67\In\ACQ000009_Tektronix.txt

===2017-12===

Recording 22483 traces for the purpose of evaluating [https://sigrok.org/bugzilla/show_bug.cgi?id=1085 a proposed fix to the CAN protocol decoder] (actually only changing a single number from 16 to 17), stuff bit at the very end of the CRC segment, with a modified trigger scheme:

* Change the position of the trigger point to the end (right) so there is always a CAN message in the trace (for the previous), but still 26 µs recessive.

The time division was 100 µs / division (about 225 bit times max) to always record whole CAN messages - at 10 samples per bit time.

===2017-07===

Using the sigrok command-line ("sigrok-cli") to bulk process data derived from Tektronix oscilloscope data of 250 kbit/s CAN traffic on a real-world system (mobile cranes). The first sample data set is 5335 oscilloscope traces obtained with the trigger set to a negative pulse on CAN-H (to start off at the end of a CAN message) - corresponding to 6.5 recessive bits, 26 µsec (detecting the space in-between CAN messages). Sometimes there is a CAN message right after this, sometimes it is a bit delayed, and sometimes it is completely empty.

A sample command line (on Windows) is:

<pre>sigrok-cli -P can:bitrate=250000:can_rx="CAN RX" -P timing:data="CAN RX" -I csv:header=true:samplerate=5000000 -i "T:\stdHMF\UserData\scripts\Tektronix2PulseView\_PulseView_AllChannels_ACQ000001_Tektronix_f5000000.txt"</pre>

===2017-04===

Using [[PulseView]] to decode data from a Tektronix oscilloscope of SPI communication to a CAN controller, [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010406 MCP2515].

==Task list==

Currently not in priority order.

* Allow import of analog data through CSV files. (Related: fixed [https://sigrok.org/bugzilla/show_bug.cgi?id=1064 bug 1064] - ''locale'' issue, decimal point, "," vs. ".".).

* Add detection of error frames to the CAN protocol decoder

* Add support for the gigga watt EEVBlog multimeter (Bluetooth, etc.)

* Add a snap feature to the "cursor" (blue) in PulveView

* Change number of significant digits for the time display in the "cursor" (blue) in PulveView

* Submit selected sample traces for CAN decoder change (for CRC segment) validation. With and without stuff bits in various places. With and without timing deviations. (Related: [https://sigrok.org/bugzilla/show_bug.cgi?id=1085 bug 1085], celeron55's fix, '''''if len(self.bits) > self.last_databit + 16''''' → '''''if len(self.bits) > self.last_databit + 17''''' (16 → 17)).

* Add support for the [[Tektronix TDS2000B series|TDS2000]] series in libsigrok, and thus, by extension, use by the new shiny stuff in PulveView.

===On wiki===

* Change recommended procedure for submitting sample Sigrok files (traces), on ''[[Example dumps#Contributing dumps|Example dumps]]''.

==Glossary==

*''BBB'' [https://en.wikipedia.org/wiki/BeagleBoard#BeagleBone_Black BeagleBone Black]
*''GH'' [http://en.wikipedia.org/wiki/GitHub GitHub]
*''ISTR'' ????
*''LA'' Logic analyser
*''ML'' Mailing list
*''OLS'' ????
*''PR'' Pull request (a Git term). ''Not'' "problem report".
*''SR'' Sigrok
*''srd'' ????
*''WIP'' Work in progress. Mostly related to particular Git commits.
*''PD'' protocol decoder. Non-standard spellings are ''Pd'' and ''pd''.
*''PV'' PulseView. Non-standard spellings are ''Pv'' and ''pv''.

==Some bug reports==

* [https://sigrok.org/bug/1155 Possible problem with the MSO-19 USB driver on Windows]. PulveView crashes at startup if the MSO-19 is connected.

==Interests==

I am mostly interested in:

* The [[CAN|CAN protocol decoder]] (that page is currently empty, but it is listed on [[Protocol decoders|the protocol decoders page]])
* CAN bus loggers, like IXXAT's (now acquired by HMS) ''USB-to-CAN compact''/''USB-to-CAN V2'' and Kvaser's ''Memorator''.
* The higher-level [http://en.wikipedia.org/wiki/CANopen CANopen] protocol (on top of CAN)

==Protocol decoders==

===Non-empty wiki pages===

Currently (2017-07-08), 28
of 77 [[Protocol_decoders#Supported protocol decoders|protocol decoders]] (36%) have non-empty pages here on the wiki:

*[[Protocol decoder:Adns5020|ADNS5020]]
*[[Protocol decoder:Am230x|AM230X]]
*[[Protocol decoder:Arm etmv3|ARM ETMV3]]
*[[Protocol decoder:Arm itm|ARM ITM]]
*[[Protocol decoder:Arm tpiu|ARM TPIU]]
*[[Protocol decoder:Aud|AUD]]
*[[Protocol decoder:Avr pdi|AVR PDI]]
*[[Protocol decoder:Dcf77|DCF77]]
*[[Protocol decoder:I2c|I²C]]
*[[Protocol decoder:Ir nec|IR NEC]]
*[[Protocol decoder:Modbus|Modbus]]
*[[Protocol decoder:Mrf24j40|MRF24J40]]
*[[Protocol decoder:Nrf24l01|NRF24L01]]
*[[Protocol decoder:Nunchuk|Nunchuk]]
*[[Protocol decoder:Pan1321|PAN1321]]
*[[Protocol decoder:Parallel|Parallel]]
*[[Protocol decoder:Pwm|PWM]]
*[[Protocol decoder:Qi|Qi]]
*[[Protocol decoder:Rfm12|RFM12]]
*[[Protocol decoder:Rgb led spi|RGB LED SPI]]
*[[Protocol decoder:Rtc8564|RTC8564]]
*[[Protocol decoder:Spdif|SPDIF]]
*[[Protocol decoder:Spi|SPI]]
*[[Protocol decoder:Spiflash|SPI flash]]
*[[Protocol decoder:Stepper motor|Stepper motor]]
*[[Protocol decoder:Tlc5620|TLC5620]]
*[[Protocol decoder:Uart|UART]]
*[[Protocol decoder:Z80|Z80]]

==Meta==

===Creating sub pages for proposals===

E.g., to work on drafts and proposals for new or old wiki entries, without affecting the main wiki (this is not specific for this project). Add this non-existent link ("IRC shenanigans" is an example) somewhere on the user page (it can be deleted later if the reference is not needed):

<syntaxhighlight lang="none">
[[User:PeterMortensen/IRC shenanigans]]
</syntaxhighlight>

Rendered:

[[User:PeterMortensen/IRC shenanigans]]

Open that page and add some content.

==Profile==

Profile: see [http://en.wikipedia.org/wiki/User:Mortense my Wikipedia user page].

Credentials: more than 5000 edits on the English Wikipedia.

==Shortcuts==

* [https://sigrok.org/doc/pulseview/0.4.1/manual.html PulseView manual]
* [[Sigrok-cli|sigrok-cli man page]]
* [https://plus.google.com/communities/109843678338531936878 Google+ group for sigrok] (now defunc as Google+ closed down)
* [[PulseView]]. Includes the command line to get the source code using Git.
* [[Downloads#Windows_Download|PulseView, Windows binaries]] (nightly - development). [[Windows#Windows_installers|Alternative location]] (but it seems redundant).
* [[Downloads#Linux_AppImage_binaries|PulseView, Linux binaries]] (nightly - development).
* [[Example dumps|Example data dumps]] - sample data in .sr format. Also includes instructions on how to contribute new ones. Includes the command line to get the whole thing using Git (as of 2017-11-26, 2286 "objects", 724 .sr files, about 65 MB in download size, 192 MB on disk).
* [[Special:Random|Random page]]
* [https://sigrok.org/jenkins/job/sigrok-native-appimage/ Native app image] (not official yet). Is for Linux and x86 only. See also [https://en.wikipedia.org/wiki/AppImage AppImage] (Wikipedia).
* [[Press]]. List of annotated links, mostly blog posts.
* [[Probe comparison]]
* [[Link Instruments MSO-19|MSO-19]]. Mixed oscilloscope and logic analyser by Link Instruments that (or rather its driver) crashes PulveView at startup when connected (until some time in mid 2018(?)). Some reverse engineering has been done in 2012, but it is not supported (has status "Planned"). [https://sigrok.org/bugzilla/show_bug.cgi?id=1155 Sigrok bug report for the crash]. [http://www.linkinstruments.com/doupdate_mso19.htm Software download page for it.]
* [[Windows|sigrok, Microsoft Windows page]]
** [[Windows#Device specific USB driver|Device specific USB driver - WinUSB - Zadig]]
* [[AR488]], an Arduino-based [https://en.wikipedia.org/wiki/IEEE-488 GPIB]-to-serial port adapter. That is, serial over USB. And serial on the host side.

===Protocol decoders===

* The [[CAN|CAN bus protocol decoder]]
* [[Protocol decoder HOWTO]]
* [[Protocol decoder API]]
* [[Protocol decoders#Supported protocol decoders|Supported protocol decoders]]

===Building sigrok===

* On Debian (e.g. Raspberry Pi): [[Linux#Installing the requirements 2|Installing required software]]
* On Debian (e.g. Raspberry Pi): [[Linux#Building 3|Actual build]]
* Alternative to following the wiki pages: [https://sigrok.org/gitweb/?p=sigrok-util.git;a=blob;f=cross-compile/linux/sigrok-cross-linux;h=2c8e559efde8cf6ae9a365bf1a4324a33600fae7;hb=HEAD a script that will do most of it]. (''[sigrok-util.git] / cross-compile / linux / sigrok-cross-linux'')
* Windows:
**On Windows: [[Windows#Native_build_using_MSYS2|Native build using MSYS2]] (but may not really work - sigrok-cli and PulseView are listed as not working).
**[[Windows#Cross-compile_using_MXE|Cross compile on Linux]] (using [http://mxe.cc/ MXE]). The script is [https://sigrok.org/gitweb/?p=sigrok-util.git;a=blob;f=cross-compile/mingw/sigrok-cross-mingw;h=8330406ecd28969d8d29c8ad23df8968a4b9ec68;hb=HEAD /sigrok-util/cross-compile/mingw/sigrok-cross-mingw]. Used for nightlies? [https://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=debug,platform=cross-i686-w64-mingw32/ Jenkins page for the debug version].
* The Jenkins thingy - automatic build, e.g. nightlies for PulseView and "AppImage" (self-contained executable for x86 Linux). Sample: [https://sigrok.org/jenkins/job/sigrok-cli/ sigrok-cli] with 44 configurations (43 cross-compiles), e.g. cross-x86_64-w64-mingw32 (for Windows 64-bit?).
* The [[Building#Installing_to_a_non-standard_directory_using_LD_LIBRARY_PATH|LD_LIBRARY_PATH trick]]

AR488

2022-12-16T22:44:43Z

PeterMortensen: Some copy editing (e.g. ref. <https://en.wiktionary.org/wiki/adapter#Noun>, <https://docs.arduino.cc/hardware/uno-rev3>, <https://en.wikipedia.org/wiki/RS-232>, <https://en.wiktionary.org/wiki/out-of-band#Adjective>, <https://en.wikipedia.org/wiki/ATmega328#Family>, <https://www.microchip.com/wwwproducts/en/ATmega32U4>, and <https://en.wikipedia.org/wiki/GitHub>).

= AR488 GPIB to UART/USB =

The [https://github.com/Twilight-Logic/AR488 AR488] is an Arduino-based [[Protocol_decoder:Ieee488 | GPIB]] to serial port adapter. The firmware runs on Uno (and thus Nano), Mega as well as Leonardo boards. The PC sees a USB or RS-232 attached COM port, transmit data is sent to the device, and the device's response is seen as receive data. Out-of-band commands prefixed by ''++'' can control the adapter's behaviour. The AR488 is accessible to interactive sessions in a terminal program, as well as can serve as a SCPI-over-serial "cable".

With '''one device per adapter''' (specific GPIB address and communication parameters stored in the '''AR488''' adapter) '''support is transparent'''. When the adapter is connected to multiple devices at the same time, then "out-of-band" communication is required (the above mentioned ++ commands), which sigrok does not provide.

== Hardware ==

* Arduino Uno or Nano (ATmega328P based), or Mega (ATmega2560 based), or Leonardo or Pro Micro (ATmega32U4 based)
* Centronics 24-pin connector

See the AR488-manual.pdf in the firmware source tree for schematics. Wires run from the Arduino board to the Centronics connector, and driver chips are not involved. This keeps the component count low, the wiring simple, and the mechanical construction compact (especially with Nano boards which can execute the Uno firmware). In theory, any bare serially attached ATmega chip would do, but the firmware happens to be written in the Arduino IDE's language (it uses libraries and build support, and won't work outside of the IDE without modifications).

The primary goal of the project is to enable quick access to GPIB attached devices. Typical use is to have one adapter per device (it's rather low cost, so that's not an issue). The lack of proper drivers means that the adapter cannot handle a full bus. The limit is said to be somewhere around three or four devices, before signals go out of spec and communication need not work reliably any longer. For larger setups with many devices, a proper full-blown adapter with appropriate driving capabilities is recommended.

== Photos ==

<gallery>
File:Ar488-artag-pcb-top.png|<small>AR488 on PCB with Pro Micro</small>
File:Ar488-artag-pcb-conn.png|<small>AR488 on PCB with Pro Micro</small>
File:ar488-diy-sniff-top.png|<small>AR488 wire wrap with Nano, top, GPIB and UART signals accessible for recording</small>
File:ar488-diy-sniff-bot.png|<small>AR488 wire wrap with Nano, bottom</small>
</gallery>

== Protocol ==

See the AR488-manual.pdf document for a protocol description. The AR488 firmware passes the PC's outgoing data to the GPIB instrument, and the GPIB instrument's data to the PC. Commands start with the ''++'' prefix and affect the adapter's operation. The AR488 firmware implements most of the Prologix commands, and a few more. Macros (both executed at runtime as well as at firmware start) are supported.

How to use the AR488 adapter:

* (Optional, see below) Modify the firmware to enable the macro feature and especially the startup macro (remove comment leaders from disabled defines).

#define MACROS
#define STARTUP

* (Optional, see below) Locate the startup_macro[] definition and adjust it to match your use case. Here is an example.

++addr 20
++auto 2

* (Optional, see below) Compile and upload the firmware into the adapter.

* (See above for custom firmware) Regular common firmware can interactively get configured and that configuration can get stored in the adapter. Which eliminates the necessity for custom builds, and ++ commands at the start of a session. See the AR488 manual which parameter values get stored and applied upon firmware startup.

++ addr 20
++ auto 2
++ '''savecfg'''
++ rst

* Open a terminal program and run a few commands.

$ screen /dev/ttyUSB0 115200
*idn?
conf?
read?
++repeat 15 4000 read?

* Use the adapter with GPIB aware applications, like sigrok's SCPI over serial.

$ sigrok-cli -d scpi-dmm''':conn=/dev/ttyUSB0''':serialcomm=115200 --scan

* Alternative mix of interactive and programmatic use.

$ screen /dev/ttyUSB0 115200
++ addr 22
++ auto 2
(close terminal session)
$ sigrok-cli -d scpi-dmm:conn=/dev/ttyUSB0:serialcomm=115200

BEWARE! Depending on the specific implementation of the Arduino board, the adapter may restart when the serial port gets opened, and the volatile configuration may not take effect at all. This is an implementation detail of deriving a RESET signal from the DTR handshake, motivated by automatically entering bootloaders without the user's intervention. Consider the ++savecfg approach outlined above instead.

== Resources ==

* Twilight Logic's [https://github.com/Twilight-Logic/AR488 GitHub repo], contains firmware sources and documentation
* EEVBlog [https://www.eevblog.com/forum/projects/ar488-arduino-based-gpib-adapter/ forum thread]

[[Category:GPIB interface]]
[[Category:Supported]]

User:PeterMortensen/IRC shenanigans

2022-12-02T19:32:30Z

PeterMortensen: Copy edited.

== Using IRC with the sigrok project ==

The easiest is using [https://web.libera.chat/#sigrok the web interface], but it also times out after a relatively short time, about one hour.

The expected response time can be up to 24 hours if posting at certain times of the day. Thus be sure somebody is actually active at the time you post. About 1900 hours UTC is usually a good time.

A better solution is to download and configure an IRC client, for instance [https://en.wikipedia.org/wiki/Irssi Irssi] (on Unix-like systems) and [https://en.wikipedia.org/wiki/ChatZilla ChatZilla] on Windows (though it is on its way out due to the move by Firefox/Mozilla to "[https://en.wikipedia.org/wiki/Firefox#Firefox_Quantum Quantum]" in 2017). This can also, if configured for it, log all traffic so you don't miss out on anything. For instance, a [https://en.wikipedia.org/wiki/Raspberry_Pi Raspberry Pi] (even a first generation one, with low power consumption), can be set up with Irssi to log all traffic 24x7. It can also be logged into by SSH.

There are also commercial offerings which can log all traffic (by being persistently connected) and which is guaranteed to always be up.

User talk:PeterMortensen/IRC shenanigans

2022-12-02T19:25:56Z

PeterMortensen: /* ChatZilla */ Signed...

== This is not to stay...==

Note: This is a draft, meant as a proposal for the main wiki. It will be removed in due time.

--[[User:PeterMortensen|PeterMortensen]] ([[User talk:PeterMortensen|talk]]) 19:53, 2 December 2022 (CET)

== ChatZilla ==

Note: The information about ChatZilla may be out of date (for instance, it may no longer be possible to download the installer from a trusted source). I used it successfully for logging on Windows until the end of 2019.

--[[User:PeterMortensen|PeterMortensen]] ([[User talk:PeterMortensen|talk]]) 20:25, 2 December 2022 (CET)

User talk:PeterMortensen/IRC shenanigans

2022-12-02T19:25:27Z

PeterMortensen: It may not be possible any longer.

User talk:PeterMortensen/IRC shenanigans

2022-12-02T19:22:16Z

PeterMortensen: /* ChatZilla */ new section

User:PeterMortensen/IRC shenanigans

2022-12-02T18:56:02Z

PeterMortensen: /* Using IRC with the sigrok project */ Add some missing content.

== Using IRC with the sigrok project ==

The easiest is using [https://web.libera.chat/#sigrok the web interface], but it also times out after a relatively short time, about one hour.

The expected response time can be up to 24 hours if posting at certain times of the day. Thus be sure somebody is actually active at the time you post. About 1900 hours UTC is usually a good time.

A better solution is to download and configure an IRC client, for instance [https://en.wikipedia.org/wiki/Irssi Irssi] (on Unix-like systems) and [https://en.wikipedia.org/wiki/ChatZilla ChatZilla] on Windows (though it is on its way out due to the move by Firefox/Mozilla to "[https://en.wikipedia.org/wiki/Firefox#Firefox_Quantum Quantum]") in 2017. This can also, if configured for it, log all traffic so you don't miss out on anything. For instance, a [https://en.wikipedia.org/wiki/Raspberry_Pi Raspberry Pi], even a first generation with low power consumption, can be set up with Irssi to log all traffic. It can also be logged into by SSH.

There are also commercial offerings that can log all traffic and that is guaranteed to be always up.

User talk:PeterMortensen/IRC shenanigans

2022-12-02T18:53:45Z

PeterMortensen: Meta information about the page goes here on the talk page.

User:PeterMortensen/IRC shenanigans

2022-12-02T18:51:49Z

PeterMortensen: Some initial content. It is way too verbose, but it is a start.

== Using IRC with the sigrok project ==

The easiest is using [https://web.libera.chat/#sigrok the web interface], but it also times out after a relatively short time, about one hour.

The expected response time can be up to 24 hours if posting at certain times of the day. Thus be sure somebody is actually active at the time you post. About 1900 hours UTC is usually a good time.

A better solution is to download and configure an IRC client, for instance [https://en.wikipedia.org/wiki/Irssi Irssi] (on Unix-like systems) and [https://en.wikipedia.org/wiki/ChatZilla ChatZilla] on Windows (though it is on its way out due to the move by Firefox/ to "[https://en.wikipedia.org/wiki/Firefox#Firefox_Quantum Quantum]"). This can also, if configured for it, log all traffic so you don't miss out on anything. For instance, a [https://en.wikipedia.org/wiki/Raspberry_Pi Raspberry Pi], even a first generation with low power consumption, can be set up with Irssi to log all traffic. It can also be logged into by SSH.

There are also commercial offerings that can log all traffic and that is guaranteed to be always up.

User:PeterMortensen

2022-12-02T18:33:02Z

PeterMortensen: /* Creating sub pages for proposals */ Added some meat.

==Recent activity==

===2020-01===

Getting insight into what happens with PC keyboards on the signal level and on higher levels (related to repurposing an old PS/2 keyboard (BTC 5349) as a macro keyboard, with the help of an [https://store.arduino.cc/arduino-leonardo-with-headers Arduino Leonardo]):

#For the keyboards listed below: Verify that all keys work (by capturing in PulseView and observe there is actually a signal. Note that the accent and umlaut key requires pressing a letter after).
#For the keyboards listed below: Capturing and submitting information for PS/2 PC keyboards (CLK and DATA), including during pressing and releasing and bidirectional traffic (PC initialising the keyboard, e.g. at connect and/or PC startup). Submit to Git repository "[https://sigrok.org/gitweb/ sigrok-dumps]": Keyboards (all European layout):
##BTC 5349 (102 keys IBM/AT type, corresponding to IBM Model M (Enhanced)). 100 mA (measured). Mechanical keyboard?
##Fujitsu/Siemens ([https://en.wikipedia.org/wiki/File:ISO_keyboard_%28105%29_QWERTY_UK.svg 105 keys] + 10 media keys (sleep, mail, play, stop, speaker controls, etc.). IBM/AT type. ?? mA.
##Microsoft ''"Natural Keyboard Elite"''. [https://en.wikipedia.org/wiki/File:ISO_keyboard_%28105%29_QWERTY_UK.svg 105 keys]. 500 mA (nominal).
##[https://en.wikipedia.org/wiki/Apple_Extended_Keyboard Apple Extended Keyboard II]. [https://en.wikipedia.org/wiki/File:ISO_keyboard_%28105%29_QWERTY_UK.svg 105 keys] + one power key. ??? mA. Mechanical keyboard. Uses [https://en.wikipedia.org/wiki/Apple_Desktop_Bus#Physical ADB], not PS/2 (physically similar, but 4-pin mini-DIN connector). A single pin for data and 'PSW' connected directly to the power switch. All communication is host initiated (polling).
#Consider adding regression tests for the PS/2 decoder. It will include if it handles the 2-3% clock frequency offset for the BTC 5349 (probably, as there is CLK, but that is not the case if decoding as the UART protocol decoder).
#Some higher-level protocol decoder work for PC keyboards (not decided on yet), e.g. identifying scan code sequences as the corresponding keys.
#Some hardware to allow an Arduino Leonardo to pose as a PC ([https://en.wikipedia.org/wiki/Open_collector open collector] outputs). To explore what commands various keyboards responds to and what modes they might enter (for example, Linux allegedly tries put keyboards into "Set 3" (the powerup default is usually "Set 2")). The three LEDs on the keyboard can also be used for user feedback for the macro keyboard.
#Existing content on the wiki, etc. regarding PC keyboards, etc.:
##Keyboards (none found, but are probably not supposed to exist, only actual capturing hardware(?)).
##[[Protocol_decoder:Ps2|PS/2 decoder page]]. Does not exist??
##''"The decode of some PS/2 (or USB) keyboard/mouse traffic could yield an ASCII text file of all the keys that were pressed on the keyboard."'' (on [[Protocol decoder output|a planning page]])
##Look in bug tracker for PS/2, keyboards, etc.
###Bug #1460 - [https://sigrok.org/gitweb/?p=libsigrokdecode.git;a=commitdiff;h=4370348c4fcdbd708715c35a38fdf06c9364d518 ps2: end data byte at rising clock edge of the stop bit]
##Look in Git log
### [https://sigrok.org/gitweb/?p=sigrok-dumps.git;a=commit;h=16931eb480ba5df923c1508f3d83719eddcc5ab3 PS/2 keyboard data submitted on 2019-12-21] (discovered on [https://sigrok.org/gitweb/?p=sigrok-dumps.git;a=log projects / sigrok-dumps.git / commit ])
##Look in IRC log
##Look in blog posts for info on PS/2, etc.
#Updating the wiki
##Add PS/2 low-level reference (details about the CLK signal) to the PS/2 protocol decoder page. IRC ref. [2020-01-07 01:49:07] and [2020-01-07 18:09:02] (UTC+1)). Add to the resources section. Is: http://www.nerdkits.com/videos/interrupts_and_ps2_keyboard/
##Add keyboard documentation, pictures (not decided on yet).
#Ideas:
##Deliberately send data to the keyboard with a parity error.
##Deliberately add noise to the signals (say, wide-band white noise by electronics means), forcing parity errors. This should force the receiver (keyboard or host PC) to respond.
##Send unknown commands to the keyboard. It should respond with 0xFE (in contrast to the normal 0xFA).
##Try all the keyboard commands in ''[https://www.win.tue.nl/~aeb/linux/kbd/scancodes-12.html Keyboard commands]''.
##For a keyboard that is ''both'' capable of USB and PS/2: Record the startup sequence when connected via PS/2 to a PC host. To see if there is any indication on the signal level of such capability.

Other:

#Updating broken links here. For example, for the CAN protocol decoder.

===2019-04===

#Building a Docker container for compiling sigrok-cli and PulseView. It is supposed to both run under Linux and Windows (x64).
#Testing a new driver by user ''droghio'' that should work for the [[Tektronix TDS2024B|TDS2024C Tektronix oscilloscope]]. Some placeholding:
#*Part of "lsusb -v" output: "Bus 008 Device 005: ID 0699:03a6 Tektronix, Inc."
#*Notes to self: the ''"[git://sigrok.org/sigrok-util util]"'' repository (for building and stuff) - [https://github.com/sigrokproject/sigrok-util read-only mirror at GitHub]. [https://github.com/sigrokproject/sigrok-util/blob/master/cross-compile/linux/sigrok-cross-linux Cross-built script].

===2018-04===

Submitting comprehensive sample data for CAN bus, both 11-bit and 29-bit messages, and corresponding test cases (mostly for regression test - especially regression for [https://sigrok.org/bugzilla/show_bug.cgi?id=1085 the 2018-04-12 fix to the decoding at the end of the CRC part]).

Notes to self:

# Original acquired analog data: C:\temp2\2017-12-23\CAN decoder, new stuff bit handling at the end of the CRC segment\Data67\In\ACQ000009_Tektronix.txt

===2017-12===

Recording 22483 traces for the purpose of evaluating [https://sigrok.org/bugzilla/show_bug.cgi?id=1085 a proposed fix to the CAN protocol decoder] (actually only changing a single number from 16 to 17), stuff bit at the very end of the CRC segment, with a modified trigger scheme:

* Change the position of the trigger point to the end (right) so there is always a CAN message in the trace (for the previous), but still 26 µs recessive.

The time division was 100 µs / division (about 225 bit times max) to always record whole CAN messages - at 10 samples per bit time.

===2017-07===

Using the sigrok command-line ("sigrok-cli") to bulk process data derived from Tektronix oscilloscope data of 250 kbit/s CAN traffic on a real-world system (mobile cranes). The first sample data set is 5335 oscilloscope traces obtained with the trigger set to a negative pulse on CAN-H (to start off at the end of a CAN message) - corresponding to 6.5 recessive bits, 26 µsec (detecting the space in-between CAN messages). Sometimes there is a CAN message right after this, sometimes it is a bit delayed, and sometimes it is completely empty.

A sample command line (on Windows) is:

<pre>sigrok-cli -P can:bitrate=250000:can_rx="CAN RX" -P timing:data="CAN RX" -I csv:header=true:samplerate=5000000 -i "T:\stdHMF\UserData\scripts\Tektronix2PulseView\_PulseView_AllChannels_ACQ000001_Tektronix_f5000000.txt"</pre>

===2017-04===

Using [[PulseView]] to decode data from a Tektronix oscilloscope of SPI communication to a CAN controller, [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010406 MCP2515].

==Task list==

Currently not in priority order.

* Allow import of analog data through CSV files. (Related: fixed [https://sigrok.org/bugzilla/show_bug.cgi?id=1064 bug 1064] - ''locale'' issue, decimal point, "," vs. ".".).

* Add detection of error frames to the CAN protocol decoder

* Add support for the gigga watt EEVBlog multimeter (Bluetooth, etc.)

* Add a snap feature to the "cursor" (blue) in PulveView

* Change number of significant digits for the time display in the "cursor" (blue) in PulveView

* Submit selected sample traces for CAN decoder change (for CRC segment) validation. With and without stuff bits in various places. With and without timing deviations. (Related: [https://sigrok.org/bugzilla/show_bug.cgi?id=1085 bug 1085], celeron55's fix, '''''if len(self.bits) > self.last_databit + 16''''' → '''''if len(self.bits) > self.last_databit + 17''''' (16 → 17)).

* Add support for the [[Tektronix TDS2000B series|TDS2000]] series in libsigrok, and thus, by extension, use by the new shiny stuff in PulveView.

===On wiki===

* Change recommended procedure for submitting sample Sigrok files (traces), on ''[[Example dumps#Contributing dumps|Example dumps]]''.

==Glossary==

*''BBB'' [https://en.wikipedia.org/wiki/BeagleBoard#BeagleBone_Black BeagleBone Black]
*''GH'' [http://en.wikipedia.org/wiki/GitHub GitHub]
*''ISTR'' ????
*''LA'' Logic analyser
*''ML'' Mailing list
*''OLS'' ????
*''PR'' Pull request (a Git term). ''Not'' "problem report".
*''SR'' Sigrok
*''srd'' ????
*''WIP'' Work in progress. Mostly related to particular Git commits.
*''PD'' protocol decoder. Non-standard spellings are ''Pd'' and ''pd''.
*''PV'' PulseView. Non-standard spellings are ''Pv'' and ''pv''.

==Some bug reports==

* [https://sigrok.org/bug/1155 Possible problem with the MSO-19 USB driver on Windows]. PulveView crashes at startup if the MSO-19 is connected.

==Interests==

I am mostly interested in:

* The [[CAN|CAN protocol decoder]] (that page is currently empty, but it is listed on [[Protocol decoders|the protocol decoders page]])
* CAN bus loggers, like IXXAT's (now acquired by HMS) ''USB-to-CAN compact''/''USB-to-CAN V2'' and Kvaser's ''Memorator''.
* The higher-level [http://en.wikipedia.org/wiki/CANopen CANopen] protocol (on top of CAN)

==Protocol decoders==

===Non-empty wiki pages===

Currently (2017-07-08), 28
of 77 [[Protocol_decoders#Supported protocol decoders|protocol decoders]] (36%) have non-empty pages here on the wiki:

*[[Protocol decoder:Adns5020|ADNS5020]]
*[[Protocol decoder:Am230x|AM230X]]
*[[Protocol decoder:Arm etmv3|ARM ETMV3]]
*[[Protocol decoder:Arm itm|ARM ITM]]
*[[Protocol decoder:Arm tpiu|ARM TPIU]]
*[[Protocol decoder:Aud|AUD]]
*[[Protocol decoder:Avr pdi|AVR PDI]]
*[[Protocol decoder:Dcf77|DCF77]]
*[[Protocol decoder:I2c|I²C]]
*[[Protocol decoder:Ir nec|IR NEC]]
*[[Protocol decoder:Modbus|Modbus]]
*[[Protocol decoder:Mrf24j40|MRF24J40]]
*[[Protocol decoder:Nrf24l01|NRF24L01]]
*[[Protocol decoder:Nunchuk|Nunchuk]]
*[[Protocol decoder:Pan1321|PAN1321]]
*[[Protocol decoder:Parallel|Parallel]]
*[[Protocol decoder:Pwm|PWM]]
*[[Protocol decoder:Qi|Qi]]
*[[Protocol decoder:Rfm12|RFM12]]
*[[Protocol decoder:Rgb led spi|RGB LED SPI]]
*[[Protocol decoder:Rtc8564|RTC8564]]
*[[Protocol decoder:Spdif|SPDIF]]
*[[Protocol decoder:Spi|SPI]]
*[[Protocol decoder:Spiflash|SPI flash]]
*[[Protocol decoder:Stepper motor|Stepper motor]]
*[[Protocol decoder:Tlc5620|TLC5620]]
*[[Protocol decoder:Uart|UART]]
*[[Protocol decoder:Z80|Z80]]

==Meta==

===Creating sub pages for proposals===

E.g., to work on drafts and proposals for new or old wiki entries, without affecting the main wiki (this is not specific for this project). Add this non-existent link ("IRC shenanigans" is an example) somewhere on the user page (it can be deleted later if the reference is not needed):

<syntaxhighlight lang="none">
[[User:PeterMortensen/IRC shenanigans]]
</syntaxhighlight>

Rendered:

[[User:PeterMortensen/IRC shenanigans]]

Open that page and add some content.

==Profile==

Profile: see [http://en.wikipedia.org/wiki/User:Mortense my Wikipedia user page].

Credentials: more than 5000 edits on the English Wikipedia.

==Shortcuts==

* [https://sigrok.org/doc/pulseview/0.4.1/manual.html PulseView manual]
* [[Sigrok-cli|sigrok-cli man page]]
* [https://plus.google.com/communities/109843678338531936878 Google+ group for sigrok] (now defunc as Google+ closed down)
* [[PulseView]]. Includes the command line to get the source code using Git.
* [[Downloads#Windows_Download|PulseView, Windows binaries]] (nightly - development). [[Windows#Windows_installers|Alternative location]] (but it seems redundant).
* [[Downloads#Linux_AppImage_binaries|PulseView, Linux binaries]] (nightly - development).
* [[Example dumps|Example data dumps]] - sample data in .sr format. Also includes instructions on how to contribute new ones. Includes the command line to get the whole thing using Git (as of 2017-11-26, 2286 "objects", 724 .sr files, about 65 MB in download size, 192 MB on disk).
* [[Special:Random|Random page]]
* [https://sigrok.org/jenkins/job/sigrok-native-appimage/ Native app image] (not official yet). Is for Linux and x86 only. See also [https://en.wikipedia.org/wiki/AppImage AppImage] (Wikipedia).
* [[Press]]. List of annotated links, mostly blog posts.
* [[Probe comparison]]
* [[Link Instruments MSO-19|MSO-19]]. Mixed oscilloscope and logic analyser by Link Instruments that (or rather its driver) crashes PulveView at startup when connected (until some time in mid 2018(?)). Some reverse engineering has been done in 2012, but it is not supported (has status "Planned"). [https://sigrok.org/bugzilla/show_bug.cgi?id=1155 Sigrok bug report for the crash]. [http://www.linkinstruments.com/doupdate_mso19.htm Software download page for it.]
* [[Windows|sigrok, Microsoft Windows page]]
** [[Windows#Device specific USB driver|Device specific USB driver - WinUSB - Zadig]]

===Protocol decoders===

* The [[CAN|CAN bus protocol decoder]]
* [[Protocol decoder HOWTO]]
* [[Protocol decoder API]]
* [[Protocol decoders#Supported protocol decoders|Supported protocol decoders]]

===Building sigrok===

* On Debian (e.g. Raspberry Pi): [[Linux#Installing the requirements 2|Installing required software]]
* On Debian (e.g. Raspberry Pi): [[Linux#Building 3|Actual build]]
* Alternative to following the wiki pages: [https://sigrok.org/gitweb/?p=sigrok-util.git;a=blob;f=cross-compile/linux/sigrok-cross-linux;h=2c8e559efde8cf6ae9a365bf1a4324a33600fae7;hb=HEAD a script that will do most of it]. (''[sigrok-util.git] / cross-compile / linux / sigrok-cross-linux'')
* Windows:
**On Windows: [[Windows#Native_build_using_MSYS2|Native build using MSYS2]] (but may not really work - sigrok-cli and PulseView are listed as not working).
**[[Windows#Cross-compile_using_MXE|Cross compile on Linux]] (using [http://mxe.cc/ MXE]). The script is [https://sigrok.org/gitweb/?p=sigrok-util.git;a=blob;f=cross-compile/mingw/sigrok-cross-mingw;h=8330406ecd28969d8d29c8ad23df8968a4b9ec68;hb=HEAD /sigrok-util/cross-compile/mingw/sigrok-cross-mingw]. Used for nightlies? [https://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=debug,platform=cross-i686-w64-mingw32/ Jenkins page for the debug version].
* The Jenkins thingy - automatic build, e.g. nightlies for PulseView and "AppImage" (self-contained executable for x86 Linux). Sample: [https://sigrok.org/jenkins/job/sigrok-cli/ sigrok-cli] with 44 configurations (43 cross-compiles), e.g. cross-x86_64-w64-mingw32 (for Windows 64-bit?).
* The [[Building#Installing_to_a_non-standard_directory_using_LD_LIBRARY_PATH|LD_LIBRARY_PATH trick]]

User:PeterMortensen

2022-12-02T17:58:41Z

PeterMortensen: /* Meta */ Created a stub for a subsection of a subsection

==Recent activity==

===2020-01===

Getting insight into what happens with PC keyboards on the signal level and on higher levels (related to repurposing an old PS/2 keyboard (BTC 5349) as a macro keyboard, with the help of an [https://store.arduino.cc/arduino-leonardo-with-headers Arduino Leonardo]):

#For the keyboards listed below: Verify that all keys work (by capturing in PulseView and observe there is actually a signal. Note that the accent and umlaut key requires pressing a letter after).
#For the keyboards listed below: Capturing and submitting information for PS/2 PC keyboards (CLK and DATA), including during pressing and releasing and bidirectional traffic (PC initialising the keyboard, e.g. at connect and/or PC startup). Submit to Git repository "[https://sigrok.org/gitweb/ sigrok-dumps]": Keyboards (all European layout):
##BTC 5349 (102 keys IBM/AT type, corresponding to IBM Model M (Enhanced)). 100 mA (measured). Mechanical keyboard?
##Fujitsu/Siemens ([https://en.wikipedia.org/wiki/File:ISO_keyboard_%28105%29_QWERTY_UK.svg 105 keys] + 10 media keys (sleep, mail, play, stop, speaker controls, etc.). IBM/AT type. ?? mA.
##Microsoft ''"Natural Keyboard Elite"''. [https://en.wikipedia.org/wiki/File:ISO_keyboard_%28105%29_QWERTY_UK.svg 105 keys]. 500 mA (nominal).
##[https://en.wikipedia.org/wiki/Apple_Extended_Keyboard Apple Extended Keyboard II]. [https://en.wikipedia.org/wiki/File:ISO_keyboard_%28105%29_QWERTY_UK.svg 105 keys] + one power key. ??? mA. Mechanical keyboard. Uses [https://en.wikipedia.org/wiki/Apple_Desktop_Bus#Physical ADB], not PS/2 (physically similar, but 4-pin mini-DIN connector). A single pin for data and 'PSW' connected directly to the power switch. All communication is host initiated (polling).
#Consider adding regression tests for the PS/2 decoder. It will include if it handles the 2-3% clock frequency offset for the BTC 5349 (probably, as there is CLK, but that is not the case if decoding as the UART protocol decoder).
#Some higher-level protocol decoder work for PC keyboards (not decided on yet), e.g. identifying scan code sequences as the corresponding keys.
#Some hardware to allow an Arduino Leonardo to pose as a PC ([https://en.wikipedia.org/wiki/Open_collector open collector] outputs). To explore what commands various keyboards responds to and what modes they might enter (for example, Linux allegedly tries put keyboards into "Set 3" (the powerup default is usually "Set 2")). The three LEDs on the keyboard can also be used for user feedback for the macro keyboard.
#Existing content on the wiki, etc. regarding PC keyboards, etc.:
##Keyboards (none found, but are probably not supposed to exist, only actual capturing hardware(?)).
##[[Protocol_decoder:Ps2|PS/2 decoder page]]. Does not exist??
##''"The decode of some PS/2 (or USB) keyboard/mouse traffic could yield an ASCII text file of all the keys that were pressed on the keyboard."'' (on [[Protocol decoder output|a planning page]])
##Look in bug tracker for PS/2, keyboards, etc.
###Bug #1460 - [https://sigrok.org/gitweb/?p=libsigrokdecode.git;a=commitdiff;h=4370348c4fcdbd708715c35a38fdf06c9364d518 ps2: end data byte at rising clock edge of the stop bit]
##Look in Git log
### [https://sigrok.org/gitweb/?p=sigrok-dumps.git;a=commit;h=16931eb480ba5df923c1508f3d83719eddcc5ab3 PS/2 keyboard data submitted on 2019-12-21] (discovered on [https://sigrok.org/gitweb/?p=sigrok-dumps.git;a=log projects / sigrok-dumps.git / commit ])
##Look in IRC log
##Look in blog posts for info on PS/2, etc.
#Updating the wiki
##Add PS/2 low-level reference (details about the CLK signal) to the PS/2 protocol decoder page. IRC ref. [2020-01-07 01:49:07] and [2020-01-07 18:09:02] (UTC+1)). Add to the resources section. Is: http://www.nerdkits.com/videos/interrupts_and_ps2_keyboard/
##Add keyboard documentation, pictures (not decided on yet).
#Ideas:
##Deliberately send data to the keyboard with a parity error.
##Deliberately add noise to the signals (say, wide-band white noise by electronics means), forcing parity errors. This should force the receiver (keyboard or host PC) to respond.
##Send unknown commands to the keyboard. It should respond with 0xFE (in contrast to the normal 0xFA).
##Try all the keyboard commands in ''[https://www.win.tue.nl/~aeb/linux/kbd/scancodes-12.html Keyboard commands]''.
##For a keyboard that is ''both'' capable of USB and PS/2: Record the startup sequence when connected via PS/2 to a PC host. To see if there is any indication on the signal level of such capability.

Other:

#Updating broken links here. For example, for the CAN protocol decoder.

===2019-04===

#Building a Docker container for compiling sigrok-cli and PulseView. It is supposed to both run under Linux and Windows (x64).
#Testing a new driver by user ''droghio'' that should work for the [[Tektronix TDS2024B|TDS2024C Tektronix oscilloscope]]. Some placeholding:
#*Part of "lsusb -v" output: "Bus 008 Device 005: ID 0699:03a6 Tektronix, Inc."
#*Notes to self: the ''"[git://sigrok.org/sigrok-util util]"'' repository (for building and stuff) - [https://github.com/sigrokproject/sigrok-util read-only mirror at GitHub]. [https://github.com/sigrokproject/sigrok-util/blob/master/cross-compile/linux/sigrok-cross-linux Cross-built script].

===2018-04===

Submitting comprehensive sample data for CAN bus, both 11-bit and 29-bit messages, and corresponding test cases (mostly for regression test - especially regression for [https://sigrok.org/bugzilla/show_bug.cgi?id=1085 the 2018-04-12 fix to the decoding at the end of the CRC part]).

Notes to self:

# Original acquired analog data: C:\temp2\2017-12-23\CAN decoder, new stuff bit handling at the end of the CRC segment\Data67\In\ACQ000009_Tektronix.txt

===2017-12===

Recording 22483 traces for the purpose of evaluating [https://sigrok.org/bugzilla/show_bug.cgi?id=1085 a proposed fix to the CAN protocol decoder] (actually only changing a single number from 16 to 17), stuff bit at the very end of the CRC segment, with a modified trigger scheme:

* Change the position of the trigger point to the end (right) so there is always a CAN message in the trace (for the previous), but still 26 µs recessive.

The time division was 100 µs / division (about 225 bit times max) to always record whole CAN messages - at 10 samples per bit time.

===2017-07===

Using the sigrok command-line ("sigrok-cli") to bulk process data derived from Tektronix oscilloscope data of 250 kbit/s CAN traffic on a real-world system (mobile cranes). The first sample data set is 5335 oscilloscope traces obtained with the trigger set to a negative pulse on CAN-H (to start off at the end of a CAN message) - corresponding to 6.5 recessive bits, 26 µsec (detecting the space in-between CAN messages). Sometimes there is a CAN message right after this, sometimes it is a bit delayed, and sometimes it is completely empty.

A sample command line (on Windows) is:

<pre>sigrok-cli -P can:bitrate=250000:can_rx="CAN RX" -P timing:data="CAN RX" -I csv:header=true:samplerate=5000000 -i "T:\stdHMF\UserData\scripts\Tektronix2PulseView\_PulseView_AllChannels_ACQ000001_Tektronix_f5000000.txt"</pre>

===2017-04===

Using [[PulseView]] to decode data from a Tektronix oscilloscope of SPI communication to a CAN controller, [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010406 MCP2515].

==Task list==

Currently not in priority order.

* Allow import of analog data through CSV files. (Related: fixed [https://sigrok.org/bugzilla/show_bug.cgi?id=1064 bug 1064] - ''locale'' issue, decimal point, "," vs. ".".).

* Add detection of error frames to the CAN protocol decoder

* Add support for the gigga watt EEVBlog multimeter (Bluetooth, etc.)

* Add a snap feature to the "cursor" (blue) in PulveView

* Change number of significant digits for the time display in the "cursor" (blue) in PulveView

* Submit selected sample traces for CAN decoder change (for CRC segment) validation. With and without stuff bits in various places. With and without timing deviations. (Related: [https://sigrok.org/bugzilla/show_bug.cgi?id=1085 bug 1085], celeron55's fix, '''''if len(self.bits) > self.last_databit + 16''''' → '''''if len(self.bits) > self.last_databit + 17''''' (16 → 17)).

* Add support for the [[Tektronix TDS2000B series|TDS2000]] series in libsigrok, and thus, by extension, use by the new shiny stuff in PulveView.

===On wiki===

* Change recommended procedure for submitting sample Sigrok files (traces), on ''[[Example dumps#Contributing dumps|Example dumps]]''.

==Glossary==

*''BBB'' [https://en.wikipedia.org/wiki/BeagleBoard#BeagleBone_Black BeagleBone Black]
*''GH'' [http://en.wikipedia.org/wiki/GitHub GitHub]
*''ISTR'' ????
*''LA'' Logic analyser
*''ML'' Mailing list
*''OLS'' ????
*''PR'' Pull request (a Git term). ''Not'' "problem report".
*''SR'' Sigrok
*''srd'' ????
*''WIP'' Work in progress. Mostly related to particular Git commits.
*''PD'' protocol decoder. Non-standard spellings are ''Pd'' and ''pd''.
*''PV'' PulseView. Non-standard spellings are ''Pv'' and ''pv''.

==Some bug reports==

* [https://sigrok.org/bug/1155 Possible problem with the MSO-19 USB driver on Windows]. PulveView crashes at startup if the MSO-19 is connected.

==Interests==

I am mostly interested in:

* The [[CAN|CAN protocol decoder]] (that page is currently empty, but it is listed on [[Protocol decoders|the protocol decoders page]])
* CAN bus loggers, like IXXAT's (now acquired by HMS) ''USB-to-CAN compact''/''USB-to-CAN V2'' and Kvaser's ''Memorator''.
* The higher-level [http://en.wikipedia.org/wiki/CANopen CANopen] protocol (on top of CAN)

==Protocol decoders==

===Non-empty wiki pages===

Currently (2017-07-08), 28
of 77 [[Protocol_decoders#Supported protocol decoders|protocol decoders]] (36%) have non-empty pages here on the wiki:

*[[Protocol decoder:Adns5020|ADNS5020]]
*[[Protocol decoder:Am230x|AM230X]]
*[[Protocol decoder:Arm etmv3|ARM ETMV3]]
*[[Protocol decoder:Arm itm|ARM ITM]]
*[[Protocol decoder:Arm tpiu|ARM TPIU]]
*[[Protocol decoder:Aud|AUD]]
*[[Protocol decoder:Avr pdi|AVR PDI]]
*[[Protocol decoder:Dcf77|DCF77]]
*[[Protocol decoder:I2c|I²C]]
*[[Protocol decoder:Ir nec|IR NEC]]
*[[Protocol decoder:Modbus|Modbus]]
*[[Protocol decoder:Mrf24j40|MRF24J40]]
*[[Protocol decoder:Nrf24l01|NRF24L01]]
*[[Protocol decoder:Nunchuk|Nunchuk]]
*[[Protocol decoder:Pan1321|PAN1321]]
*[[Protocol decoder:Parallel|Parallel]]
*[[Protocol decoder:Pwm|PWM]]
*[[Protocol decoder:Qi|Qi]]
*[[Protocol decoder:Rfm12|RFM12]]
*[[Protocol decoder:Rgb led spi|RGB LED SPI]]
*[[Protocol decoder:Rtc8564|RTC8564]]
*[[Protocol decoder:Spdif|SPDIF]]
*[[Protocol decoder:Spi|SPI]]
*[[Protocol decoder:Spiflash|SPI flash]]
*[[Protocol decoder:Stepper motor|Stepper motor]]
*[[Protocol decoder:Tlc5620|TLC5620]]
*[[Protocol decoder:Uart|UART]]
*[[Protocol decoder:Z80|Z80]]

==Meta==

===Creating sub pages for proposals===

==Profile==

Profile: see [http://en.wikipedia.org/wiki/User:Mortense my Wikipedia user page].

Credentials: more than 5000 edits on the English Wikipedia.

==Shortcuts==

* [https://sigrok.org/doc/pulseview/0.4.1/manual.html PulseView manual]
* [[Sigrok-cli|sigrok-cli man page]]
* [https://plus.google.com/communities/109843678338531936878 Google+ group for sigrok] (now defunc as Google+ closed down)
* [[PulseView]]. Includes the command line to get the source code using Git.
* [[Downloads#Windows_Download|PulseView, Windows binaries]] (nightly - development). [[Windows#Windows_installers|Alternative location]] (but it seems redundant).
* [[Downloads#Linux_AppImage_binaries|PulseView, Linux binaries]] (nightly - development).
* [[Example dumps|Example data dumps]] - sample data in .sr format. Also includes instructions on how to contribute new ones. Includes the command line to get the whole thing using Git (as of 2017-11-26, 2286 "objects", 724 .sr files, about 65 MB in download size, 192 MB on disk).
* [[Special:Random|Random page]]
* [https://sigrok.org/jenkins/job/sigrok-native-appimage/ Native app image] (not official yet). Is for Linux and x86 only. See also [https://en.wikipedia.org/wiki/AppImage AppImage] (Wikipedia).
* [[Press]]. List of annotated links, mostly blog posts.
* [[Probe comparison]]
* [[Link Instruments MSO-19|MSO-19]]. Mixed oscilloscope and logic analyser by Link Instruments that (or rather its driver) crashes PulveView at startup when connected (until some time in mid 2018(?)). Some reverse engineering has been done in 2012, but it is not supported (has status "Planned"). [https://sigrok.org/bugzilla/show_bug.cgi?id=1155 Sigrok bug report for the crash]. [http://www.linkinstruments.com/doupdate_mso19.htm Software download page for it.]
* [[Windows|sigrok, Microsoft Windows page]]
** [[Windows#Device specific USB driver|Device specific USB driver - WinUSB - Zadig]]

===Protocol decoders===

* The [[CAN|CAN bus protocol decoder]]
* [[Protocol decoder HOWTO]]
* [[Protocol decoder API]]
* [[Protocol decoders#Supported protocol decoders|Supported protocol decoders]]

===Building sigrok===

* On Debian (e.g. Raspberry Pi): [[Linux#Installing the requirements 2|Installing required software]]
* On Debian (e.g. Raspberry Pi): [[Linux#Building 3|Actual build]]
* Alternative to following the wiki pages: [https://sigrok.org/gitweb/?p=sigrok-util.git;a=blob;f=cross-compile/linux/sigrok-cross-linux;h=2c8e559efde8cf6ae9a365bf1a4324a33600fae7;hb=HEAD a script that will do most of it]. (''[sigrok-util.git] / cross-compile / linux / sigrok-cross-linux'')
* Windows:
**On Windows: [[Windows#Native_build_using_MSYS2|Native build using MSYS2]] (but may not really work - sigrok-cli and PulseView are listed as not working).
**[[Windows#Cross-compile_using_MXE|Cross compile on Linux]] (using [http://mxe.cc/ MXE]). The script is [https://sigrok.org/gitweb/?p=sigrok-util.git;a=blob;f=cross-compile/mingw/sigrok-cross-mingw;h=8330406ecd28969d8d29c8ad23df8968a4b9ec68;hb=HEAD /sigrok-util/cross-compile/mingw/sigrok-cross-mingw]. Used for nightlies? [https://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=debug,platform=cross-i686-w64-mingw32/ Jenkins page for the debug version].
* The Jenkins thingy - automatic build, e.g. nightlies for PulseView and "AppImage" (self-contained executable for x86 Linux). Sample: [https://sigrok.org/jenkins/job/sigrok-cli/ sigrok-cli] with 44 configurations (43 cross-compiles), e.g. cross-x86_64-w64-mingw32 (for Windows 64-bit?).
* The [[Building#Installing_to_a_non-standard_directory_using_LD_LIBRARY_PATH|LD_LIBRARY_PATH trick]]

User:PeterMortensen

2022-12-02T17:57:10Z

PeterMortensen: Added a stub for a new sub section.

==Recent activity==

===2020-01===

Getting insight into what happens with PC keyboards on the signal level and on higher levels (related to repurposing an old PS/2 keyboard (BTC 5349) as a macro keyboard, with the help of an [https://store.arduino.cc/arduino-leonardo-with-headers Arduino Leonardo]):

#For the keyboards listed below: Verify that all keys work (by capturing in PulseView and observe there is actually a signal. Note that the accent and umlaut key requires pressing a letter after).
#For the keyboards listed below: Capturing and submitting information for PS/2 PC keyboards (CLK and DATA), including during pressing and releasing and bidirectional traffic (PC initialising the keyboard, e.g. at connect and/or PC startup). Submit to Git repository "[https://sigrok.org/gitweb/ sigrok-dumps]": Keyboards (all European layout):
##BTC 5349 (102 keys IBM/AT type, corresponding to IBM Model M (Enhanced)). 100 mA (measured). Mechanical keyboard?
##Fujitsu/Siemens ([https://en.wikipedia.org/wiki/File:ISO_keyboard_%28105%29_QWERTY_UK.svg 105 keys] + 10 media keys (sleep, mail, play, stop, speaker controls, etc.). IBM/AT type. ?? mA.
##Microsoft ''"Natural Keyboard Elite"''. [https://en.wikipedia.org/wiki/File:ISO_keyboard_%28105%29_QWERTY_UK.svg 105 keys]. 500 mA (nominal).
##[https://en.wikipedia.org/wiki/Apple_Extended_Keyboard Apple Extended Keyboard II]. [https://en.wikipedia.org/wiki/File:ISO_keyboard_%28105%29_QWERTY_UK.svg 105 keys] + one power key. ??? mA. Mechanical keyboard. Uses [https://en.wikipedia.org/wiki/Apple_Desktop_Bus#Physical ADB], not PS/2 (physically similar, but 4-pin mini-DIN connector). A single pin for data and 'PSW' connected directly to the power switch. All communication is host initiated (polling).
#Consider adding regression tests for the PS/2 decoder. It will include if it handles the 2-3% clock frequency offset for the BTC 5349 (probably, as there is CLK, but that is not the case if decoding as the UART protocol decoder).
#Some higher-level protocol decoder work for PC keyboards (not decided on yet), e.g. identifying scan code sequences as the corresponding keys.
#Some hardware to allow an Arduino Leonardo to pose as a PC ([https://en.wikipedia.org/wiki/Open_collector open collector] outputs). To explore what commands various keyboards responds to and what modes they might enter (for example, Linux allegedly tries put keyboards into "Set 3" (the powerup default is usually "Set 2")). The three LEDs on the keyboard can also be used for user feedback for the macro keyboard.
#Existing content on the wiki, etc. regarding PC keyboards, etc.:
##Keyboards (none found, but are probably not supposed to exist, only actual capturing hardware(?)).
##[[Protocol_decoder:Ps2|PS/2 decoder page]]. Does not exist??
##''"The decode of some PS/2 (or USB) keyboard/mouse traffic could yield an ASCII text file of all the keys that were pressed on the keyboard."'' (on [[Protocol decoder output|a planning page]])
##Look in bug tracker for PS/2, keyboards, etc.
###Bug #1460 - [https://sigrok.org/gitweb/?p=libsigrokdecode.git;a=commitdiff;h=4370348c4fcdbd708715c35a38fdf06c9364d518 ps2: end data byte at rising clock edge of the stop bit]
##Look in Git log
### [https://sigrok.org/gitweb/?p=sigrok-dumps.git;a=commit;h=16931eb480ba5df923c1508f3d83719eddcc5ab3 PS/2 keyboard data submitted on 2019-12-21] (discovered on [https://sigrok.org/gitweb/?p=sigrok-dumps.git;a=log projects / sigrok-dumps.git / commit ])
##Look in IRC log
##Look in blog posts for info on PS/2, etc.
#Updating the wiki
##Add PS/2 low-level reference (details about the CLK signal) to the PS/2 protocol decoder page. IRC ref. [2020-01-07 01:49:07] and [2020-01-07 18:09:02] (UTC+1)). Add to the resources section. Is: http://www.nerdkits.com/videos/interrupts_and_ps2_keyboard/
##Add keyboard documentation, pictures (not decided on yet).
#Ideas:
##Deliberately send data to the keyboard with a parity error.
##Deliberately add noise to the signals (say, wide-band white noise by electronics means), forcing parity errors. This should force the receiver (keyboard or host PC) to respond.
##Send unknown commands to the keyboard. It should respond with 0xFE (in contrast to the normal 0xFA).
##Try all the keyboard commands in ''[https://www.win.tue.nl/~aeb/linux/kbd/scancodes-12.html Keyboard commands]''.
##For a keyboard that is ''both'' capable of USB and PS/2: Record the startup sequence when connected via PS/2 to a PC host. To see if there is any indication on the signal level of such capability.

Other:

#Updating broken links here. For example, for the CAN protocol decoder.

===2019-04===

#Building a Docker container for compiling sigrok-cli and PulseView. It is supposed to both run under Linux and Windows (x64).
#Testing a new driver by user ''droghio'' that should work for the [[Tektronix TDS2024B|TDS2024C Tektronix oscilloscope]]. Some placeholding:
#*Part of "lsusb -v" output: "Bus 008 Device 005: ID 0699:03a6 Tektronix, Inc."
#*Notes to self: the ''"[git://sigrok.org/sigrok-util util]"'' repository (for building and stuff) - [https://github.com/sigrokproject/sigrok-util read-only mirror at GitHub]. [https://github.com/sigrokproject/sigrok-util/blob/master/cross-compile/linux/sigrok-cross-linux Cross-built script].

===2018-04===

Submitting comprehensive sample data for CAN bus, both 11-bit and 29-bit messages, and corresponding test cases (mostly for regression test - especially regression for [https://sigrok.org/bugzilla/show_bug.cgi?id=1085 the 2018-04-12 fix to the decoding at the end of the CRC part]).

Notes to self:

# Original acquired analog data: C:\temp2\2017-12-23\CAN decoder, new stuff bit handling at the end of the CRC segment\Data67\In\ACQ000009_Tektronix.txt

===2017-12===

Recording 22483 traces for the purpose of evaluating [https://sigrok.org/bugzilla/show_bug.cgi?id=1085 a proposed fix to the CAN protocol decoder] (actually only changing a single number from 16 to 17), stuff bit at the very end of the CRC segment, with a modified trigger scheme:

* Change the position of the trigger point to the end (right) so there is always a CAN message in the trace (for the previous), but still 26 µs recessive.

The time division was 100 µs / division (about 225 bit times max) to always record whole CAN messages - at 10 samples per bit time.

===2017-07===

Using the sigrok command-line ("sigrok-cli") to bulk process data derived from Tektronix oscilloscope data of 250 kbit/s CAN traffic on a real-world system (mobile cranes). The first sample data set is 5335 oscilloscope traces obtained with the trigger set to a negative pulse on CAN-H (to start off at the end of a CAN message) - corresponding to 6.5 recessive bits, 26 µsec (detecting the space in-between CAN messages). Sometimes there is a CAN message right after this, sometimes it is a bit delayed, and sometimes it is completely empty.

A sample command line (on Windows) is:

<pre>sigrok-cli -P can:bitrate=250000:can_rx="CAN RX" -P timing:data="CAN RX" -I csv:header=true:samplerate=5000000 -i "T:\stdHMF\UserData\scripts\Tektronix2PulseView\_PulseView_AllChannels_ACQ000001_Tektronix_f5000000.txt"</pre>

===2017-04===

Using [[PulseView]] to decode data from a Tektronix oscilloscope of SPI communication to a CAN controller, [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010406 MCP2515].

==Task list==

Currently not in priority order.

* Allow import of analog data through CSV files. (Related: fixed [https://sigrok.org/bugzilla/show_bug.cgi?id=1064 bug 1064] - ''locale'' issue, decimal point, "," vs. ".".).

* Add detection of error frames to the CAN protocol decoder

* Add support for the gigga watt EEVBlog multimeter (Bluetooth, etc.)

* Add a snap feature to the "cursor" (blue) in PulveView

* Change number of significant digits for the time display in the "cursor" (blue) in PulveView

* Submit selected sample traces for CAN decoder change (for CRC segment) validation. With and without stuff bits in various places. With and without timing deviations. (Related: [https://sigrok.org/bugzilla/show_bug.cgi?id=1085 bug 1085], celeron55's fix, '''''if len(self.bits) > self.last_databit + 16''''' → '''''if len(self.bits) > self.last_databit + 17''''' (16 → 17)).

* Add support for the [[Tektronix TDS2000B series|TDS2000]] series in libsigrok, and thus, by extension, use by the new shiny stuff in PulveView.

===On wiki===

* Change recommended procedure for submitting sample Sigrok files (traces), on ''[[Example dumps#Contributing dumps|Example dumps]]''.

==Glossary==

*''BBB'' [https://en.wikipedia.org/wiki/BeagleBoard#BeagleBone_Black BeagleBone Black]
*''GH'' [http://en.wikipedia.org/wiki/GitHub GitHub]
*''ISTR'' ????
*''LA'' Logic analyser
*''ML'' Mailing list
*''OLS'' ????
*''PR'' Pull request (a Git term). ''Not'' "problem report".
*''SR'' Sigrok
*''srd'' ????
*''WIP'' Work in progress. Mostly related to particular Git commits.
*''PD'' protocol decoder. Non-standard spellings are ''Pd'' and ''pd''.
*''PV'' PulseView. Non-standard spellings are ''Pv'' and ''pv''.

==Some bug reports==

* [https://sigrok.org/bug/1155 Possible problem with the MSO-19 USB driver on Windows]. PulveView crashes at startup if the MSO-19 is connected.

==Interests==

I am mostly interested in:

* The [[CAN|CAN protocol decoder]] (that page is currently empty, but it is listed on [[Protocol decoders|the protocol decoders page]])
* CAN bus loggers, like IXXAT's (now acquired by HMS) ''USB-to-CAN compact''/''USB-to-CAN V2'' and Kvaser's ''Memorator''.
* The higher-level [http://en.wikipedia.org/wiki/CANopen CANopen] protocol (on top of CAN)

==Protocol decoders==

===Non-empty wiki pages===

Currently (2017-07-08), 28
of 77 [[Protocol_decoders#Supported protocol decoders|protocol decoders]] (36%) have non-empty pages here on the wiki:

*[[Protocol decoder:Adns5020|ADNS5020]]
*[[Protocol decoder:Am230x|AM230X]]
*[[Protocol decoder:Arm etmv3|ARM ETMV3]]
*[[Protocol decoder:Arm itm|ARM ITM]]
*[[Protocol decoder:Arm tpiu|ARM TPIU]]
*[[Protocol decoder:Aud|AUD]]
*[[Protocol decoder:Avr pdi|AVR PDI]]
*[[Protocol decoder:Dcf77|DCF77]]
*[[Protocol decoder:I2c|I²C]]
*[[Protocol decoder:Ir nec|IR NEC]]
*[[Protocol decoder:Modbus|Modbus]]
*[[Protocol decoder:Mrf24j40|MRF24J40]]
*[[Protocol decoder:Nrf24l01|NRF24L01]]
*[[Protocol decoder:Nunchuk|Nunchuk]]
*[[Protocol decoder:Pan1321|PAN1321]]
*[[Protocol decoder:Parallel|Parallel]]
*[[Protocol decoder:Pwm|PWM]]
*[[Protocol decoder:Qi|Qi]]
*[[Protocol decoder:Rfm12|RFM12]]
*[[Protocol decoder:Rgb led spi|RGB LED SPI]]
*[[Protocol decoder:Rtc8564|RTC8564]]
*[[Protocol decoder:Spdif|SPDIF]]
*[[Protocol decoder:Spi|SPI]]
*[[Protocol decoder:Spiflash|SPI flash]]
*[[Protocol decoder:Stepper motor|Stepper motor]]
*[[Protocol decoder:Tlc5620|TLC5620]]
*[[Protocol decoder:Uart|UART]]
*[[Protocol decoder:Z80|Z80]]

==Meta==

==Profile==

Profile: see [http://en.wikipedia.org/wiki/User:Mortense my Wikipedia user page].

Credentials: more than 5000 edits on the English Wikipedia.

==Shortcuts==

* [https://sigrok.org/doc/pulseview/0.4.1/manual.html PulseView manual]
* [[Sigrok-cli|sigrok-cli man page]]
* [https://plus.google.com/communities/109843678338531936878 Google+ group for sigrok] (now defunc as Google+ closed down)
* [[PulseView]]. Includes the command line to get the source code using Git.
* [[Downloads#Windows_Download|PulseView, Windows binaries]] (nightly - development). [[Windows#Windows_installers|Alternative location]] (but it seems redundant).
* [[Downloads#Linux_AppImage_binaries|PulseView, Linux binaries]] (nightly - development).
* [[Example dumps|Example data dumps]] - sample data in .sr format. Also includes instructions on how to contribute new ones. Includes the command line to get the whole thing using Git (as of 2017-11-26, 2286 "objects", 724 .sr files, about 65 MB in download size, 192 MB on disk).
* [[Special:Random|Random page]]
* [https://sigrok.org/jenkins/job/sigrok-native-appimage/ Native app image] (not official yet). Is for Linux and x86 only. See also [https://en.wikipedia.org/wiki/AppImage AppImage] (Wikipedia).
* [[Press]]. List of annotated links, mostly blog posts.
* [[Probe comparison]]
* [[Link Instruments MSO-19|MSO-19]]. Mixed oscilloscope and logic analyser by Link Instruments that (or rather its driver) crashes PulveView at startup when connected (until some time in mid 2018(?)). Some reverse engineering has been done in 2012, but it is not supported (has status "Planned"). [https://sigrok.org/bugzilla/show_bug.cgi?id=1155 Sigrok bug report for the crash]. [http://www.linkinstruments.com/doupdate_mso19.htm Software download page for it.]
* [[Windows|sigrok, Microsoft Windows page]]
** [[Windows#Device specific USB driver|Device specific USB driver - WinUSB - Zadig]]

===Protocol decoders===

* The [[CAN|CAN bus protocol decoder]]
* [[Protocol decoder HOWTO]]
* [[Protocol decoder API]]
* [[Protocol decoders#Supported protocol decoders|Supported protocol decoders]]

===Building sigrok===

* On Debian (e.g. Raspberry Pi): [[Linux#Installing the requirements 2|Installing required software]]
* On Debian (e.g. Raspberry Pi): [[Linux#Building 3|Actual build]]
* Alternative to following the wiki pages: [https://sigrok.org/gitweb/?p=sigrok-util.git;a=blob;f=cross-compile/linux/sigrok-cross-linux;h=2c8e559efde8cf6ae9a365bf1a4324a33600fae7;hb=HEAD a script that will do most of it]. (''[sigrok-util.git] / cross-compile / linux / sigrok-cross-linux'')
* Windows:
**On Windows: [[Windows#Native_build_using_MSYS2|Native build using MSYS2]] (but may not really work - sigrok-cli and PulseView are listed as not working).
**[[Windows#Cross-compile_using_MXE|Cross compile on Linux]] (using [http://mxe.cc/ MXE]). The script is [https://sigrok.org/gitweb/?p=sigrok-util.git;a=blob;f=cross-compile/mingw/sigrok-cross-mingw;h=8330406ecd28969d8d29c8ad23df8968a4b9ec68;hb=HEAD /sigrok-util/cross-compile/mingw/sigrok-cross-mingw]. Used for nightlies? [https://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=debug,platform=cross-i686-w64-mingw32/ Jenkins page for the debug version].
* The Jenkins thingy - automatic build, e.g. nightlies for PulseView and "AppImage" (self-contained executable for x86 Linux). Sample: [https://sigrok.org/jenkins/job/sigrok-cli/ sigrok-cli] with 44 configurations (43 cross-compiles), e.g. cross-x86_64-w64-mingw32 (for Windows 64-bit?).
* The [[Building#Installing_to_a_non-standard_directory_using_LD_LIBRARY_PATH|LD_LIBRARY_PATH trick]]

KERN scale series

2022-11-05T22:57:58Z

PeterMortensen: Copy edited (e.g. ref. <https://en.wikipedia.org/wiki/RS-232>, <https://en.wikipedia.org/wiki/Symbol_rate>, and <http://english.stackexchange.com/questions/15953>).

{{Infobox multimeter
| image = [[File:Kern ew-6200-2nm mugshot.png|180px]]
| name = KERN scale
| status = supported
| source_code_dir = kern-scale
| counts =
| categories =
| connectivity = [[Device_cables#KERN_EW_6200-2NM_cable|RS-232]]
| measurements = mass
| features =
| website = [http://www.kern-sohn.com/shop/en/laboratory-balances/precision-balances/ kern-sohn.com]
}}

The '''KERN scale''' is a series of weighing scales with RS-232 connectivity.

== Devices ==

{| border="0" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
!Device
!Max. weight
!Readout
!Protocol
!Comments

|-
| KERN EW 220-3NM
| 220 g
| 0.001 g
| 14/15-byte ASCII
|
|-
| KERN EW 420-3NM
| 420 g
| 0.001 g
| 14/15-byte ASCII
|
|-
| KERN EW 620-3NM
| 620 g
| 0.001 g
| 14/15-byte ASCII
|
|-
| KERN EW 820-2NM
| 820 g
| 0.01 g
| 14/15-byte ASCII
|
|-
| KERN EW 2200-2NM
| 2200 g
| 0.01 g
| 14/15-byte ASCII
|
|-
| KERN EW 4200-2NM
| 4200 g
| 0.01 g
| 14/15-byte ASCII
|
|-
| [[KERN EW 6200-2NM]]
| 6200 g
| 0.01 g
| 14/15-byte ASCII
|
|-
| KERN EW 12000-1NM
| 12000 g
| 0.1 g
| 14/15-byte ASCII
|
|-
| KERN EG 220-3NM
| 220 g
| 0.001 g
| 14/15-byte ASCII
|
|-
| KERN EG 420-3NM
| 420 g
| 0.001 g
| 14/15-byte ASCII
|
|-
| KERN EG 620-3NM
| 620 g
| 0.001 g
| 14/15-byte ASCII
|
|-
| KERN EG 2200-2NM
| 2200 g
| 0.01 g
| 14/15-byte ASCII
|
|-
| KERN EG 4200-2NM
| 4200 g
| 0.01 g
| 14/15-byte ASCII
|

|}

== Protocol ==

The devices use a simple ASCII-based protocol over an [[Device_cables#KERN_EW_6200-2NM_cable|RS-232 cable]].

The default settings are (device-dependent), e.g., 1200 8N2, but the devices usually have a menu where the user can change the baud rate, parity settings, and so on.

There are two different packet lengths (also user-configurable via the menu): 14-byte packets and 15-byte packets.

See e.g. the [http://dok.kern-sohn.com/downloads/de/EW%206200-2NM/file/EW_EG-(N)-EWB-BA-e-1226.pdf KERN EW/EG-N/EWB series user manual] for more protocol details.

== Resources ==

* [http://www.kern-sohn.com/shop/en/laboratory-balances/precision-balances/ Device list]

Talk:PulseView

2022-09-23T12:57:45Z

PeterMortensen: /* Broken link */ Refinement (for easier navigation).

== Broken link ==

The link "PulseView manual" in sub section ''[[PulseView#Manual|Manual]]'' is broken:

: ''"Not Found. The requested URL was not found on this server"''

--[[User:PeterMortensen|PeterMortensen]] ([[User talk:PeterMortensen|talk]]) 17:25, 31 March 2022 (CEST)

:: Some alternatives are:
::
::#[https://sigrok.org/doc/pulseview/0.4.1/manual.pdf https://sigrok.org/doc/pulseview/0.4.1/manual.pdf] ([https://www.sigrok.org/blog/libsigrokdecode-041-released 2016-12-27 release])
::#[https://sigrok.org/doc/pulseview/0.4.2/manual.pdf https://sigrok.org/doc/pulseview/0.4.2/manual.pdf] ([https://sigrok.org/blog/pulseview-042-released 2020-04-01 release])
::#[http://sigrok.org/gitweb/?p=pulseview.git;a=tree;f=manual;h=03eded2ba33f8df0238b3ea519866cff01d41805;hb=HEAD Manual ''source''] ([https://en.wikipedia.org/wiki/Markdown Markdown format]), one file per chapter, for the current development version ("unstable"), presumably for the version linked to in the article. The order of chapters is defined by file [http://sigrok.org/gitweb/?p=pulseview.git;a=blob;f=manual/manual.txt;h=19baff63157442dddefa605b8a7600a0225601d1;hb=HEAD manual.txt] (file 'license.txt' is chapter 1). [http://sigrok.org/gitweb/?p=pulseview.git;a=log;h=HEAD Log].
::
:: --[[User:PeterMortensen|PeterMortensen]] ([[User talk:PeterMortensen|talk]]) 17:17, 18 August 2022 (CEST)

Talk:Main Page

2022-09-08T14:45:51Z

PeterMortensen: /* Broken link (Gmane) */ It isn't a local problem.

==Questions regarding the wiki==

If anybody has questions regarding the wiki, like the ones below, where is the place? --[[User:Manorainjan|Manorainjan]] ([[User talk:Manorainjan|talk]]) 20:12, 5 March 2017 (CET)

:: It's probably best to discuss any non-trivial changes on the [http://webchat.freenode.net/?channels=%23sigrok&uio=MT1mYWxzZQ9a #sigrok IRC channel on Freenode], that's where most of the active development discussions take place. --[[User:Uwe Hermann|Uwe Hermann]] ([[User talk:Uwe Hermann|talk]]) 00:55, 7 March 2017 (CET)

==Frequency counters==

I added [[:Category:Frequency counter]]. A comparison list seems to be there not yet.
Should I create one, or does anyone more experienced like to do it? --[[User:Manorainjan|Manorainjan]] ([[User talk:Manorainjan|talk]]) 20:12, 5 March 2017 (CET)

:: I've added a basic page with the usual info, feel free to extend and add more (PC-attachable) devices, if any. --[[User:Uwe Hermann|Uwe Hermann]] ([[User talk:Uwe Hermann|talk]]) 00:55, 7 March 2017 (CET)

==Category Device==
I tend to remove the category device from pages that belong to a more specific category as well, like multimeter or counter.
But maybe someone sees a specific reason for keeping this redundancy? --[[User:Manorainjan|Manorainjan]] ([[User talk:Manorainjan|talk]]) 20:12, 5 March 2017 (CET)

:: Yes, that's intentional and is done on all current pages. Please don't remove those categories. All devices should be in as many categories as required to describe all the hardware facilities (e.g. and MSO will be in the following categories: Device, Logic analyzer, Oscilloscope, Mixed-signal oscilloscope). The redundancy is not a problem, and it's intentional. --[[User:Uwe Hermann|Uwe Hermann]] ([[User talk:Uwe Hermann|talk]]) 00:55, 7 March 2017 (CET)

== Broken link (Gmane) ==

In section ''"Getting in touch"'': the '''''news.gmane.org''''' link times out.

The first two worked fine.

--[[User:PeterMortensen|PeterMortensen]] ([[User talk:PeterMortensen|talk]]) 16:44, 8 September 2022 (CEST)

Talk:Main Page

2022-09-08T14:44:22Z

PeterMortensen: /* Broken link (Gmane) */ new section

==Questions regarding the wiki==

If anybody has questions regarding the wiki, like the ones below, where is the place? --[[User:Manorainjan|Manorainjan]] ([[User talk:Manorainjan|talk]]) 20:12, 5 March 2017 (CET)

:: It's probably best to discuss any non-trivial changes on the [http://webchat.freenode.net/?channels=%23sigrok&uio=MT1mYWxzZQ9a #sigrok IRC channel on Freenode], that's where most of the active development discussions take place. --[[User:Uwe Hermann|Uwe Hermann]] ([[User talk:Uwe Hermann|talk]]) 00:55, 7 March 2017 (CET)

==Frequency counters==

I added [[:Category:Frequency counter]]. A comparison list seems to be there not yet.
Should I create one, or does anyone more experienced like to do it? --[[User:Manorainjan|Manorainjan]] ([[User talk:Manorainjan|talk]]) 20:12, 5 March 2017 (CET)

:: I've added a basic page with the usual info, feel free to extend and add more (PC-attachable) devices, if any. --[[User:Uwe Hermann|Uwe Hermann]] ([[User talk:Uwe Hermann|talk]]) 00:55, 7 March 2017 (CET)

==Category Device==
I tend to remove the category device from pages that belong to a more specific category as well, like multimeter or counter.
But maybe someone sees a specific reason for keeping this redundancy? --[[User:Manorainjan|Manorainjan]] ([[User talk:Manorainjan|talk]]) 20:12, 5 March 2017 (CET)

:: Yes, that's intentional and is done on all current pages. Please don't remove those categories. All devices should be in as many categories as required to describe all the hardware facilities (e.g. and MSO will be in the following categories: Device, Logic analyzer, Oscilloscope, Mixed-signal oscilloscope). The redundancy is not a problem, and it's intentional. --[[User:Uwe Hermann|Uwe Hermann]] ([[User talk:Uwe Hermann|talk]]) 00:55, 7 March 2017 (CET)

== Broken link (Gmane) ==

In section ''"Getting in touch"'': the '''''news.gmane.org''''' link times out.

--[[User:PeterMortensen|PeterMortensen]] ([[User talk:PeterMortensen|talk]]) 16:44, 8 September 2022 (CEST)

Link Instruments MSO-19

2022-08-18T19:49:09Z

PeterMortensen: /* Resources */ Some copy editing (ref. <https://en.wikipedia.org/wiki/GitHub>).

[[File:Link Instruments MSO-19 front.png|thumb|right|Link Instruments MSO-19]]

The [http://www.linkinstruments.com/mso19.htm Link Instruments MSO-19] is a 2GSa/s (repetitive) or 200MSa/s (one-shot) one-channel oscilloscope, 200MSa/s eight-channel logic analyzer, 100MSa/s pattern generator and a TDR. Acquisition is done to local memory (1Ksa depth per channel) before samples get sent to the PC. It is small and USB powered, thus portable. Price is $249 (including probe, clips, wires and software). The MSO-28 specs are similar but this device provides two analog channels ($325).

See [[Link Instruments MSO-19/Info]] for more details (such as '''lsusb -vvv''' output) about the device.

'''Note:''' There is already some unused driver code in <code>src/hardware/link-mso19</code> ([https://sigrok.org/gitweb/?p=libsigrok.git;a=tree;f=src/hardware/link-mso19;hb=HEAD see here]).

== Hardware ==

* [http://www.latticesemi.com/products/cpld/machxo/index.cfm Lattice MachXO LCMXO2280 PLD]
* [http://www.intersil.com/products/deviceinfo.asp?pn=KAD2710C-10 Kenet KAD2710C-10 10bit, 105MSPS ADC]
* [http://www.silabs.com/products/interface/usbtouart/Pages/usb-to-uart-bridge.aspx Silabs CP2103 USB to UART Bridge]

== Photos ==

<gallery>
File:Link Instruments MSO-19 front.jpg|<small>Device, front</small>
File:Link Instruments MSO-19 back.jpg|<small>Device, back</small>
File:Link Instruments MSO-19 PCB top.jpg|<small>PCB, front</small>
File:Link Instruments MSO-19 PCB bottom.jpg|<small>PCB, back</small>
</gallery>

== Protocol ==

=== USB protocol ===

It's just serial-over-USB, supported by the Linux kernel through the '''[http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob;f=drivers/usb/serial/cp210x.c;hb=90a4c0f51e8e44111a926be6f4c87af3938a79c3 cp210x]''' driver. The Link Instruments Vendor/Product ID ('''3195:f190''') was added to the driver by kernel version '''[https://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv3.x%2Fpatch-3.2.50.xz;z=1468 3.2.50]'''. Earlier versions may need to be patched.

iSerial was exploited by Link Instruments to store hardware type, hardware revision, calibration quirks and the actual serial number.
*for an iSerial of 4294333650260000000 we have:
**42943 336 502 6 0 000000
***vbit = 42943 / 10000
***dacoffset = 336
***offsetrange = 502
***hwmodel = 6
***hwrev = 0
***serial number = 000000

=== Serial protocol ===

*Control message
**Fixed header: 0x40, 0x4c, 0x44, 0x53, 0x7e
**Variable size payload, 16bit aligned
***Looks like each 16bits of payload are a register write operation
***register writes are 4bits for addr, 8 bits for value, 2 unused bits and 2 bits im not sure what they are for :)
**** The simplest explanation for the unused bits is that the device bus width is 7 bits (being a CPLD that is very acceptable).
**** The 2 special bits seem to be synchronization bits. 0x7e violates the conversion (high byte), and that may be used to reset the CPLD parser at the end of the packet.
***.?12 AAAA .?34 5678
***Conversion is: ((v & 0x3f) | ((v & 0xc0) << 6) | ((a & 0xf) << 8) | (((v ^ 0x20) & 0x20) << 1) | (((v ^ 0x80) & 0x80) << 7))
***Byte order is big endian
**Fixed footer: 0x7e

=== Registers description ===

There is no way to read from registers, only write is possible.

The purpose of registers 0 to 13 seems to depend on the value of the 2 lsbs of register 15.

'''Registers for ((R15 & 0x3) == 0x0):'''

* Read Sample buffer (1): Write 0 to this register to read the samples buffer.
* Read Trigger status (2): Write 0 to this register to read the trigger status.
* TRIGGER_CONFIG_L (3):
** lsbyte of the threshold value.
* TRIGGER_CONFIG_H (4):
** bits [1:0] hold the msbits of the threshold value
** (1 << 2): Trigger on falling edge
** (1 << 4 | 1 << 3): Select the purpose of the "Output" connector:
*** 00 : Trigger pulse output
*** 01 : PWM DAC from the pattern generator buffer.
*** 10 : (?) never seen...
*** 11 : White noise
** (1 << 6 | 1 << 5): These hold the DSO/LA trigger configuration:
*** 00 : DSO level trigger
*** 01 : DSO pulse trigger, width less than TRIGGER_WIDTH
*** 10 : DSO pulse trigger, width equal or greater than TRIGGER_WIDTH
*** 11 : LA combination trigger
* LA_TRIGGER(5): The value of the LA byte that generates a trigger event (in that mode).
* LA_TRIGGER_MASK(6): The mask for the LA_TRIGGER (bits set to 0 matter, those set to 1 are ignored).
* SCOPE_TRIGGER_HOLDOFF1 (7):
* SCOPE_TRIGGER_HOLDOFF2 (8): Store the trigger holdoff (delay between a triggering event and the trigger rearming).
* CLKRATE(9-10):
* TRIGGER_WIDTH (11): Stores the pulse width for the DSO pulse trigger, in sample units. Forced to be greater than 3 by the mso19 app.
* DAC(12-13):

'''Registers for ((R15 & 0x3) == 0x1):'''

This mode seems to be used to configure the pattern generator.

* REG_PATGEN_CLOCK1 (2) :
* REG_PATGEN_CLOCK2 (3) : Stores the sample clock configuration. Not sure how these two bytes work together...
* REG_PATGEN_START_L (4):
* REG_PATGEN_START_H (5): The start address for the pattern generator buffer (1023 samples long). When writing to the buffer, it is set to 0.
* REG_PATGEN_END_L (6):
* REG_PATGEN_END_H (7): The end address for the pattern generator buffer (1023 samples long). When writing the buffer, it is set to 0x3ff. When in normal mode (to set the end of the output) it is writen as the end address minus 2 (probably due to the actual implementation details).
* PATGEN_CFG (8): Configures the pattern generator.
** (1 << 0): Continuous mode ? (only seems to be allowed for the waveform generator, not for the pattern generator. why?)
** (1 << 1): Enter pattern write mode.
** (1 << 3 | 1 << 2):
*** 11 : Manual start (starts after a pulse in PATGEN_TRIG)
*** 10 : Start on MSO trigger
*** 01 : Start on MSO "Go" (MSO trigger arm)
*** 00 : Disabled
* PATGEN_TRIG (9): writen 0x1 and then 0x0, acts as a manual trigger to activate "stuff".
* PATGEN_WORD (10): In pattern write mode, takes the word for the current "instant".
* PATGEN_IO (11): In pattern write mode, writing 0x1 makes the instant an output one, and writing 0x0 makes it an input one (?)
* PATGEN_LOOPS (12): Stores the number of loops for the pattern generator. Set to 1 for pattern buffer writing mode.
* PATTERN_MASK (13): Stores the output bit mask (1 for enabled bits, 0 for disabled bits)

'''Registers for ((R15 & 0x3) == 0x2):'''

This mode is used to set the i2c or spi triggers.

NOTES:
* the difference between i2c and spi capture seems to be the TRIGGER_CFG_H bits (see R15 = 0)
* how does the hardware handle the start/stop conditions or the ack bit??

The protocol matcher seems to be comprised of a 4 byte shift register. The serial bits are shifted in through the last byte comparator (word 3) and exit through the first byte comparator (word 0). This is why if the trigger is set up with less than 3 words, the first bytes are the ones that end up matching everything (word set to 0x00, mask set to 0xff).

The mask bytes have their bits set to 1 for "ignore", and 0 for "match". The protocol matching block simply doing something this for every bit i:

matches[i] = (read[i] ^ word[i]) | mask[i]

The final result is the and'ing of the resulting 32 bits.

* TRIG_WORD0 (0): Hold the comparison words for the comparator.
* TRIG_WORD1 (1):
* TRIG_WORD2 (2):
* TRIG_WORD2 (3):
* TRIG_MASK0 (4): Holds the mask for the comparator (bits set at 1 always produce a positive match)
* TRIG_MASK1 (5):
* TRIG_MASK2 (6):
* TRIG_MASK3 (7):
* TRIG_SPI_MODE (8): Holds the SPI mode for triggering (valid modes 0, 1, 2, 3). Is set to 0 for I2C (not sure if mandatory)

'''Registers which don't seem to change purpose (so far):'''

*CONTROL1 (14):
**(1 << 0): Reset SFM
**(1 << 3): Force trigger
**(1 << 4): Enable ADC (?)
**(1 << 6): Reset ADC (?)
**(1 << 7): Led on/off
*CONTROL2 (15):
** (1 << 1 | 1 << 0): Control which register bank is selected for writing:
*** 00: The DSO and LA control bank is selected
*** 01: The PG (patern generator) control bank is selected
*** 10: The PT (protocol trigger) control bank is selected
** (1 << 5): Slow mode (?) (set for the low clock rates, probably enables a clock divider)

=== Device reply description ===

* After writing 0x0 to the registers (1) or (2) of bank 0, the device replies with either 3072 bytes (1), or 1 byte (2).
* Only 7 bits are used from each byte.
* Bit (1 << 6) indicates which type of message this is:
** 0: This is a "status" message.
** 1: This is a "data" message.

'''STATUS ((1 << 6) == 0):'''

* The reply comprises just one byte. The lower nibble contains the trigger status (t), while the other two bits contain other status info (?)
** [ (ignored) 0 (h1) (h0) (t3) (t2) (t1) (t0) ]

Bit description:
** (1 << 5): Seems to be always set to 1 (?)
** (1 << 4): The state of the control bit (1 << 4): adc enabled (?).
** (1 << 3): Set to 1 upon successful triggering.
** (1 << 2): Set to 1 when the trigger block is armed and the adc (1 << 4) is also enabled (?)
** (1 << 1): Set to 1 when the trigger block is armed but the adc (1 << 4) is not (?)
** (1 << 0): Seems to be the oposite of bit (1 << 2) (?)

* Ususal values for t(3:0):
** 0x6: Triggered (data ready on the samples buffer).
** 0x4: Trigger armed
** 0x3: Someone messed up and armed the trigger without enabling ctl bit (1 << 4) (???)
** 0x1: Trigger not armed

'''DATA ((1 << 6) == 1):'''

* The reply is 24 bit aligned, and contains both the 10 bit analog sample data (a) and the 8 bit digital sample data (d).
* There's a total of 3072 bytes, comprising 1024 samples.
* For each group of 24 bits (a "sample"):
** (byte 0): [ (ignored) 1 (a5) (a4) (a3) (a2) (a1) (a0) ]
** (byte 1): [ (ignored) 1 (d1) (d0) (a9) (a8) (a7) (a6) ]
** (byte 2): [ (ignored) 1 (d7) (d6) (d5) (d4) (d3) (d2) ]

=== Device operation ===

The trigger status must be checked periodically, by writing 0 to the "Read Status" register (address 0 of bank 0). The returned value indicates the device status.

'''Startup:'''

* The MSO19 application starts by checking the device status. It accepts the values 0x21 or 0x31 as normal, before proceeding.
* It then resets the ADC, and checks for the device status again, and also accepts the values 0x21 and 0x31 as normal.
(...)

'''Capture Start:'''

Upon starting a capture, by hitting the "Go" button:
* If the DSO or the DAC need to be configured, the app resets the FSM (finite state machine), and then configures them both.
* If the PG needs to be configured, the app configures it.
* The app then arms the trigger system.
* Finally the app issues a trigger check (writing 0 to the register), and waits for the serial reply.

'''Handle Serial Reply:'''

* First the app checks how many bytes there are waiting on the serial port buffer. It only accepts two byte lengths, 3072 bytes and 1 byte.
* The app then checks if the first byte has bit 6 turned off ((byte & (1 << 6)) == 0), and if it is, it assumes it's a trigger status. Otherwise it assumes it's sample data.

== Resources ==

* [https://linkinstruments.com/mso19.html MSO-19 product page]
* [https://linkinstruments.com/mso28.html MSO-28 product page]
* [https://www.linkinstruments.com/wiki/index.php?title=PiMSO19 linkinstruments.com: PiMSO19]
** [https://github.com/tkrmnz/mso19fcgi GitHub: mso19fcgi] (contains some source code for MSO-19)
* [https://www.linkinstruments.com/wiki/index.php?title=PiMSO linkinstruments.com: PiMSO] (for MSO-28)
** [https://www.linkinstruments.com/wiki/index.php?title=MSO28_Registers linkinstruments.com: MSO28 registers]
** [https://github.com/tkrmnz/mso28fcgi/ GitHub: mso28fcgi] (contains some source code for MSO-28)

[[Category:Device]]
[[Category:Logic analyzer]]
[[Category:Oscilloscope]]
[[Category:Mixed-signal oscilloscope]]
[[Category:Planned]]

Link Instruments MSO-19/Info

2022-08-18T19:41:54Z

PeterMortensen: Added an escape (this page turns up in search results).

== lsusb ==

This is the lsusb ouput on Linux (serial number changed):

<small>
$ '''lsusb -vvv'''
Bus 007 Device 005: ID '''3195:f190'''
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x3195
idProduct 0xf190
bcdDevice 3.10
iManufacturer 1 '''Silicon Labs'''
iProduct 2 '''MSO-19 Link Instruments'''
iSerial 3 4294333650260000000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 450mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 2 MSO-19 Link Instruments
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)
</small>

== See also ==

* [[Link Instruments MSO-19]]

Talk:PulseView

2022-08-18T15:17:53Z

PeterMortensen: /* Broken link */ Added workarounds, so at least the information is available. It could be considered adding some of the information to the article itself.

== Broken link ==

The link "PulseView manual" in sub section ''[[PulseView#Manual|Manual]]'' is broken:

: ''"Not Found. The requested URL was not found on this server"''

--[[User:PeterMortensen|PeterMortensen]] ([[User talk:PeterMortensen|talk]]) 17:25, 31 March 2022 (CEST)

:: Some alternatives are:
::
::#[https://sigrok.org/doc/pulseview/0.4.1/manual.pdf https://sigrok.org/doc/pulseview/0.4.1/manual.pdf] ([https://www.sigrok.org/blog/libsigrokdecode-041-released 2016-12-27 release])
::#[https://sigrok.org/doc/pulseview/0.4.2/manual.pdf https://sigrok.org/doc/pulseview/0.4.2/manual.pdf] ([https://sigrok.org/blog/pulseview-042-released 2020-04-01 release])
::#[http://sigrok.org/gitweb/?p=pulseview.git;a=tree;f=manual;h=03eded2ba33f8df0238b3ea519866cff01d41805;hb=HEAD Manual ''source''] ([https://en.wikipedia.org/wiki/Markdown Markdown format]), one file per chapter, for the current development version ("unstable"), presumably for the version linked to in the article. [http://sigrok.org/gitweb/?p=pulseview.git;a=log;h=HEAD Log].
::
:: --[[User:PeterMortensen|PeterMortensen]] ([[User talk:PeterMortensen|talk]]) 17:17, 18 August 2022 (CEST)

PulseView

2022-08-18T15:17:24Z

PeterMortensen: Some copy editing (e.g. ref. <https://git-scm.com/book/en/v2/Git-on-the-Server-GitWeb>, <https://en.wikipedia.org/wiki/GitHub>, <https://en.wikipedia.org/wiki/Bug_tracking_system>, and <https://en.wikipedia.org/wiki/Clang>). Applied some formatting.

[[File:PulseView I2C DS1307 Decode.png|thumb|320px|right|PulseView (10-Aug-2014)]]
[[File:Pulseview rigol 2 analog channels.png|thumb|320px|PulseView + scope]]

'''PulseView''' (sometimes abbreviated as "PV") is a Qt based logic analyzer, oscilloscope and MSO GUI for sigrok.

It is licensed under the terms of the '''GNU GPL, version 3 or later'''.

== Features ==

* Fast O(log N) signal rendering at all zoom levels.
* [[Protocol decoders|Protocol decoder]] support
* Trace groups support

== Manual ==

Please refer to the [https://sigrok.org/doc/pulseview/unstable/manual.html PulseView manual] for a lot more information.

If you are updating the manual and want to check what your changes look like, you can use "make manual" to build it.

There's also a video made by the original author of PulseView on YouTube that explains the basics of logic analyzers in general, how to use them and how they work with PulseView: ''[https://www.youtube.com/watch?v=dobU-b0_L1I 001 Sigrok and Logic Analyzers]''

== Download ==

Binaries, distro packages and source code tarballs are available from [[Downloads]].

Git:

$ '''git clone git://sigrok.org/pulseview.git'''

You can also [http://sigrok.org/gitweb/?p=pulseview.git;a=summary browse the source code] via GitWeb.

== Requirements ==

See [[Building#PulseView|build requirements for PulseView]].

== Building ==

See [[Linux#PulseView|building PulseView on Linux]] (or any other of the [[Building#Building_from_source|OS-specific instruction pages]]).

'''Additional notes:'''

* Use <code>PKG_CONFIG_PATH=/''<prefix-of-libsigrok-installation>''/lib/pkgconfig/</code> if [[libsigrok]] and [[libsigrokdecode]] are installed to a non-standard prefix. See also [[Building#Installing_to_a_non-standard_directory_using_LD_LIBRARY_PATH]] for more details.
* To change the install prefix: <code>cmake -DCMAKE_INSTALL_PREFIX=''<prefix-dir>''/ ..</code>
* To show compiler arguments during the build: <code>make VERBOSE=1</code>
* To make a non-stripped debug build <code>cmake -DCMAKE_BUILD_TYPE=Debug ..</code>
* To enable unit tests: <code>cmake -DENABLE_TESTS=y ..</code>
* To enable decoders: <code>cmake -DENABLE_DECODE=y ..</code>
* To disable -Werror: <code>cmake -DDISABLE_WERROR=y ..</code>
* To build with Clang: <code>CXX=clang++ cmake ..</code>

== Translations ==

PulseView supports translations and so it would be nice if users like you would contribute translations of the user interface that we can include. All you need is a clone of the PulseView repository (either using our Git repo or the GitHub repo), lupdate and Qt Linguist - on Ubuntu, the last two are included in the qttools5-dev and qttools5-dev-tools packages.

After obtaining a copy of the repository, look up the [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1 code] for the language you want to translate to and create an untranslated language file. Using Germany (DE) as an example, you'd do

cd where/you/unpacked/the/PulseView/repo
lupdate -recursive . -ts l10n/de.ts

or, if the language has a regional flavor, additionally with a [https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes Alpha-2 ISO code] (here for Mexican Spanish):

cd where/you/unpacked/the/PulseView/repo
lupdate -recursive . -ts l10n/es_mx.ts

Then, open the newly created .ts file in Qt Lingust and go through the translations just like its [https://doc.qt.io/qt-5/linguist-translators.html manual] describes. We are aware that some terms are unique to sigrok/PulseView and thus hard to translate, but please try to preserve the spirit of the word, even if there isn't any literal translation. Sometimes, this is however not possible, and that's okay. For the German translation, for example, the words "annotation" and "decode trace row" have no suitable equivalents, so we had to make use of translations in spirit ("decoded values" for annotations and "category" for decode trace row), as unfortunate as this is.

When you're done with your translations, set the language of the translations in Qt Linguist (menu ''Edit'' → ''Translation File Settings'') and put it somewhere where we can access it - e.g., the [https://sigrok.org/bugzilla/ bug tracker] or the mailing list. We'll then take the file and incorporate it into the build. Either way, we'll add your name to the application credits and keep your email on file, so that we can contact you when additional translations are needed - there isn't any obligation, but we'd appreciate if you'd then update the translation for the language you chose to submit to us.

== Resources ==

* [[PulseView/Architecture|PulseView architecture overview]]
* [[TODO#PulseView|PulseView TODO list]]
* [[PulseView/Concepts|PulseView GUI concepts]]
* [https://www.ohloh.net/p/pulseview PulseView on ohloh]
* [http://airwebreathe.org.uk/doku.php?id=pulseview Joel Holdsworth's personal PulseView project page]

PulseView

2022-03-31T15:39:15Z

PeterMortensen: Dressed the (effectively) naked links (the link texts have been chosen to not be literal (over the sub section titles) in order to be more specific).

[[File:PulseView I2C DS1307 Decode.png|thumb|320px|right|PulseView (10-Aug-2014)]]
[[File:Pulseview rigol 2 analog channels.png|thumb|320px|PulseView + scope]]

'''PulseView''' (sometimes abbreviated as "PV") is a Qt based logic analyzer, oscilloscope and MSO GUI for sigrok.

It is licensed under the terms of the '''GNU GPL, version 3 or later'''.

== Features ==

* Fast O(log N) signal rendering at all zoom levels.
* [[Protocol decoders|Protocol decoder]] support
* Trace groups support

== Manual ==

Please refer to the [https://sigrok.org/doc/pulseview/unstable/manual.html PulseView manual] for a lot more information.

If you are updating the manual and want to check what your changes look like, you can use "make manual" to build it.

There's also a video made by the original author of PulseView on YouTube that explains the basics of logic analyzers in general, how to use them and how they work with PulseView: ''[https://www.youtube.com/watch?v=dobU-b0_L1I 001 Sigrok and Logic Analyzers]''

== Download ==

Binaries, distro packages and source code tarballs are available from [[Downloads]].

Git:

$ '''git clone git://sigrok.org/pulseview.git'''

You can also [http://sigrok.org/gitweb/?p=pulseview.git;a=summary browse the source code] via gitweb.

== Requirements ==

See [[Building#PulseView|build requirements for PulseView]].

== Building ==

See [[Linux#PulseView|building PulseView on Linux]] (or any other of the [[Building#Building_from_source|OS-specific instruction pages]]).

'''Additional notes:'''

* Use <code>PKG_CONFIG_PATH=/''<prefix-of-libsigrok-installation>''/lib/pkgconfig/</code> if [[libsigrok]] and [[libsigrokdecode]] are installed to a non-standard prefix. See also [[Building#Installing_to_a_non-standard_directory_using_LD_LIBRARY_PATH]] for more details.
* To change the install prefix: <code>cmake -DCMAKE_INSTALL_PREFIX=''<prefix-dir>''/ ..</code>
* To show compiler arguments during the build: <code>make VERBOSE=1</code>
* To make a non-stripped debug build <code>cmake -DCMAKE_BUILD_TYPE=Debug ..</code>
* To enable unit tests: <code>cmake -DENABLE_TESTS=y ..</code>
* To enable decoders: <code>cmake -DENABLE_DECODE=y ..</code>
* To disable -Werror: <code>cmake -DDISABLE_WERROR=y ..</code>
* To build with clang: <code>CXX=clang++ cmake ..</code>

== Translations ==

PulseView supports translations and so it would be nice if users like you would contribute translations of the user interface that we can include. All you need is a clone of the PulseView repository (either using our git repo or the github repo), lupdate and Qt Linguist - on Ubuntu, the last two are included in the qttools5-dev and qttools5-dev-tools packages.

After obtaining a copy of the repository, look up the [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1 code] for the language you want to translate to and create an untranslated language file. Using Germany (DE) as an example, you'd do

cd where/you/unpacked/the/PulseView/repo
lupdate -recursive . -ts l10n/de.ts

or, if the language has a regional flavor, additionally with a [https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes Alpha-2 ISO code] (here for Mexican Spanish):

cd where/you/unpacked/the/PulseView/repo
lupdate -recursive . -ts l10n/es_mx.ts

Then, open the newly created .ts file in Qt Lingust and go through the translations just like its [https://doc.qt.io/qt-5/linguist-translators.html manual] describes. We are aware that some terms are unique to sigrok/PulseView and thus hard to translate but please try to preserve the spirit of the word, even if there's no literal translation. Sometimes, this is however not possible, and that's okay. For the German translation, for example, the words "annotation" and "decode trace row" have no suitable equivalents, so we had to make use of translations in spirit ("decoded values" for annotations and "category" for decode trace row), as unfortunate as this is.

When you're done with your translations, set the language of the translations in Qt Linguist (Edit->Translation File Settings) and put it somewhere where we can access it - e.g. the [https://sigrok.org/bugzilla/ bugtracker] or the mailing list. We'll then take the file and incorporate it into the build. Either way, we'll add your name to the application credits and keep your email on file so that we can contact you when additional translations are needed - there's no obligation but we'd appreciate if you'd then update the translation for the language you chose to submit to us.

== Resources ==

* [[PulseView/Architecture|PulseView architecture overview]]
* [[TODO#PulseView|PulseView TODO list]]
* [[PulseView/Concepts|PulseView GUI concepts]]
* [https://www.ohloh.net/p/pulseview PulseView on ohloh]
* [http://airwebreathe.org.uk/doku.php?id=pulseview Joel Holdsworth's personal PulseView project page]

PulseView

2022-03-31T15:29:36Z

PeterMortensen: /* Manual */ Spelling/case. Dressed the naked link (but how can "[" and "]" be escaped?).

[[File:PulseView I2C DS1307 Decode.png|thumb|320px|right|PulseView (10-Aug-2014)]]
[[File:Pulseview rigol 2 analog channels.png|thumb|320px|PulseView + scope]]

'''PulseView''' (sometimes abbreviated as "PV") is a Qt based logic analyzer, oscilloscope and MSO GUI for sigrok.

It is licensed under the terms of the '''GNU GPL, version 3 or later'''.

== Features ==

* Fast O(log N) signal rendering at all zoom levels.
* [[Protocol decoders|Protocol decoder]] support
* Trace groups support

== Manual ==

Please refer to the [https://sigrok.org/doc/pulseview/unstable/manual.html PulseView manual] for a lot more information.

If you are updating the manual and want to check what your changes look like, you can use "make manual" to build it.

There's also a video made by the original author of PulseView on YouTube that explains the basics of logic analyzers in general, how to use them and how they work with PulseView: ''[https://www.youtube.com/watch?v=dobU-b0_L1I 001 Sigrok and Logic Analyzers]''

== Download ==

Binaries, distro packages and source code tarballs are available from [[Downloads]].

Git:

$ '''git clone git://sigrok.org/pulseview.git'''

You can also [http://sigrok.org/gitweb/?p=pulseview.git;a=summary browse the source code] via gitweb.

== Requirements ==

See [[Building#PulseView]].

== Building ==

See [[Linux#PulseView]] (or any other of the [[Building#Building_from_source|OS-specific instruction pages]]).

'''Additional notes:'''

* Use <code>PKG_CONFIG_PATH=/''<prefix-of-libsigrok-installation>''/lib/pkgconfig/</code> if [[libsigrok]] and [[libsigrokdecode]] are installed to a non-standard prefix. See also [[Building#Installing_to_a_non-standard_directory_using_LD_LIBRARY_PATH]] for more details.
* To change the install prefix: <code>cmake -DCMAKE_INSTALL_PREFIX=''<prefix-dir>''/ ..</code>
* To show compiler arguments during the build: <code>make VERBOSE=1</code>
* To make a non-stripped debug build <code>cmake -DCMAKE_BUILD_TYPE=Debug ..</code>
* To enable unit tests: <code>cmake -DENABLE_TESTS=y ..</code>
* To enable decoders: <code>cmake -DENABLE_DECODE=y ..</code>
* To disable -Werror: <code>cmake -DDISABLE_WERROR=y ..</code>
* To build with clang: <code>CXX=clang++ cmake ..</code>

== Translations ==

PulseView supports translations and so it would be nice if users like you would contribute translations of the user interface that we can include. All you need is a clone of the PulseView repository (either using our git repo or the github repo), lupdate and Qt Linguist - on Ubuntu, the last two are included in the qttools5-dev and qttools5-dev-tools packages.

After obtaining a copy of the repository, look up the [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1 code] for the language you want to translate to and create an untranslated language file. Using Germany (DE) as an example, you'd do

cd where/you/unpacked/the/PulseView/repo
lupdate -recursive . -ts l10n/de.ts

or, if the language has a regional flavor, additionally with a [https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes Alpha-2 ISO code] (here for Mexican Spanish):

cd where/you/unpacked/the/PulseView/repo
lupdate -recursive . -ts l10n/es_mx.ts

Then, open the newly created .ts file in Qt Lingust and go through the translations just like its [https://doc.qt.io/qt-5/linguist-translators.html manual] describes. We are aware that some terms are unique to sigrok/PulseView and thus hard to translate but please try to preserve the spirit of the word, even if there's no literal translation. Sometimes, this is however not possible, and that's okay. For the German translation, for example, the words "annotation" and "decode trace row" have no suitable equivalents, so we had to make use of translations in spirit ("decoded values" for annotations and "category" for decode trace row), as unfortunate as this is.

When you're done with your translations, set the language of the translations in Qt Linguist (Edit->Translation File Settings) and put it somewhere where we can access it - e.g. the [https://sigrok.org/bugzilla/ bugtracker] or the mailing list. We'll then take the file and incorporate it into the build. Either way, we'll add your name to the application credits and keep your email on file so that we can contact you when additional translations are needed - there's no obligation but we'd appreciate if you'd then update the translation for the language you chose to submit to us.

== Resources ==

* [[PulseView/Architecture|PulseView architecture overview]]
* [[TODO#PulseView|PulseView TODO list]]
* [[PulseView/Concepts|PulseView GUI concepts]]
* [https://www.ohloh.net/p/pulseview PulseView on ohloh]
* [http://airwebreathe.org.uk/doku.php?id=pulseview Joel Holdsworth's personal PulseView project page]

Talk:PulseView

PeterMortensen: Minior corrections, etc.

2019-04-17T23:38:37Z

PeterMortensen: /* Shortcuts */ Added an item.

==Recent activity==

===2019-04===

#Building a Docker container for compiling sigrok-cli and PulseView. It is supposed to both run under Linux and Windows (x64).
#Testing a new driver by user ''droghio'' that should work for the [[Tektronix TDS2024B|TDS2024C Tektronix oscilloscope]]. Some placeholding:
#*Part of "lsusb -v" output: "Bus 008 Device 005: ID 0699:03a6 Tektronix, Inc."
#*Notes to self: the ''"[git://sigrok.org/sigrok-util util]"'' repository (for building and stuff) - [https://github.com/sigrokproject/sigrok-util read-only mirror at GitHub]. [https://github.com/sigrokproject/sigrok-util/blob/master/cross-compile/linux/sigrok-cross-linux Cross-built script].

===2018-04===

Submitting comprehensive sample data for CAN bus, both 11-bit and 29-bit messages, and corresponding test cases (mostly for regression test - especially regression for [https://sigrok.org/bugzilla/show_bug.cgi?id=1085 the 2018-04-12 fix to the decoding at the end of the CRC part]).

Notes to self:

# Original acquired analog data: C:\temp2\2017-12-23\CAN decoder, new stuff bit handling at the end of the CRC segment\Data67\In\ACQ000009_Tektronix.txt

===2017-12===

Recording 22483 traces for the purpose of evaluating [https://sigrok.org/bugzilla/show_bug.cgi?id=1085 a proposed fix to the CAN protocol decoder] (actually only changing a single number from 16 to 17), stuff bit at the very end of the CRC segment, with a modified trigger scheme:

* Change the position of the trigger point to the end (right) so there is always a CAN message in the trace (for the previous), but still 26 µs recessive.

The time division was 100 µs / division (about 225 bit times max) to always record whole CAN messages - at 10 samples per bit time.

===2017-07===

Using the sigrok command-line ("sigrok-cli") to bulk process data derived from Tektronix oscilloscope data of 250 kbit/s CAN traffic on a real-world system (mobile cranes). The first sample data set is 5335 oscilloscope traces obtained with the trigger set to a negative pulse on CAN-H (to start off at the end of a CAN message) - corresponding to 6.5 recessive bits, 26 µsec (detecting the space in-between CAN messages). Sometimes there is a CAN message right after this, sometimes it is a bit delayed, and sometimes it is completely empty.

A sample command line (on Windows) is:

<pre>sigrok-cli -P can:bitrate=250000:can_rx="CAN RX" -P timing:data="CAN RX" -I csv:header=true:samplerate=5000000 -i "T:\stdHMF\UserData\scripts\Tektronix2PulseView\_PulseView_AllChannels_ACQ000001_Tektronix_f5000000.txt"</pre>

===2017-04===

Using [[PulseView]] to decode data from a Tektronix oscilloscope of SPI communication to a CAN controller, [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010406 MCP2515].

==Task list==

Currently not in priority order.

* Allow import of analog data through CSV files. (Related: fixed [https://sigrok.org/bugzilla/show_bug.cgi?id=1064 bug 1064] - ''locale'' issue, decimal point, "," vs. ".".).

* Add detection of error frames to the CAN protocol decoder

* Add support for the gigga watt EEVBlog multimeter (Bluetooth, etc.)

* Add a snap feature to the "cursor" (blue) in PulveView

* Change number of significant digits for the time display in the "cursor" (blue) in PulveView

* Submit selected sample traces for CAN decoder change (for CRC segment) validation. With and without stuff bits in various places. With and without timing deviations. (Related: [https://sigrok.org/bugzilla/show_bug.cgi?id=1085 bug 1085], celeron55's fix, '''''if len(self.bits) > self.last_databit + 16''''' → '''''if len(self.bits) > self.last_databit + 17''''' (16 → 17)).

* Add support for the [[Tektronix TDS2000B series|TDS2000]] series in libsigrok, and thus, by extension, use by the new shiny stuff in PulveView.

===On wiki===

* Change recommended procedure for submitting sample Sigrok files (traces), on ''[[Example dumps#Contributing dumps|Example dumps]]''.

==Glossary==

*''BBB'' [https://en.wikipedia.org/wiki/BeagleBoard#BeagleBone_Black BeagleBone Black]
*''GH'' [http://en.wikipedia.org/wiki/GitHub GitHub]
*''ISTR'' ????
*''LA'' Logic analyser
*''ML'' Mailing list
*''OLS'' ????
*''PR'' Pull request (a Git term). ''Not'' "problem report".
*''SR'' Sigrok
*''srd'' ????
*''WIP'' Work in progress. Mostly related to particular Git commits.
*''PD'' protocol decoder. Non-standard spellings are ''Pd'' and ''pd''.
*''PV'' PulseView. Non-standard spellings are ''Pv'' and ''pv''.

==Some bug reports==

* [https://sigrok.org/bug/1155 Possible problem with the MSO-19 USB driver on Windows]. PulveView crashes at startup if the MSO-19 is connected.

==Interests==

I am mostly interested in:

* The [[CAN|CAN protocol decoder]] (that page is currently empty, but it is listed on [[Protocol decoders|the protocol decoders page]])
* CAN bus loggers, like IXXAT's (now acquired by HMS) ''USB-to-CAN compact''/''USB-to-CAN V2'' and Kvaser's ''Memorator''.
* The higher-level [http://en.wikipedia.org/wiki/CANopen CANopen] protocol (on top of CAN)

==Protocol decoders==

===Non-empty wiki pages===

Currently (2017-07-08), 28
of 77 [[Protocol_decoders#Supported protocol decoders|protocol decoders]] (36%) have non-empty pages here on the wiki:

*[[Protocol decoder:Adns5020|ADNS5020]]
*[[Protocol decoder:Am230x|AM230X]]
*[[Protocol decoder:Arm etmv3|ARM ETMV3]]
*[[Protocol decoder:Arm itm|ARM ITM]]
*[[Protocol decoder:Arm tpiu|ARM TPIU]]
*[[Protocol decoder:Aud|AUD]]
*[[Protocol decoder:Avr pdi|AVR PDI]]
*[[Protocol decoder:Dcf77|DCF77]]
*[[Protocol decoder:I2c|I²C]]
*[[Protocol decoder:Ir nec|IR NEC]]
*[[Protocol decoder:Modbus|Modbus]]
*[[Protocol decoder:Mrf24j40|MRF24J40]]
*[[Protocol decoder:Nrf24l01|NRF24L01]]
*[[Protocol decoder:Nunchuk|Nunchuk]]
*[[Protocol decoder:Pan1321|PAN1321]]
*[[Protocol decoder:Parallel|Parallel]]
*[[Protocol decoder:Pwm|PWM]]
*[[Protocol decoder:Qi|Qi]]
*[[Protocol decoder:Rfm12|RFM12]]
*[[Protocol decoder:Rgb led spi|RGB LED SPI]]
*[[Protocol decoder:Rtc8564|RTC8564]]
*[[Protocol decoder:Spdif|SPDIF]]
*[[Protocol decoder:Spi|SPI]]
*[[Protocol decoder:Spiflash|SPI flash]]
*[[Protocol decoder:Stepper motor|Stepper motor]]
*[[Protocol decoder:Tlc5620|TLC5620]]
*[[Protocol decoder:Uart|UART]]
*[[Protocol decoder:Z80|Z80]]

==Profile==

Profile: see [http://en.wikipedia.org/wiki/User:Mortense my Wikipedia user page].

Credentials: more than 5000 edits on the English Wikipedia.

==Shortcuts==

* [https://sigrok.org/doc/pulseview/0.4.1/manual.html PulseView manual]
* [[Sigrok-cli|sigrok-cli man page]]
* [https://plus.google.com/communities/109843678338531936878 Google+ group for sigrok]
* [[PulseView]]. Includes the command line to get the source code using Git.
* [[Downloads#Windows_Download|PulseView, Windows binaries]] (nightly - development). [[Windows#Windows_installers|Alternative location]] (but it seems redundant).
* [[Example dumps|Example data dumps]] - sample data in .sr format. Also includes instructions on how to contribute new ones. Includes the command line to get the whole thing using Git (as of 2017-11-26, 2286 "objects", 724 .sr files, about 65 MB in download size, 192 MB on disk).
* [[Special:Random|Random page]]
* [https://sigrok.org/jenkins/job/sigrok-native-appimage/ Native app image] (not official yet). Is for Linux and x86 only. See also [https://en.wikipedia.org/wiki/AppImage AppImage] (Wikipedia).
* [[Press]]. List of annotated links, mostly blog posts.
* [[Probe comparison]]
* [[Link Instruments MSO-19|MSO-19]]. Mixed oscilloscope and logic analyser by Link Instruments that (or rather its driver) crashes PulveView at startup when connected (until some time in mid 2018(?)). Some reverse engineering has been done in 2012, but it is not supported (has status "Planned"). [https://sigrok.org/bugzilla/show_bug.cgi?id=1155 Sigrok bug report for the crash]. [http://www.linkinstruments.com/doupdate_mso19.htm Software download page for it.]
* [[Windows|sigrok, Microsoft Windows page]]
** [[Windows#Device specific USB driver|Device specific USB driver - WinUSB - Zadig]]

===Protocol decoders===

* The [[CAN|CAN bus protocol decoder]]
* [[Protocol decoder HOWTO]]
* [[Protocol decoder API]]
* [[Protocol decoders#Supported protocol decoders|Supported protocol decoders]]

===Building sigrok===

* On Debian (e.g. Raspberry Pi): [[Linux#Installing the requirements 2|Installing required software]]
* On Debian (e.g. Raspberry Pi): [[Linux#Building 3|Actual build]]
* Alternative to following the wiki pages: [https://sigrok.org/gitweb/?p=sigrok-util.git;a=blob;f=cross-compile/linux/sigrok-cross-linux;h=2c8e559efde8cf6ae9a365bf1a4324a33600fae7;hb=HEAD a script that will do most of it]. (''[sigrok-util.git] / cross-compile / linux / sigrok-cross-linux'')
* Windows:
**On Windows: [[Windows#Native_build_using_MSYS2|Native build using MSYS2]] (but may not really work - sigrok-cli and PulseView are listed as not working).
**[[Windows#Cross-compile_using_MXE|Cross compile on Linux]] (using [http://mxe.cc/ MXE]). The script is [https://sigrok.org/gitweb/?p=sigrok-util.git;a=blob;f=cross-compile/mingw/sigrok-cross-mingw;h=8330406ecd28969d8d29c8ad23df8968a4b9ec68;hb=HEAD /sigrok-util/cross-compile/mingw/sigrok-cross-mingw]. Used for nightlies? [https://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=debug,platform=cross-i686-w64-mingw32/ Jenkins page for the debug version].
* The Jenkins thingy - automatic build, e.g. nightlies for PulseView and "AppImage" (self-contained executable for x86 Linux). Sample: [https://sigrok.org/jenkins/job/sigrok-cli/ sigrok-cli] with 44 configurations (43 cross-compiles), e.g. cross-x86_64-w64-mingw32 (for Windows 64-bit?).
* The [[Building#Installing_to_a_non-standard_directory_using_LD_LIBRARY_PATH|LD_LIBRARY_PATH trick]]

Downloads

2019-04-17T20:08:36Z

PeterMortensen: Spelling (<http://en.wikipedia.org/wiki/OS_X>)

{| border="0" width="100%" style="white-space: margin: 0em; margin-bottom: 2em; border-width: 1em; align:center; vertical-align: top"
|-
!Linux
!Windows
!Mac OS X
!Other

|-
!colspan="4" | {{Rounded_corners|url=https://sigrok.org/wiki/Downloads|bgcolor=#aaaaaa|text=Stable release builds}}

|- style="background-color: white"

| style="width:20%; vertical-align: top" |

{{Rounded_corners|url=https://sigrok.org/download/binary/pulseview/PulseView-0.4.1-i386.AppImage|text=PulseView 0.4.1 (32bit)}}

{{Rounded_corners|url=https://sigrok.org/download/binary/pulseview/PulseView-0.4.1-x86_64.AppImage|text=PulseView 0.4.1 (64bit)}}

{{Rounded_corners|url=https://sigrok.org/download/binary/sigrok-cli/sigrok-cli-0.7.1-i386.AppImage|text=sigrok-cli 0.7.1 (32bit)}}

{{Rounded_corners|url=https://sigrok.org/download/binary/sigrok-cli/sigrok-cli-0.7.1-x86_64.AppImage|text=sigrok-cli 0.7.1 (64bit)}}

| style="width:20%; vertical-align: top" |

{{Rounded_corners|url=https://sigrok.org/download/binary/pulseview/pulseview-0.4.1-32bit-static-release-installer.exe|text=PulseView 0.4.1 (32bit)}}

{{Rounded_corners|url=https://sigrok.org/download/binary/pulseview/pulseview-0.4.1-64bit-static-release-installer.exe|text=PulseView 0.4.1 (64bit)}}

{{Rounded_corners|url=https://sigrok.org/download/binary/sigrok-cli/sigrok-cli-0.7.1-i686-installer.exe|text=sigrok-cli 0.7.1 (32bit)}}

{{Rounded_corners|url=https://sigrok.org/download/binary/sigrok-cli/sigrok-cli-0.7.1-x86_64-installer.exe|text=sigrok-cli 0.7.1 (64bit)}}

| style="width:20%; vertical-align: top" |

{{Rounded_corners|url=https://sigrok.org/download/binary/pulseview/PulseView-0.4.1.dmg|text=PulseView 0.4.1 (64bit)}}

| style="width:20%; vertical-align: top; text-align: center" |

{{Rounded_corners|url=https://sigrok.org/wiki/Downloads#Releases|text=See below}}

|-
! colspan="4" | {{Rounded_corners|url=https://sigrok.org/wiki/Downloads|bgcolor=#aaaaaa|text=Nightly builds}}

|- style="background-color: white"

| style="width:20%; vertical-align: top" |

{{Rounded_corners|url=https://sigrok.org/jenkins/job/sigrok-native-appimage/platform=native-i686-appimage/lastSuccessfulBuild/artifact/cross-compile/appimage/out/PulseView-NIGHTLY-i686.AppImage|text=PulseView (32bit)}}

{{Rounded_corners|url=https://sigrok.org/jenkins/job/sigrok-native-appimage/platform=native-x86_64-appimage/lastSuccessfulBuild/artifact/cross-compile/appimage/out/PulseView-NIGHTLY-x86_64.AppImage|text=PulseView (64bit)}}

{{Rounded_corners|url=https://sigrok.org/jenkins/job/sigrok-native-appimage/platform=native-i686-appimage/lastSuccessfulBuild/artifact/cross-compile/appimage/out/sigrok-cli-NIGHTLY-i686.AppImage|text=sigrok-cli (32bit)}}

{{Rounded_corners|url=https://sigrok.org/jenkins/job/sigrok-native-appimage/platform=native-x86_64-appimage/lastSuccessfulBuild/artifact/cross-compile/appimage/out/sigrok-cli-NIGHTLY-x86_64.AppImage|text=sigrok-cli (64bit)}}

| style="width:20%; vertical-align: top" |

{{Rounded_corners|url=http://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=release,platform=cross-i686-w64-mingw32/lastSuccessfulBuild/artifact/pulseview-NIGHTLY-32bit-static-release-installer.exe|text=PulseView (32bit)}}

{{Rounded_corners|url=https://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=release,platform=cross-x86_64-w64-mingw32/lastSuccessfulBuild/artifact/pulseview-NIGHTLY-64bit-static-release-installer.exe|text=PulseView (64bit)}}

{{Rounded_corners|url=http://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=release,platform=cross-i686-w64-mingw32/lastSuccessfulBuild/artifact/sigrok-cli-NIGHTLY-32bit-static-release-installer.exe|text=sigrok-cli (32bit)}}

{{Rounded_corners|url=https://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=release,platform=cross-x86_64-w64-mingw32/lastSuccessfulBuild/artifact/sigrok-cli-NIGHTLY-64bit-static-release-installer.exe|text=sigrok-cli (64bit)}}

| style="width:20%; vertical-align: top" |

{{Rounded_corners|url=http://sigrok.org/jenkins/job/sigrok-native-macosx/platform=native-macosx/lastSuccessfulBuild/artifact/cross-compile/macosx/build_app/PulseView-NIGHTLY.dmg|text=PulseView (64bit)}}

| style="width:20%; vertical-align: top; text-align: center" |

{{Rounded_corners|url=https://sigrok.org/wiki/Downloads#Releases|text=See below}}

|- style="background-color: white; vertical-align: top;"

| style="text-align:center" | <em><small>Requires a Linux distro more recent than Ubuntu 14.04 LTS (Trusty Tahr) from 2014.</small></em>
| style="text-align:center" | <em><small>Requires Windows XP or higher.</small></em>
| style="text-align:center" | <em><small>Requires OS X 10.9 (Mavericks) or higher.</small></em>
| style="text-align:center" | <em><small>See below for other download options (Android, FreeBSD, source code, etc.).</small></em>

|}

== Releases ==

You can download the latest released tarballs of the following subprojects from [http://sigrok.org/download/ the sigrok.org download directory]:

{| border="0" style="font-size: smaller; white-space: nowrap;" class="alternategrey sigroktable"
|-
!Project
!Release/download
!News

|-
| [[libserialport]]
| [http://sigrok.org/download/source/libserialport/libserialport-0.1.1.tar.gz libserialport-0.1.1.tar.gz]
| [http://sigrok.org/gitweb/?p=libserialport.git;a=blob;f=NEWS;hb=HEAD release notes]

|-
| [[libsigrok]]
| [http://sigrok.org/download/source/libsigrok/libsigrok-0.5.1.tar.gz libsigrok-0.5.1.tar.gz]
| [https://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=NEWS;h=dd44cf53be5b41b9fc586d9fd6a700eae545d6aa;hb=8686b747cd40695c36f998603f6e853ee5eea883 release notes]

|-
| [[libsigrokdecode]]
| [http://sigrok.org/download/source/libsigrokdecode/libsigrokdecode-0.5.2.tar.gz libsigrokdecode-0.5.2.tar.gz]
| [https://sigrok.org/gitweb/?p=libsigrokdecode.git;a=blob;f=NEWS;h=369dbe342036557654c3f9b8980cc9714a138c44;hb=07b9781940ed3c194805ff08e20ae32a90098cb5 release notes]

|-
| [[sigrok-cli]]
| [http://sigrok.org/download/source/sigrok-cli/sigrok-cli-0.7.0.tar.gz sigrok-cli-0.7.0.tar.gz]
| [http://sigrok.org/gitweb/?p=sigrok-cli.git;a=blob;f=NEWS;hb=HEAD release notes]

|-
| [[PulseView]]
| [http://sigrok.org/download/source/pulseview/pulseview-0.4.1.tar.gz pulseview-0.4.1.tar.gz]
| [https://sigrok.org/gitweb/?p=pulseview.git;a=blob;f=NEWS;h=69c7ac5d418bbae896906b8c6b64c6719b1912db;hb=05a4de8abd5810cf8219077259ffa44adb08043e release notes]

|-
| [[Example dumps|sigrok-dumps]]
| [http://sigrok.org/download/source/sigrok-dumps/sigrok-dumps-0.1.0.tar.gz sigrok-dumps-0.1.0.tar.gz]
| [http://sigrok.org/gitweb/?p=sigrok-dumps.git;a=blob;f=NEWS;hb=HEAD release notes]

|-
| [[fx2lafw|sigrok-firmware-fx2lafw]] (source code)
| [http://sigrok.org/download/source/sigrok-firmware-fx2lafw/sigrok-firmware-fx2lafw-0.1.6.tar.gz sigrok-firmware-fx2lafw-0.1.6.tar.gz]
| [http://sigrok.org/gitweb/?p=sigrok-firmware-fx2lafw.git;a=blob;f=NEWS;hb=HEAD release notes]

|-
| [[fx2lafw|sigrok-firmware-fx2lafw]] (prebuilt firmware)
| [http://sigrok.org/download/binary/sigrok-firmware-fx2lafw/sigrok-firmware-fx2lafw-bin-0.1.6.tar.gz sigrok-firmware-fx2lafw-bin-0.1.6.tar.gz]
| [http://sigrok.org/gitweb/?p=sigrok-firmware-fx2lafw.git;a=blob;f=NEWS;hb=HEAD release notes]

|}

== Binaries and distribution packages ==

=== Linux AppImage binaries ===

* Nightly AppImage binaries (require a Linux distro more recent than Ubuntu 14.04 LTS Trusty Tahr from 2014):
** [https://sigrok.org/jenkins/job/sigrok-native-appimage/platform=native-i686-appimage/lastSuccessfulBuild/artifact/cross-compile/appimage/out/PulseView-NIGHTLY-i686.AppImage PulseView-NIGHTLY-i686.AppImage] (32bit)
** [https://sigrok.org/jenkins/job/sigrok-native-appimage/platform=native-x86_64-appimage/lastSuccessfulBuild/artifact/cross-compile/appimage/out/PulseView-NIGHTLY-x86_64.AppImage PulseView-NIGHTLY-x86_64.AppImage] (64bit)
** [https://sigrok.org/jenkins/job/sigrok-native-appimage/platform=native-i686-appimage/lastSuccessfulBuild/artifact/cross-compile/appimage/out/sigrok-cli-NIGHTLY-i686.AppImage sigrok-cli-NIGHTLY-i686.AppImage] (32bit)
** [https://sigrok.org/jenkins/job/sigrok-native-appimage/platform=native-x86_64-appimage/lastSuccessfulBuild/artifact/cross-compile/appimage/out/sigrok-cli-NIGHTLY-x86_64.AppImage sigrok-cli-NIGHTLY-x86_64.AppImage] (64bit)
* Download the correct (32bit or 64bit) AppImage file for your Linux system, make the file executable via "'''chmod +x'''" and then run it.
* If you want to access hardware, please install the [https://sigrok.org/gitweb/?p=libsigrok.git;a=tree;f=contrib udev rules] on your system and reload the rules with udevadm.
* See also [[Linux#AppImage|Linux]] for more information.

=== Linux distribution packages ===

* '''Debian:''' [http://packages.qa.debian.org/s/sigrok.html sigrok] (pulls [http://packages.qa.debian.org/libs/libserialport.html libserialport], [http://packages.qa.debian.org/libs/libsigrok.html libsigrok], [http://packages.qa.debian.org/libs/libsigrokdecode.html libsigrokdecode], [http://packages.qa.debian.org/s/sigrok-cli.html sigrok-cli], [http://packages.qa.debian.org/p/pulseview.html pulseview], [http://packages.qa.debian.org/s/sigrok-firmware-fx2lafw.html sigrok-firmware-fx2lafw])
* '''Ubuntu:''' [http://launchpad.net/ubuntu/+source/sigrok sigrok] (pulls [http://launchpad.net/ubuntu/+source/libserialport libserialport], [http://launchpad.net/ubuntu/+source/libsigrok libsigrok], [http://launchpad.net/ubuntu/+source/libsigrokdecode libsigrokdecode], [http://launchpad.net/ubuntu/+source/sigrok-cli sigrok-cli], [http://launchpad.net/ubuntu/+source/pulseview pulseview], [http://launchpad.net/ubuntu/+source/sigrok-firmware-fx2lafw sigrok-firmware-fx2lafw])
* '''Arch Linux:''' [https://aur.archlinux.org/packages.php?O=0&K=sigrok&do_Search=Go AUR (Arch Linux User Repository)], [https://aur.archlinux.org/packages/libserialport-git/ libserialport], [https://aur.archlinux.org/packages/libsigrok-git/ libsigrok], [https://aur.archlinux.org/packages/libsigrokdecode-git/ libsigrokdecode], [https://aur.archlinux.org/packages/sigrok-cli/ sigrok-cli], [https://aur.archlinux.org/packages/pulseview-git/ pulseview], [https://aur.archlinux.org/packages/sigrok-firmware-fx2lafw/ sigrok-firmware-fx2lafw]
* '''Slackware:''' [http://slackbuilds.org/apps/libserialport/ libserialport], [http://slackbuilds.org/apps/libsigrok/ libsigrok], [http://slackbuilds.org/apps/libsigrokdecode/ libsigrokdecode], [http://slackbuilds.org/apps/sigrok-cli/ sigrok-cli], [http://slackbuilds.org/apps/pulseview/ pulseview], [http://slackbuilds.org/apps/sigrok-firmware-fx2lafw/ sigrok-firmware-fx2lafw]
* '''Fedora:''' [https://src.fedoraproject.org/cgit/rpms/libserialport.git/ libserialport], [https://src.fedoraproject.org/cgit/rpms/libsigrok.git/ libsigrok], [https://src.fedoraproject.org/cgit/rpms/libsigrokdecode.git/ libsigrokdecode], [https://src.fedoraproject.org/cgit/rpms/sigrok-cli.git/ sigrok-cli], [https://src.fedoraproject.org/cgit/rpms/pulseview.git/ pulseview], [https://src.fedoraproject.org/cgit/rpms/sigrok-firmware-fx2lafw.git/ sigrok-firmware-fx2lafw], [https://src.fedoraproject.org/cgit/rpms/sigrok-firmware.git/ sigrok-firmware]
* '''Gentoo:''' [http://packages.gentoo.org/package/dev-libs/libserialport libserialport], [http://packages.gentoo.org/package/sci-libs/libsigrok libsigrok], [http://packages.gentoo.org/package/sci-libs/libsigrokdecode libsigrokdecode], [http://packages.gentoo.org/package/sci-electronics/sigrok-cli sigrok-cli], [http://packages.gentoo.org/package/sci-electronics/pulseview pulseview], [http://packages.gentoo.org/package/sys-firmware/sigrok-firmware-fx2lafw sigrok-firmware-fx2lafw]
* '''openSUSE:''' Latest stable versions are included in Tumbleweed. Leap includes the latest stable version at time of release, newer versions are available from the [http://download.opensuse.org/repositories/electronics/ "electronics" repository], created by the [https://build.opensuse.org/project/show/electronics OpenBuildService (OBS)].
** '''openSUSE weekly GIT:''' [http://download.opensuse.org/repositories/home:/StefanBruens:/branches:/electronics:/GIT/ Repositories], [https://build.opensuse.org/project/show/home:StefanBruens:branches:electronics:GIT OBS Project]

=== Windows ===
<span id="Windows_Download">

* Nightly installer binaries (require Windows XP or higher):
** [http://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=release,platform=cross-i686-w64-mingw32/lastSuccessfulBuild/artifact/pulseview-NIGHTLY-32bit-static-release-installer.exe pulseview-NIGHTLY-32bit-static-release-installer.exe] ([http://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=debug,platform=cross-i686-w64-mingw32/lastSuccessfulBuild/artifact/pulseview-NIGHTLY-32bit-static-debug-installer.exe debug build])
** [https://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=release,platform=cross-x86_64-w64-mingw32/lastSuccessfulBuild/artifact/pulseview-NIGHTLY-64bit-static-release-installer.exe pulseview-NIGHTLY-64bit-static-release-installer.exe] ([https://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=debug,platform=cross-x86_64-w64-mingw32/lastSuccessfulBuild/artifact/pulseview-NIGHTLY-64bit-static-debug-installer.exe debug build])
** [http://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=release,platform=cross-i686-w64-mingw32/lastSuccessfulBuild/artifact/sigrok-cli-NIGHTLY-32bit-static-release-installer.exe sigrok-cli-NIGHTLY-32bit-static-release-installer.exe] ([http://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=debug,platform=cross-i686-w64-mingw32/lastSuccessfulBuild/artifact/sigrok-cli-NIGHTLY-32bit-static-debug-installer.exe debug build])
** [https://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=release,platform=cross-x86_64-w64-mingw32/lastSuccessfulBuild/artifact/sigrok-cli-NIGHTLY-64bit-static-release-installer.exe sigrok-cli-NIGHTLY-64bit-static-release-installer.exe] ([https://sigrok.org/jenkins/job/sigrok-cross-mingw/buildtype=static,debugtype=debug,platform=cross-x86_64-w64-mingw32/lastSuccessfulBuild/artifact/sigrok-cli-NIGHTLY-64bit-static-debug-installer.exe debug build])
* See also [[Windows#Windows_installers|Windows]] for more information.

=== Mac OS X ===

* Nightly DMG binaries (require OS X 10.9 Mavericks or higher):
** [http://sigrok.org/jenkins/job/sigrok-native-macosx/platform=native-macosx/lastSuccessfulBuild/artifact/cross-compile/macosx/build_app/PulseView-NIGHTLY.dmg PulseView-NIGHTLY.dmg] (64 bit x86 only; requires OS X 10.9 (Mavericks) or higher)
* See also [[Mac OS X]] for more information.

=== FreeBSD ===

* [http://www.freshports.org/devel/libserialport/ libserialport], [http://www.freshports.org/devel/libsigrok/ libsigrok], [http://www.freshports.org/devel/libsigrokdecode/ libsigrokdecode], [http://www.freshports.org/science/sigrok-cli/ sigrok-cli], [http://www.freshports.org/science/pulseview/ pulseview], [http://www.freshports.org/science/sigrok-firmware-fx2lafw/ sigrok-firmware-fx2lafw], [http://www.freshports.org/science/sigrok-firmware/ sigrok-firmware], [http://www.freshports.org/science/sigrok-firmware-utils/ sigrok-firmware-utils]

=== OpenBSD ===
* [https://cvsweb.openbsd.org/ports/comms/sigrok/libserialport/ libserialport], [https://cvsweb.openbsd.org/ports/comms/sigrok/libsigrok/ libsigrok], [https://cvsweb.openbsd.org/ports/comms/sigrok/libsigrokdecode/ libsigrokdecode], [https://cvsweb.openbsd.org/ports/comms/sigrok/sigrok-cli/ sigrok-cli], [https://cvsweb.openbsd.org/ports/comms/sigrok/pulseview/ pulseview], [https://cvsweb.openbsd.org/ports/comms/sigrok/sigrok-dumps/ sigrok-dumps], [https://cvsweb.openbsd.org/ports/comms/sigrok/sigrok-firmware-fx2lafw/ sigrok-firmware-fx2lafw]

=== Android ===

* Nightly APK binaries:
** [http://sigrok.org/jenkins/job/sigrok-cross-android/platform=cross-arm-linux-androideabi/lastSuccessfulBuild/artifact/PulseView-NIGHTLY.apk PulseView-NIGHTLY.apk (ARM)]
* See also [[Android]] for more information.

== Source code ==

The development is done in various [http://sigrok.org/gitweb/ git repositories].

See [[Building]] for build instructions.

== Example data ==

See the [[Example dumps]] wiki page.

== Firmware files ==

See the [[Firmware]] wiki page.