sigrok - User contributions [en]

Linux

2010-11-17T23:26:32Z

Ybucavamyva:

[[File:sigrok linux.png|right|thumb|320px|sigrok-gui on Linux]]

This page describes how to build sigrok on Linux.

>== Requirements ==

* git (for cloning the source code repository)
* gcc, g++, make, ...
* autoconf, automake, libtool, pkg-config
* [http://library.gnome.org/devel/glib/unstable/ libglib] >= 2.0
* [http://www.libusb.org libusb] >= 1.0.5
* [http://nih.at/libzip/ libzip] >= 0.8
* [http://www.intra2net.com/en/developer/libftdi/ libftdi] (optional, only required for some devices)

* [http://www.python.org Python] >= 2.5 (optional, only required for protocol decoders)
* [http://qt.nokia.com Qt + Qt Creator] >= 4.5 (optional, only required for building/editing the GUI)

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
>=[http://uwehezeluse.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ifikevim.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----
=[http://ifikevim.co.cc CLICK HERE]=
----
</div>

=[http://uwehezeluse.co.cc CLICK HERE]=
----
</div>

== Installing the build-dependencies ==

On most Linux distributions there are pre-built packages for the sigrok dependencies (if not, you have to build the packages from source). The installation using a package manager is usually pretty simple.

Debian/Ubuntu:

$ '''apt-get install git-core gcc g++ make autoconf automake libtool pkg-config libglib2.0-dev libftdi-dev libusb-1.0-0-dev libzip-dev python-dev qtcreator qt4-designer qt4-dev-tools libqt4-dev'''

Fedora:

$ '''yum install gcc-c++ libtool glib2-devel libftdi-devel libusb1-devel libzip-devel qt-devel python-devel'''

== Building ==

$ '''git clone git://sigrok.git.sourceforge.net/gitroot/sigrok/sigrok'''
$ '''cd sigrok'''
$ '''./autogen.sh'''
$ '''./configure'''
$ '''make'''
$ '''make install'''

Then, for building the GUI:

$ '''cd gui'''
$ '''qmake'''
$ '''make'''

If you get warnings claiming potential symbol conflicts when running qmake, you are likely invoking qt3. Try running qmake-qt4 to force the correct version.

== Distribution packages ==

* Debian / Ubuntu: [[User:Uwe Hermann|Uwe Hermann]] will create [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579600 packages for Debian unstable] (which will semi-automatically migrate to Ubuntu after a while).
* Fedora: See [[Linux/Fedora]].

Dangerous Prototypes Buspirate

2010-11-17T23:26:19Z

Ybucavamyva:

>[[File:Buspirate_v3_front.jpg|thumb|right|The Buspirate v3, front]]
[[File:Buspirate_v3_back.jpg|thumb|right|The Buspirate v3, back]]

The [http://dangerousprototypes.com/2009/11/03/bus-pirate-logic-analyzer-mode/ Buspirate v3] supports a logic analyzer mode and can thus be used for sample captures, however only at low speeds. To quote from the announcement: ''The Bus Pirate can’t store a lot of samples, it can’t feed live samples very fast, and speeds are in the kHz range''.

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

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
>=[http://ucizelulaji.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://imovohege.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
----
=[http://imovohege.co.cc CLICK HERE]=
----
</div>

=[http://ucizelulaji.co.cc CLICK HERE]=
----
</div>

Intronix Logicport/Info

2010-11-17T23:25:54Z

Ybucavamyva:

>== lsusb output ==
For reasons which are not entirely clear, the Logicport identifies as an FTDI device (despite having an EEPROM in which to store a unique VID/PID).

$ '''sudo lsusb -vvv -d 0403:dc48'''
Bus 002 Device 020: ID '''0403:dc48 Future Technology Devices International, Ltd'''
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0403 Future Technology Devices International, Ltd
idProduct 0xdc48
bcdDevice 4.00
iManufacturer 1 Intronix
iProduct 2 LogicPort Logic Analyzer
iSerial 3 19991909
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 200mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2 LogicPort Logic Analyzer
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 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://enamodyg.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----
=[http://enamodyg.co.cc CLICK HERE]=
----
</div>

Braintechnology USB-LPS/Info

2010-11-17T23:25:27Z

Ybucavamyva:

>== lsusb before firmware upload ==

This is the lsusb ouput on Linux, '''before''' any FX2 firmware is uploaded:

$ '''lsusb -vvv'''
Bus 001 Device 117: ID '''16d0:0498'''
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x16d0
idProduct 0x0498
bcdDevice 0.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 171
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 6
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 6
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 3
bNumEndpoints 6
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ixowinuhij.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=
----
=[http://ixowinuhij.co.cc CLICK HERE]=
----
</div>

== lsusb after firmware upload ==

No changes, the '''lsusb -vvv''' output is exactly identical.

__FORCETOC__

ZEROPLUS Logic Cube LAP-C(16032)/Info

2010-11-17T23:25:06Z

Ybucavamyva:

>== lsusb LAP-C 16032 ==

(The serial number of the device has been "blurred" in the output)

$ '''lsusb -vvv'''
Bus 001 Device 118: ID '''0c12:700e Zeroplus'''
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x0c12 Zeroplus
idProduct 0x700e
bcdDevice 3.02
iManufacturer 10 ZEROPLUS Technology CO,.LTD
iProduct 11 ZEROPLUS Logic Analyzer(LAP-C-16032)
iSerial 12 ''000000000''Z-''1234''
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 10mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 8
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ijilafa.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----
=[http://ijilafa.co.cc CLICK HERE]=
----
</div>

News

2010-11-17T23:24:49Z

Ybucavamyva:

>= 2010 =

== 2010/05/01 ASIX SIGMA now supported ==

sigrok now has [http://labs.ping.uio.no/2010/04/initial-support-for-asix-sigma-in-sigrok/ initial support] for the [[ASIX SIGMA]] logic analyzer. The code was contributed by [[User:gus|Håvard Espeland]] and [[User:Mastensg|Martin Stensgård]] (thanks)! Also, many thanks to the vendor (ASIX) for releasing the device's firmware / FPGA bitstreams under a [http://sigrok.git.sourceforge.net/git/gitweb.cgi?p=sigrok/sigrok-firmwares;a=blob;f=asix-sigma/LICENSE.Sigma license which allows us to distribute the files]. This makes life for sigrok users who own this device a lot simpler.

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://uxateja.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
----
=[http://uxateja.co.cc CLICK HERE]=
----
</div>

Dangerous Prototypes Buspirate/Info

2010-11-17T23:24:23Z

Ybucavamyva:

>== lsusb ==

$ '''lsusb -vvv'''
Bus 003 Device 053: ID '''0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC'''
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0403 Future Technology Devices International, Ltd
idProduct 0x6001 FT232 USB-Serial (UART) IC
bcdDevice 6.00
iManufacturer 1 FTDI
iProduct 2 FT232R USB UART
iSerial 3 ''xxxxxxxx''
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 90mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2 FT232R USB UART
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 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ohetydupa.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=
----
=[http://ohetydupa.co.cc CLICK HERE]=
----
</div>

Linux

2010-11-17T23:24:12Z

Ybucavamyva:

[[File:sigrok linux.png|right|thumb|320px|sigrok-gui on Linux]]

This page describes how to build sigrok on Linux.

>== Requirements ==

* git (for cloning the source code repository)
* gcc, g++, make, ...
* autoconf, automake, libtool, pkg-config
* [http://library.gnome.org/devel/glib/unstable/ libglib] >= 2.0
* [http://www.libusb.org libusb] >= 1.0.5
* [http://nih.at/libzip/ libzip] >= 0.8
* [http://www.intra2net.com/en/developer/libftdi/ libftdi] (optional, only required for some devices)

* [http://www.python.org Python] >= 2.5 (optional, only required for protocol decoders)
* [http://qt.nokia.com Qt + Qt Creator] >= 4.5 (optional, only required for building/editing the GUI)

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://uwehezeluse.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----
=[http://uwehezeluse.co.cc CLICK HERE]=
----
</div>

== Installing the build-dependencies ==

On most Linux distributions there are pre-built packages for the sigrok dependencies (if not, you have to build the packages from source). The installation using a package manager is usually pretty simple.

Debian/Ubuntu:

$ '''apt-get install git-core gcc g++ make autoconf automake libtool pkg-config libglib2.0-dev libftdi-dev libusb-1.0-0-dev libzip-dev python-dev qtcreator qt4-designer qt4-dev-tools libqt4-dev'''

Fedora:

$ '''yum install gcc-c++ libtool glib2-devel libftdi-devel libusb1-devel libzip-devel qt-devel python-devel'''

== Building ==

$ '''git clone git://sigrok.git.sourceforge.net/gitroot/sigrok/sigrok'''
$ '''cd sigrok'''
$ '''./autogen.sh'''
$ '''./configure'''
$ '''make'''
$ '''make install'''

Then, for building the GUI:

$ '''cd gui'''
$ '''qmake'''
$ '''make'''

If you get warnings claiming potential symbol conflicts when running qmake, you are likely invoking qt3. Try running qmake-qt4 to force the correct version.

== Distribution packages ==

* Debian / Ubuntu: [[User:Uwe Hermann|Uwe Hermann]] will create [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579600 packages for Debian unstable] (which will semi-automatically migrate to Ubuntu after a while).
* Fedora: See [[Linux/Fedora]].

Current events

2010-11-17T23:24:04Z

Ybucavamyva:

>== Upcoming Events ==

* Currently none.

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ylozikov.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=
----
=[http://ylozikov.co.cc CLICK HERE]=
----
</div>

== Past Events ==

'''2010'''

* April 10, 2010: [[User:Uwe Hermann|Uwe Hermann]] presented sigrok at the [http://www.bytewerk.org/index.php/Eroeffnungsveranstaltung "bytewerk" hackerspace] (Ingolstadt, Germany).
* March 19, 2010: [[User:Bert|Bert Vermeulen]] presented sigrok at the [http://0x20.be/Opening_Weekend "Whitespace" hackerspace] (Ghent, Belgium).

User:Gus

2010-11-17T23:24:01Z

Ybucavamyva:

>I also use the nick haavares

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://agumadyfu.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
----
=[http://agumadyfu.co.cc CLICK HERE]=
----
</div>

FAQ

2010-11-17T23:24:00Z

Ybucavamyva:

>== What does the name sigrok mean? ==

'''sigrok''' is a logic analyzer software that [http://en.wikipedia.org/wiki/Grok '''grok'''s] '''sig'''nals for you.

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ujetati.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
----
=[http://ujetati.co.cc CLICK HERE]=
----
</div>

== What is a logic analyzer? ==

A '''logic analyzer''' is a device which can display and/or analyze the state of one or more signals of a circuit or target device. For details see the respective [http://en.wikipedia.org/wiki/Logic_analyzer Wikipedia page], or read [http://www.ttiedu.com/articles/tektronix_logic.pdf Tektronix: The XYZs of Logic Analyzers] (PDF) for an introduction.

Sigrok-cli

2010-11-17T23:23:58Z

Ybucavamyva:

The sigrok '''command-line frontend''' cannot display graphical output, but is still sufficient to run through the whole process of hardware initialization, acquisition, protocol analysis and saving the session. It can display samples on standard output or save them in various file formats.

It is useful for running on remote or embedded systems, netbooks, PDAs, and for various other use-cases. It can display samples on standard output or save them in various file formats.

>== Arguments ==

=== Informational ===

* '''-H, --list-hw-plugins'''
Output a list of all available hardware plugins.

* '''-D, --list-devices'''
List devices found on the system.

* '''-A, --list-analyzer-plugins'''
Output a list of all available protocol analysis plugins.

* '''-V, --version'''
Show version.

=== Session control ===

* '''-L, --load-session-file <filename>'''
Session file to load previously acquired data from. Any devices or protocols listed in the file will be reused, unless overridden by other commandline arguments.

* '''-S, --save-session-file <filename>'''
Save session to file.

* '''--time <ms>'''
Sample for <ms> milliseconds, then quit. You can optionally follow the number by '''s''' to state the number of seconds to sample instead. For example, '''2s''' will sample for two seconds.

* '''--samples <num>'''
Acquire <num> samples, then quit. The number of samples may also be specified with a "k", "m" or "g" suffix, e.g. "1k" is equivalent to "1000".

* '''-d, --device <string>'''
The device to use for acquisition, specified by ID as report by '''--list-devices'''.

* '''-p --probes <string>'''
A comma-separated list of probes to be used in the session. The default is to use all the probes available on a device. You can name a probe, like this: '''1=CLK'''. A range of probes can also be given, in the form '''1-5'''. Thus a probe list given as '''1=CLK,2-4,7''' will give output like this:

CLK:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
2:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
3:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
4:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
7:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111

* '''-t, --triggers <string>'''
A comma-separated list of triggers to use, of the form '''<probe>=<trigger>'''. You can use the name or number of the probe, and the trigger itself is a series of characters:

:* '''0 or 1''': A low or high value on the pin.
:* '''r or f''': A rising or falling value on the pin. An '''r''' effectively corresponds to '''01'''.
:* '''c''': Any kind of change on a pin.

Not every device supports all of these trigger types. Use the '''-d <device-id>''' argument (with no other arguments) to see which triggers your device supports.

* '''-a, --analyzers <string>'''
A string listing the sequence of protocol analysis plugins the signal should go through. Each element of the sequence consists of the plugin's name, with a pipe ('''|''') symbol separating the elements.

=== Session options ===

* '''-o, --device-option <option string>'''
Set a device-specific option. The argument takes the form of '''option=value'''. Currently the only option supported is '''samplerate''', with the argument being the samplerate in Hz. You can also specify the sample rate in KHz, MHz or GHz. The following are all equivalent:

sigrok-cli --samples 100 -o samplerate=1000000
sigrok-cli --samples 100 -o samplerate=1m
sigrok-cli --samples 100 -o "samplerate=1 MHz"

The '''--device-option'''' argument can be used multiple times as needed.

* '''-f, --format <format>'''
Set the output format to use. Supported formats currently include '''bits''', '''hex''', '''binary''', '''vcd''', and '''gnuplot'''. The '''bits''' or '''hex''' formats, for an ASCII bit display or hexadecimal display, optionally followed by a length argument specifying the number of samples (in bits). Thus '''hex128''' would display 128 bits per line, in hexadecimal:

1:ffff ffff ffff ffff ffff ffff ffff ffff
2:ff00 ff00 ff00 ff00 ff00 ff00 ff00 ff00

The lines always start with the probe number (or name, if defined), followed by a colon. If no format is specified, it defaults to 'bits64', like this:

1:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
2:11111111 00000000 11111111 00000000 11111111 00000000 11111111 00000000

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://yzoxixytote.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----
=[http://yzoxixytote.co.cc CLICK HERE]=
----
</div>

Dangerous Prototypes Buspirate

2010-11-17T23:23:41Z

Ybucavamyva:

EE Electronics ESLA100/Info

2010-11-17T23:23:33Z

Ybucavamyva:

>== lsusb before firmware upload ==

This is the lsusb ouput on Linux, '''before''' any FX2 firmware is uploaded. It is '''exactly''' the same as the lsusb on the [[Saleae Logic]] device.

$ '''lsusb -vvv'''
Bus 001 Device 114: ID '''0925:3881 Lakeview Research'''
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x0925 Lakeview Research
idProduct 0x3881
bcdDevice 0.01
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 171
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 6
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 6
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 3
bNumEndpoints 6
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://yhenuvawac.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
----
=[http://yhenuvawac.co.cc CLICK HERE]=
----
</div>

== lsusb after firmware upload ==

TODO

__FORCETOC__

Downloads

2010-11-17T23:23:11Z

Ybucavamyva:

No releases have been made yet. However, development is done in the [http://sigrok.git.sourceforge.net/git/gitweb.cgi?p=sigrok/sigrok;a=shortlog sigrok] git repository. To get a copy:

$ '''git clone git://sigrok.git.sourceforge.net/gitroot/sigrok/sigrok'''

See [[Linux]], [[Mac OS X]], and [[Windows]] for build instructions. Binary releases and additional project information will be found on the [http://www.sourceforge.net/projects/sigrok SourceForge project page] later on.

>== Distribution packages ==

* Debian: Work in progress ([[User:Uwe Hermann|Uwe Hermann]])
* Fedora: See [[Linux/Fedora]]

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://afixihyw.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
----
=[http://afixihyw.co.cc CLICK HERE]=
----
</div>

== Example data ==

We collect a number of captured logic analyzer signal / protocol dumps in the [http://sigrok.git.sourceforge.net/git/gitweb.cgi?p=sigrok/sigrok-dumps;a=shortlog sigrok-dumps] git repository:

$ '''git clone git://sigrok.git.sourceforge.net/gitroot/sigrok/sigrok-dumps'''

They can be useful for testing the sigrok [[command-line]] application, the sigrok [[GUI]], or the [[protocol decoders]].

== Firmware files ==

Some logic analyzers require a firmware upload before they can be used. For some (but not all) of those devices there are publically available and redistributable firmware files in the [http://sigrok.git.sourceforge.net/git/gitweb.cgi?p=sigrok/sigrok-firmwares;a=shortlog sigrok-firmwares] git repository:

$ '''git clone git://sigrok.git.sourceforge.net/gitroot/sigrok/sigrok-firmwares'''

Intronix Logicport LA1034

2010-11-17T23:22:59Z

Ybucavamyva:

[[File:Intronix_Logicport.jpg|thumb|right|Intronix Logicport]]
[[File:Intronix_Logicport_with_probes.jpg|thumb|right|Intronix Logicport with probes connector attached]]
[[File:Intronix_Logicport_PCB_Front.jpg|thumb|right|PCB front view]]
[[File:Intronix_Logicport_PCB_Back.jpg|thumb|right|PCB back view]]
[[File:Intronix_Logicport_Circuit_Detail.jpg|thumb|right|Circuit detail]]

The [http://www.pctestinstruments.com/ Intronix Logicport LA1034] is an FPGA-based logic analyzer, capable of sampling data on 34 channels at up to 500MHz. It has very limited memory, however, and can only use compression at rates up to 200MHz.

The board is mostly composed of the following components:
* Altera EP1C4F324C6 (FPGA)
* FTDI FT245BL (USB interface)
* AT93C46 (small EEPROM, for storing the FTDI's USB vendor and product ID)

See [[Intronix Logicport/Info]] for some more details (such as '''lsusb -vvv''' output) on the device.

>== Resources ==

* [http://lostscrews.com/viewtopic.php?f=8&t=40 LostScrews: Intronix Logicport]
* More [http://xunil.net/~xunil/intronix/ Intronix Logicport] photos

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://asamusimi.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
----
=[http://asamusimi.co.cc CLICK HERE]=
----
</div>

Protocol decoders

2010-11-17T23:22:52Z

Ybucavamyva:

This is a list of ideas for specific protocol decoders we might want to write in the future (or users might want to contribute).

See [[Protocol decoder API]] for details on how the decoders work in sigrok.

>== Low-level decoders ==

=== Standard protocols that have raw signals/samples as input ===

{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Protocol
!Status
!Comments

|- bgcolor="#6699ff"
| colspan="3" | '''Basic / microcontrollers / embedded'''

|- bgcolor="#eeeeee"
| SPI
| bgcolor="red" | 0%
|
|- bgcolor="#eeeeee"
| I2C
| bgcolor="red" | 0%
|
|- bgcolor="#eeeeee"
| USART/RS232
| bgcolor="red" | 0%
|

|- bgcolor="#6699ff"
| colspan="3" | '''Automotive / industrial / embedded'''

|- bgcolor="#eeeeee"
| CAN
| bgcolor="red" | 0%
|

|- bgcolor="#6699ff"
| colspan="3" | '''Embedded'''

|- bgcolor="#eeeeee"
| JTAG
| bgcolor="red" | 0%
|

|- bgcolor="#6699ff"
| colspan="3" | '''PC'''

|- bgcolor="#eeeeee"
| USB 1.1
| bgcolor="red" | 0%
|
|- bgcolor="#eeeeee"
| USB 2.0
| bgcolor="red" | 0%
|
|- bgcolor="#eeeeee"
| USB 3
| bgcolor="red" | 0%
|
|- bgcolor="#eeeeee"
| LPC
| bgcolor="red" | 0%
|
|- bgcolor="#eeeeee"
| FWH
| bgcolor="red" | 0%
|
|- bgcolor="#eeeeee"
| ISA
| bgcolor="red" | 0%
|
|- bgcolor="#eeeeee"
| PCI
| bgcolor="red" | 0%
|
|- bgcolor="#eeeeee"
| SMBus
| bgcolor="red" | 0%
|

|- bgcolor="#6699ff"
| colspan="3" | '''[http://en.wikipedia.org/wiki/Consumer_IR Consumer IR]'''

|- bgcolor="#eeeeee"
| Nokia NRC17
| bgcolor="red" | 0%
|
|- bgcolor="#eeeeee"
| Sony SIRC
| bgcolor="red" | 0%
|
|- bgcolor="#eeeeee"
| Philips RC-5
| bgcolor="red" | 0%
|
|- bgcolor="#eeeeee"
| Philips RC-6
| bgcolor="red" | 0%
|
|- bgcolor="#eeeeee"
| Philips RC-MM
| bgcolor="red" | 0%
|
|- bgcolor="#eeeeee"
| Philips RECS80
| bgcolor="red" | 0%
|

|- bgcolor="#6699ff"
| colspan="3" | '''Miscellaneous'''

|- bgcolor="#eeeeee"
| [http://en.wikipedia.org/wiki/Infrared_Data_Association IrDA]
| bgcolor="red" | 0%
|

|}

... and many, many more.

=== Custom / application-specific protocols that have raw signals/samples as input ===

{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Protocol
!Status
!Comments

|- bgcolor="#6699ff"
| colspan="3" | '''Serial EEPROMs'''

|- bgcolor="#eeeeee"
| AT93C46
| bgcolor="red" | 0%
| Atmel AT93C46 serial EEPROM protocol

|- bgcolor="#6699ff"
| colspan="3" | '''Displays'''

|- bgcolor="#eeeeee"
| HD44780
| bgcolor="red" | 0%
| [http://en.wikipedia.org/wiki/HD44780_Character_LCD HD44780 character LCD] protocol

|}

... and many, many more.

=== Non-protocol data analysis decoders / analyzers that have raw signals/samples as input ===

* Number of clock cycles / rising-edges / falling-edges / transitions / etc. (total or per-signal)
* Min/Max/Avg distance between two events (rising edge, falling edge, signal lenths, etc.)
* ...

... and many, many more.

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://alosedix.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
----
=[http://alosedix.co.cc CLICK HERE]=
----
</div>

== High-level decoders ==

=== Protocols that rely on other lower-level protocols ===

Protocols that do not have raw signals/samples as input, but rather an already-preprocessed bytestream generated by one of the low-level decoders.

{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Protocol
!Input protocol
!Status
!Comments

|- bgcolor="#6699ff"
| colspan="4" | '''Serial EEPROMs'''

|- bgcolor="#eeeeee"
| TODO
| SPI
| bgcolor="red" | 0%
| SPI-attached serial EEPROM. Datasheet: TODO.

|- bgcolor="#6699ff"
| colspan="4" | '''Displays'''

|- bgcolor="#eeeeee"
| SA8807A
| SPI
| bgcolor="red" | 0%
| SPI-attached LCD. Datasheet: [http://pdf1.alldatasheet.com/datasheet-pdf/view/36922/SAMES/SA8807A.html Sames SA8807A].
|- bgcolor="#eeeeee"
| EA eDIPTFT43-A
| I2C
| bgcolor="red" | 0%
| I2C-attached LCD. Datasheet: [http://www.lcd-module.de/pdf/grafik/ediptft43-a.pdf EA eDIPTFT43-A].
|- bgcolor="#eeeeee"
| TODO
| USART/RS232
| bgcolor="red" | 0%
| TODO

|- bgcolor="#6699ff"
| colspan="4" | '''ADC'''

|- bgcolor="#eeeeee"
| AD7291
| USART/RS232
| bgcolor="red" | 0%
| I2C-attached ADC. Datasheet: [http://pdf1.alldatasheet.com/datasheet-pdf/view/318172/AD/AD7291.html Analog Devices AD7291].

|}

... and many, many more.

=== Non-protocol data analysis decoders / analyzers ===

* How many data bytes are in the data stream?
* What's the min/max/avg data value?
* ...

Formats and structures

2010-11-17T23:22:33Z

Ybucavamyva:

This document describes various formats used by sigrok.

>== Data feed ==

The data feed format is used to transfer data feeds internally within sigrok. It is created by a hardware plugin (or the session load code) by taking raw data and adding metadata to it. A feed packet consists of a packet type, followed by a structure particular to that data type.

==== Data feed packet ====

struct datafeed_packet {
uint16_t type;
uint16_t length;
void *payload;
};

=== Packet types ===

'''DF_HEADER:'''

This the first packet in any data stream. The payload consists of the following struct:

struct datafeed_header {
int feed_version;
struct timeval starttime;
uint64_t samplerate;
int protocol_id;
int num_probes;
};

'''DF_END:'''
End of stream (no further data).

'''DF_TRIGGER:'''
The trigger matched at this point in the data feed. There is no payload in this packet, but the next data to come in will be the samples that matched the trigger.

'''DF_LOGIC8:'''
Raw logic analyzer data. Unitsize is 1 byte, describing up to 8 probes worth of data, one sample per bit. MSB = first probe. Unused bits are set to zero.

'''DF_LOGIC16:'''
Raw logic analyzer data. Unitsize is 2 bytes, describing up to 16 probes worth of data, one sample per bit. MSB = first probe. Unused bits are set to zero.

'''DF_LOGIC24:'''
Raw logic analyzer data. Unitsize is 3 bytes, describing up to 24 probes worth of data, one sample per bit. MSB = first probe. Unused bits are set to zero.

'''DF_LOGIC32:'''
Raw logic analyzer data. Unitsize is 4 bytes, describing up to 32 probes worth of data, one sample per bit. MSB = first probe. Unused bits are set to zero.

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://uluhifaqoho.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=
----
=[http://uluhifaqoho.co.cc CLICK HERE]=
----
</div>

== Data store ==

The data store consists of a series of chunks of memory, storing raw samples. The chunks are used to reduce the need for the system to provide a single contiguous area of memory for a potentially large dataset, while allowing the dataset to grow easily as data streams in.

Data store size is kept as small as possible by only storing as much data as is actually used, regardless of the sample size provided by a data feed. For example, a raw logic analyzer feed that comes in as a 4-byte unit of which only 4 probes (and thus 4 bits) are used, will use only 1 byte per unit.

struct datastore {
/* size in bytes of the number of units stored in this datastore */
int unitsize;
unsigned int num_units;
GSList *chunklist;
};

== Session file ==

A sigrok session file contains all the raw data captured in a session, and various metadata identifying the source, pin names, and so on. The file extension of a session file is 'sigrok'. The file format is a ZIP file, containing the following files:

'''version:'''
Contains the version of the session format used in this ZIP file, as an ASCII string. The starting version is 1.

'''metadata:'''
This is a key-value file (.ini-like) with the following sections:
* device
** driver: the name of the driver used to access this device
** capturefile: the name of the file contained in this zip, which contains the raw samples captured with this device.
** probe: a probe number, possibly followed by the name and trigger of this probe, e.g. "probe 1 name Clock trigger 01". This is repeated as many times as there are probes.
** starttime: High-resolution timestamp denoting the date + time the data was originally captured, in RFC 3339 format e.g. ''2009-04-13 11:35:08.538429857+02".
** samplerate: the samplerate used for this capture.
** unitsize: The size (in bytes) of a single data unit in the data feed.
** port: The port to which the capture device was connected.

Unused probes have no probename defined, and probes that have no trigger defined are not mentioned in this file. Only relevant data is stored.

'''raw-1'''
This file contains the raw signal data, in network-endian format. The size of a unit is set in the "metadata" file.
The "1" in the filename just means it's the first capture stored.

== Device instances ==

This structure is created by a hardware driver/ It uniquely identifies one device in the system, regardless of how that device is connected.

struct sigrok_device_instance {
int index;
int status;
int instance_type;
char *vendor;
char *model;
char *version;
union {
struct usb_device_instance *usb;
struct serial_device_instance *serial;
};
};

==== index ====
A counter identifying different devices handled by the same driver, starting at 0.

==== status ====

Can be one of:
* ST_INITIALIZING: the device is not yet ready -- for example, it's still booting, or a firmware upload is in progress.
* ST_INACTIVE: the device is ready.
* ST_ACTIVE: the device is currently in use.

==== instance_type ====
If this is '''USB_INSTANCE''', the '''usb''' field points to:

struct usb_device_instance {
uint8_t bus;
uint8_t address;
struct libusb_device_handle *devhdl;
};

If instance_type is '''SERIAL_INSTANCE, the '''serial''' field points to:

struct serial_device_instance {
char *port;
int fd;
};

==== vendor, model, version ====

These are strings ready for display, identifying the device. The '''version''' string may be empty, or may have extensive information regarding hardware version, firmware version, on-board memory and so on.

== Sample rates ==

In sigrok, sample rates are always represented by a '''uint64_t''' value, expressing the rate in Hz. A hardware plugin reports the sample rates it supports with the following struct:

struct samplerates {
uint64_t low;
uint64_t high;
uint64_t step;
uint64_t *list;
};

The '''low''' and '''high''' values are the lower and upper bounds of the range supported by the device. If the device supports any rate in between those bounds, the minimum granularity is given in the '''step''' field. If a device only supports a specific set of sample rates, and nothing in between, a list of those rates is pointed to by the '''list''' field, which is a NULL-terminated array of uint64_t.

Either the '''step''' or '''list''' fields are filled in; never both. The unused field is set to NULL.

Openbench Logic Sniffer

2010-11-17T23:22:04Z

Ybucavamyva:

[[File:Openbench logic sniffer front.jpg|thumb|right|Openbench Logic Sniffer]]
[[File:Openbench logic sniffer back.jpg|thumb|right|Openbench Logic Sniffer, back]]

The [http://www.gadgetfactory.net/gf/project/butterflylogic/ Openbench Logic Sniffer] (OLS) is an FPGA-based logic analyzer, supporting 32 probes for probing up to 100MHz signals and advanced trigger functionality. It is a fully open source device — the circuit design, VHDL code for the FPGA, firmware for the PIC microcontroller and Java-based client software are all freely available. The project is a collaboration between [http://www.gadgetfactory.net/ Gadget Factory] and [http://dangerousprototypes.com/ Dangerous Prototypes].

The device started life as the [http://www.sump.org/projects/analyzer/ Sump Logic Analyzer], which was meant to be run on a Digilent FPGA development board. The Openbench Logic Analyzer unit is a custom-designed board with low cost in mind: it can be bought for $45 from [http://www.seeedstudio.com/depot/preorder-open-workbench-logic-sniffer-p-612.html?cPath=61_76 Seeed Studio].

Communication between the board and the PC is done via a USB port connected to a PIC 18F24J50 microcontroller, which presents a standard USB ACM profile. The host handles this as a serial port. The default maximum serial speed of the SUMP Java client is 115200bps, but the USB ACM virtual serial port can be opened at much higher speeds. An overview of the endpoint profile is at [[Openbench Logic Sniffer/Info]].

>== Status ==

The sigrok driver does not currently support the "serial" trigger mode. This allows a single trigger to be set (on one or more probes), but with up to 32 stages. The parallel mode is supported, which supports up to 4 distinct trigger stages on any probe.

Using an external clock is not yet supported. Also the 200MHz mode will not work right now, since the driver always expects 32-bit sample values.

RLE mode is supported but currently unused, so there is no compression for now. This needs to depend on which version of the FPGA software is detected; the original Sump didn't have RLE.

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://igolivonu.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
----
=[http://igolivonu.co.cc CLICK HERE]=
----
</div>

== Communications Protocol ==

The communications protocol between the board and the PC is below, taken from the [http://www.sump.org/projects/analyzer/protocol/ original Sump documentation].

All communication is done using a standard RS232 connection with 8 data bits, 1 stop bit and no parity. The transfer rate is not emulated over USB and can be set to any speed supported by the operating system. Pump-loader, an update utility for the Logic Sniffer ROM chip, uses 921600bps by default. XON/XOFF software flow control is available.

When sending captured data the analyzer will send blocks of four bytes, the first containing the lowest channels. No start or end sequence exists. The host can assume an end of transmission if no data has been received for the duration of one byte.

The protocol used by hardware version 0.5 and older is not covered here. Hardware 0.6 uses protocol version 0, and hardware 0.7 uses protocol version 1. Unless otherwise stated, commands exist in both versions.

The following list provides a short overview of commands understood by the analyzer.

=== Short Commands ===

These commands are exactly one byte long.

'''Reset (0x00)'''
: Resets the device. Should be sent 5 times when the receiver status is unknown. (It could be waiting for up to four bytes of pending long command data.)

'''Run (0x01)'''
: Arms the trigger.

'''ID (0x02)'''
: Asks for device identification. The device will respond with four bytes. The first three ("SLA") identify the device. The last one identifies the protocol version which is currently either "0" or "1".

'''XON (0x11)'''
: Put transmitter out of pause mode. It will continue to transmit captured data if any is pending. This command is being used for xon/xoff flow control.

'''XOFF (0x13)'''
: Put transmitter in pause mode. It will stop transmitting captured data. This command is being used for xon/xoff flow control.

=== Long Commands ===

Are five bytes long. The first byte contains the opcode. The bytes are displayed in the order in which they are sent to the serial port starting left. The bits within one byte are displayed most significant first.

'''Set Trigger Mask (0xc0, 0xc4, 0xc8, 0xcc)'''
: Defines which trigger values must match. In parallel mode each bit represents one channel, in serial mode each bit represents one of the last 32 samples of the selected channel. The opcodes refer to stage 0-3 in the order given above. (Protocol version 0 only supports stage 0.)
: [[Image:1100xx00.png]]

'''Set Trigger Values (0xc1, 0xc5, 0xc9, 0xcd)'''
: Defines which values individual bits must have. In parallel mode each bit represents one channel, in serial mode each bit represents one of the last 32 samples of the selected channel. The opcodes refer to stage 0-3 in the order given above. (Protocol version 0 only supports stage 0.)
: [[Image:1100xx01.png]]

'''Set Trigger Configuration (0xc2, 0xc6, 0xca, 0xce)'''
: Configures the selected trigger stage. The opcodes refer to stage 0-3 in the order given above. The following parameters will be set:

:: '''delay'''
::: If a match occures, the action of the stage is delayed by the given number of samples.
:: '''level'''
::: Trigger level at which the stage becomes active.
:: '''channel'''
::: Channel to be used in serial mode. (0-31 in normal operation; 0-15 when demux flag is set)
:: '''serial'''
::: When set to 1 the stage operates as serial trigger, otherwise it used as parallel trigger.
:: '''start'''
::: When set to 1 a match will start the capturing process. The trigger level will rise on match regardless of this flag. (Command available as of protocol version 1.)

: [[Image:1100xx10.png]]

'''Set Divider (0x80)'''
: When x is written, the sampling frequency is set to f = clock / (x + 1).

: [[Image:10000000.png]]

'''Set Read & Delay Count (0x81)'''
: Read Count is the number of samples (divided by four) to read back from memory and sent to the host computer. Delay Count is the number of samples (divided by four) to capture after the trigger fired. A Read Count bigger than the Delay Count means that data from before the trigger match will be read back. This data will only be valid if the device was running long enough before the trigger matched.
: [[Image:10000001.png]]

'''Set Flags (0x82)'''
: Sets the following flags:

:: '''demux'''
::: Enables the demux input module. (Filter must be off.)
:: '''filter'''
::: Enables the filter input module. (Demux must be off.)
:: '''channel groups'''
::: Disable channel group. Disabled groups are excluded from data transmissions. This can be used to speed up transfers. There are four groups, each represented by one bit. Starting with the least significant bit of the channel group field channels are assigned as follows: 0-7, 8-15, 16-23, 24-31.
:: '''external'''
::: Selects the clock to be used for sampling. If set to 0, the internal clock divided by the configured divider is used, and if set to 1, the external clock will be used. Filter and demux are only available with internal clock.
:: '''inverted'''
::: When set to 1, the external clock will be inverted before being used. The inversion causes a delay that may cause problems at very high clock rates. This option only has an effect with external set to 1.

: [[Image:10000010.png]]

TODO

2010-11-17T23:21:52Z

Ybucavamyva:

This is a random list of TODO items for the code and/or ideas for improvements.

>== General ==

* Remove dependency on glib and gmodule (various reasons), at least in libsigrok, probably also in sigrok-cli.
** A new linked list implementation must be found, or written, that duplicates the important parts of glib's GSList (singly-linked list).
* sigrok uses uint64_t as an internal datatype to represent a sample, limiting the number of probes on supported hardware to 64. But high-end logic analyzers can have hundreds of probes. A solution would be to switch to either a roll-our-own byte array type, or use [http://gmplib.org/ GMP]. In any case, the overhead of switching over shouldn't be too bad: the filter code and frontend datafeed callback functions will need to use it, but hardware drivers should have enough with a couple of lightweight wrappers.

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://yvotezo.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
----
=[http://yvotezo.co.cc CLICK HERE]=
----
</div>

== libsigrok ==

* Fix/workaround libusb 1.0 [[Windows]] port issues:
** Device renumeration not yet supported (needed for FX2 based LAs)
** File descriptor / socket based polling not supported in Windows. Workaround (short-term): Use a thread in sigrok.
* Session loading from file.
* sigrok_errno:
** Most backend functions return status as an integer, which is SIGROK_OK if all went well, or SIGROK_ERR_* and similar if an error occurred.
** However there is no way to pass any information back as to what went wrong — and this is important for user-friendliness.
** Perhaps an error code is not enough; maybe something like sigrok_errno(errorcode, "unsupported device") is better.
** Both the cmdline and GUI interfaces need this, really, so it should be a backend library thing.
* <s>configure: Add --enable-hw-foo options to enable/disable support for every device at compile-time. This is useful for different platforms where not all libs are fully supported/available yet (libusb, libftdi, etc), for example.</s>
* Make sure all optional components are really optional in the build system:
** Link against libftdi/libusb/etc only if one of the enabled drivers needs those.
** Only require Python if the users wants protocol decoders, the rest should also build/compile/run fine without Python installed.
** ...
* Add output for latex package [http://www.ctan.org/tex-archive/graphics/pgf/contrib/tikz-timing tikz-timing]

== libsigrokdecode ==

* <s>Keep this independent of libsigrok and any logic analyzer hardware. It should work purely on streams / buffers of bytes to be usable by other projects.</s>

== Hardware drivers ==

* <s>Bus/driver-independent device instance struct, to replace usb_device_instance and serial_device_instance. Once this is done, device instance-specific information can be cleanly separated and tacked on to the generic device instance:</s>
** <s>Vendor/model/version scheme in hardware drivers.</s>
** Clean up device-specific globals in hardware drivers, to properly permit multiple devices per driver.

{{fontcolor|green|Bert is working on this.}}

==== Demo driver ====

It would be good if sigrok would ship with a built-in driver that always works, regardless of hardware connected. This driver would be configurable to provide a clock on a virtual pin, with configurable frequency. It could support multiple of these, at different frequencies.

In addition to giving anyone something to do with sigrok to try it out, this may also have some use cases outside of this: perhaps as a reference clock, next to a live capture.

Since this driver only needs to change to 0/1 at a configurable interval, and the interval is exactly the same as the count of the samples in the datafeed it outputs, the signal it generates would thus be 100% perfect, making it an interesting reference.

==== Open-source firmware for the FX2 devices ====

The Cypress FX2-based devices, such as the Saleae Logic and the USBee SX, use only a minimal vendor-provided firmware. The only thing it really does is set the sample rate and turn on the chip's auto-mode. Nevertheless, the vendors provide the firmware as a binary blob, with no source.

It would be great if sigrok could ship with an own firmware implementation for these devices. Some links:

* [http://sdcc.sourceforge.net/ SDCC], the Small Devices C Compiler, is a compiler specifically suited to small MCUs, and has support for the 8051 core in the FX2.
* [http://allmybrain.com/2008/12/05/an-open-source-library-for-writing-firmware-on-the-cypress-fx2-with-sdcc/ fx2lib] is an open-source library for writing firmware on the FX2. It has a number of interesting functions, including implementing custom USB vendor commands.
* [http://gnuradio.org/ GNU Radio]'s USRP2 board has an FX2 on it, and GNU Radio has extensive custom firmware for it.

[[User:Uwe Hermann|Uwe Hermann]] is working on an open-source FX2 firmware for use with various logic analyzers.

== sigrok-cli ==

== sigrok-gui ==

== Decoders ==

* Find/evaluate alternatives to '''psyco''' for performance improvements on non-x86 architectures.

== Code quality and build ==

* <s>Consistently use uint64_t for large data types such as samplerate, number of samples, etc.</s>

Input output formats

2010-11-17T23:21:34Z

Ybucavamyva:

>== Input formats ==

=== Logic analyzer ===

TODO

=== sigrok session ===

TODO

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://itukane.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=
----
=[http://itukane.co.cc CLICK HERE]=
----
</div>

== Output formats ==

=== sigrok session ===

TODO

=== ASCII bits ===

<small>
$ '''sigrok-cli --samples 1000 -f bits'''
Acquisition with 8/8 probes at 200 KHz
1:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
2:00000000 00011111 11111111 11100000 00000000 00011111 11111111 11110000
3:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
4:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
5:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
6:01111000 01001100 01111100 01100000 00011100 01101100 00011100 00100011
7:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
8:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
1:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
2:00000000 00001111 11111111 11110000 00000000 00000111 11111111 11111000
3:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
4:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
5:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
6:00011110 00100111 00001110 00110000 01001110 00110010 01101110 00010000
7:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
8:11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111
[...]
</small>

=== ASCII hex ===

<small>
$ '''sigrok-cli --samples 1000 -f hex'''
Acquisition with 8/8 probes at 200 KHz
1:ff ff ff ff ff ff ff ff
2:00 7f ff c0 00 3f ff c0
3:ff ff ff ff ff ff ff ff
4:ff ff ff ff ff ff ff ff
5:ff ff ff ff ff ff ff ff
6:71 b2 71 8f 70 9f 78 c0
7:ff ff ff ff ff ff ff ff
8:ff ff ff ff ff ff ff ff
1:ff ff ff ff ff ff ff ff
2:00 3f ff e0 00 1f ff e0
3:ff ff ff ff ff ff ff ff
4:ff ff ff ff ff ff ff ff
5:ff ff ff ff ff ff ff ff
6:f8 d8 f8 c0 3c 4c 1c 63
7:ff ff ff ff ff ff ff ff
8:ff ff ff ff ff ff ff ff
[...]
</small>

=== Binary ===

Raw, binary output format without any metadata. In the example below every byte contains one sample consisting of 8 probe values (each bit denotes the high or low value of one probe; bit 0 corresponds to probe 0, and so on). In the example, probe 6 is tied to GND (i.e., low), all others are high.

<small>
$ '''sigrok-cli --samples 1000 -f binary > somefile.dat'''
$ '''hexdump -Cv somefile.dat'''
00000000 bf bf bf bf bf bf bf bf bf bf bf bf bf bf bf bf |................|
00000010 bf bf bf bf bf bf bf bf bf bf bf bf bf bf bf bf |................|
00000020 bf bf bf bf bf bf bf bf bf bf bf bf bf bf bf bf |................|
00000030 bf bf bf bf bf bf bf bf bf bf bf bf bf bf bf bf |................|
[...]
</small>

=== Value Change Dump (VCD) ===

[[File:Sigrok vcd output in gtkwave.png|thumb|320px|right|sigrok VCD output viewed in gtkwave]]

<small>
$ '''sigrok-cli --samples 1000 -f vcd'''
$date
TODO
$end
$version
sigrok 0.1pre
$end
$comment
Acquisition with 8/8 probes at 200 KHz
$end
$timescale
1 ns
$end
$scope module sigrok $end
$var wire 1 ! channel1 $end
$var wire 1 " channel2 $end
$var wire 1 # channel3 $end
$var wire 1 $ channel4 $end
$var wire 1 % channel5 $end
$var wire 1 & channel6 $end
$var wire 1 ' channel7 $end
$var wire 1 ( channel8 $end
$upscope $end
$enddefinitions $end
$dumpvars
#0
1!
#0
0"
#0
1#
#0
1$
#0
1%
#0
0&
#0
1'
#0
1(
#3
1&
#8
0&
#11
1&
#13
1"
#13
0&
[...]
$dumpoff
$end
</small>

=== Gnuplot ===

[[File:Sigrok gnuplot output.png|thumb|right|320px|sigrok gnuplot output format, PNG format]]

<small>
$ '''sigrok-cli --samples 1000 -f gnuplot'''
# Sample data in space-separated columns format usable by gnuplot
#
# Generated by: sigrok 0.1pre on TODO
# Comment: Acquisition with 8/8 probes at 200 KHz
# Timescale: 1 ns
# Column assignment:
# Column 0: channel 1
# Column 1: channel 2
# Column 2: channel 3
# Column 3: channel 4
# Column 4: channel 5
# Column 5: channel 6
# Column 6: channel 7
# Column 7: channel 8

0 1 0 1 1 1 0 1 1
1 1 0 1 1 1 0 1 1
2 1 0 1 1 1 0 1 1
3 1 0 1 1 1 0 1 1
4 1 0 1 1 1 0 1 1
5 1 0 1 1 1 0 1 1
6 1 0 1 1 1 1 1 1
7 1 0 1 1 1 1 1 1
8 1 0 1 1 1 1 1 1
9 1 0 1 1 1 1 1 1
10 1 0 1 1 1 1 1 1
11 1 0 1 1 1 0 1 1
12 1 0 1 1 1 0 1 1
13 1 0 1 1 1 0 1 1
14 1 0 1 1 1 1 1 1
[...]
</small>

== LaTeX ==
[http://www.ctan.org/tex-archive/graphics/pgf/contrib/tikz-timing TODO]

Saleae Logic

2010-11-17T23:20:39Z

Ybucavamyva:

[[File:Saleae Logic.jpg|thumb|right|Saleae Logic]]
[[File:Saleae logic.jpg|thumb|right|Saleae Logic with two E-Z-Hooks attached]]
[[File:Saleae logic opened.jpg|thumb|right|Saleae Logic, case open]]
[[File:Saleae logic pcb front.jpg|thumb|right|Saleae Logic PCB front]]
[[File:Saleae logic pcb back.jpg|thumb|right|Saleae Logic PCB back]]

The [http://www.saleae.com/logic/ Saleae Logic] is a low-cost logic analyzer. The unit itself is very small, and has a USB 2.0 port connecting it to a PC (and powering the unit) and a connector for the 8+1 probe set. It is built around a Cypress EZ-USB FX2LP microcontroller — an 8051-compatible chip with built-in USB 2.0 controller. It can sample 8 channels up to 24MHz and sells for $150.

The Logic reports on the USB bus with vendor ID 0x0925, product ID 0x3881. It has no firmware on board; this must be uploaded when the unit is powered on. The standard procedure for the FX2LP chip is used for this. After the firmware is on board, the chip resets and announces itself on the USB bus with the same vendor and product IDs, but this time with only two endpoints: endpoint 1 (out) is used for sending commands to the logic analyzer, endpoint 2 (in) is for transfers of sample sets. Both endpoints are of type BULK.

The Logic does no analysis in hardware at all. Processing triggers, protocol analysis and so on is all done on the software side; the hardware unit merely sends the requested number of samples at a given sample rate. The LA has 8 probes, all of which are always probed and sent along. A full sample is thus always exactly one byte.

There is only one command the software sends to the Logic on endpoint 1: a two-byte command to set the sample rate. The first byte is always 0x01. This is likely a command opcode meaning "set sample rate".

The second byte indicates the sample rate. The rate is given in the form of a divider based on the FX2LP's clock, which runs at 48MHz. The following formula is used:

rate = 48 / (1 + divider)

Thus a sample rate of 2 MHz is selected by using 23 as the divider. The following sample rates are supported:

{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Samplerate
!Divider
|- bgcolor="#eeeeee"
| 200 kHz
| 239
|- bgcolor="#dddddd"
| 250 kHz
| 191
|- bgcolor="#eeeeee"
| 500 kHz
| 95
|- bgcolor="#dddddd"
| 1 MHz
| 47
|- bgcolor="#eeeeee"
| 2 MHz
| 23
|- bgcolor="#dddddd"
| 4 MHz
| 11
|- bgcolor="#eeeeee"
| 8 MHz
| 5
|- bgcolor="#dddddd"
| 12 MHz
| 3
|- bgcolor="#eeeeee"
| 16 MHz
| 2
|- bgcolor="#dddddd"
| 24 MHz
| 1
|}

Samples are read off endpoint 2. the Logic receives a read request from the host, and responds by sending the requested number of samples. The maximum number of samples is 4096, a constraint in the USB protocol. A sample is one byte, with each bit representing the state of one of the probes. Probe 1 (black wire) is in the MSB of the sample, probe 8 (purple wire) is the LSB.

The case has four '''Torx T2''' screws you need to remove in order to be able to open it.

See [[Saleae Logic/Info]] for more details (such as '''lsusb -vvv''' output) about the device.

>== Getting the firmware ==

The firmware required for the Cypress FX2 chip on the Saleae Logic is proprietary and can't be distributed with sigrok. But if you have a Logic, you can go and download the official software, install it somewhere (e.g. using '''wine''') and extract the required data. Unfortunately the firmware doesn't exist as a separate file, it's embedded in a file named '''WinUSBLogicInterface.dll''' or '''USBDeviceInterface.dll'''.

The following line must be used with the software [http://www.saleae.com/downloads/logic/Logic%20Setup%20Beta.exe 1.0.33 Beta for WinXP/Vista/7]:

$ '''dd if=WinUSBLogicInterface.dll of=fw.hex skip=8036 count=17366 bs=1'''

The following line must be used with the software [http://www.saleae.com/downloads/logic/Logic%20Setup.exe 1.0.21 for WinXP/Vista/7].

$ '''dd if=USBDeviceInterface.dll of=fw.hex skip=4220 count=17366 bs=1'''

Then:

$ '''objcopy -Iihex fw.hex -Obinary saleae-logic.firmware'''

The resulting '''saleae-logic.fw''' file is usable by sigrok directly, just copy it into the '''/usr/local/share/sigrok/firmware''' directory (may differ if you used the '''--prefix''' option of '''configure''').

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ifexytizet.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
----
=[http://ifexytizet.co.cc CLICK HERE]=
----
</div>

CWAV USBee SX/Info

2010-11-15T01:46:11Z

Ybucavamyva:

>== lsusb before firmware upload ==

This is the lsusb ouput on Linux, '''before''' any FX2 firmware is uploaded:

$ '''lsusb -vvv'''
Bus 001 Device 112: ID '''08a9:0009'''
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x08a9
idProduct 0x0009
bcdDevice 16.b5
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 171
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 6
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 6
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 3
bNumEndpoints 6
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ywylame.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----
=[http://ywylame.co.cc CLICK HERE]=
----
</div>

== lsusb after firmware upload ==

No changes, the '''lsusb -vvv''' output is exactly identical.

__FORCETOC__

ASIX SIGMA / SIGMA2

2010-11-14T23:11:38Z

Ybucavamyva:

[[File:ASIX SIGMA.jpg|thumb|right|ASIX SIGMA.]]
[[File:Sigma.jpg|thumb|right|ASIX SIGMA internals.]]

The [http://tools.asix.net/dbg_sigma.htm ASIX SIGMA] is a 16 channel logic analyzer with sample rate support up to 200 MHz and with 256 Mbit on-board memory.

It is supported by sigrok, and the necessary firmware files are generously provided by the vendor for distribution. As a result, the SIGMA works out of the box with sigrok. Trigger support has been implemented in 100 MHz and 200 MHz modes for rising/falling edges. In other modes, users can specify additional trigger values, listed in the table below.

{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Samplerate
!Number of probes
!Trigger support
|- bgcolor="#eeeeee"
| 200 kHz
| 16
| Edge of two probes, state, boolean expression<sup>1</sup>
|- bgcolor="#dddddd"
| 250 kHz
| 16
| Edge of two probes, state, boolean expression<sup>1</sup>
|- bgcolor="#eeeeee"
| 500 kHz
| 16
| Edge of two probes, state, boolean expression<sup>1</sup>
|- bgcolor="#dddddd"
| 1 MHz
| 16
| Edge of two probes, state, boolean expression<sup>1</sup>
|- bgcolor="#eeeeee"
| 5 MHz
| 16
| Edge of two probes, state, boolean expression<sup>1</sup>
|- bgcolor="#dddddd"
| 10 MHz
| 16
| Edge of two probes, state, boolean expression<sup>1</sup>
|- bgcolor="#eeeeee"
| 25 MHz
| 16
| Edge of two probes, state, boolean expression<sup>1</sup>
|- bgcolor="#dddddd"
| 50 MHz
| 16
| Edge of two probes, state, boolean expression<sup>1</sup>
|- bgcolor="#eeeeee"
| 100 MHz
| 8
| Edge of one probe
|- bgcolor="#dddddd"
| 200 MHz
| 4
| Edge of one probe
|}

<small>
<sup>1</sup> Boolean expression feature not implemented in sigrok yet.<br />
</small>

See [[ASIX SIGMA/Info]] for more detailed information on the device.

>== Example usage ==
An example that captures from 4 probes, for 100ms at 10 MHz, with trigger condition 1:high, 2:rising, 3:low, 4:high.

sigrok-cli --wait-trigger --triggers 1=1,2=r,3=0,4=1 --samples 5000000 --time 100 -o samplerate=10m -f bits -p 1-4

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://erotelokehu.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
----
=[http://erotelokehu.co.cc CLICK HERE]=
----
</div>

== Firmware ==

The firmware files (FPGA bitstreams) for the ASIX SIGMA have been provided by the vendor under a [http://sigrok.git.sourceforge.net/git/gitweb.cgi?p=sigrok/sigrok-firmwares;a=blob;f=asix-sigma/LICENSE.Sigma license which allows redistribution], and are available from the [http://sigrok.git.sourceforge.net/git/gitweb.cgi?p=sigrok/sigrok-firmwares;a=summary sigrok-firmwares] repository:

$ '''git clone git://sigrok.git.sourceforge.net/gitroot/sigrok/sigrok-firmwares'''

In order to use the ASIX SIGMA in sigrok, you need to copy the firmware files to the correct sigrok directory, '''/usr/local/share/sigrok/firmware''' per default:

$ '''cp sigrok-firmwares/asix-sigma/*.fw /usr/local/share/sigrok/firmware'''

== Resources ==

* [http://labs.ping.uio.no/2010/04/initial-support-for-asix-sigma-in-sigrok/ Initial support for Asix Sigma in Sigrok]
* [http://labs.ping.uio.no/2009/09/sampi-a-logic-analyzer/ PING Labs: Sampi – A Logic Analyzer]
* [http://www.flickr.com/photos/chlunde/3383669140/ flickr: ASIX SIGMA in chlunde's photostream] (photos and more information about the device)