Difference between revisions of "Example dumps"

From sigrok
Jump to navigation Jump to search
m
Line 7: Line 7:
'''Tarball:'''
'''Tarball:'''


You can download released tarballs of the sigrok-dumps file collection [https://sourceforge.net/projects/sigrok/files/source/sigrok-dumps/ from SourceForge].
You can download [http://sigrok.org/download/source/sigrok-dumps/ released tarballs] of the sigrok-dumps file collection.


'''Git:'''
'''Git:'''

Revision as of 19:03, 5 September 2013

We collect various captured logic analyzer signals / protocol dumps in the sigrok-dumps git repository:

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

Download

Tarball:

You can download released tarballs of the sigrok-dumps file collection.

Git:

Alternatively, you can also get the latest files from git:

$ git clone git://sigrok.org/sigrok-dumps

License

Unless otherwise noted, all dumps are released into the public domain by their respective authors.

Contributing dumps

We're happy to include further example data in our repository, please send us .sr files of any interesting data/protocol you may come across (even if sigrok doesn't yet have a protocol decoder for that protocol).

The easiest method is to clone the sigrok-dumps repository (e.g. on Gitorious or Github) and ask us to pull from there (e.g. in IRC or on the mailing list). Alternatively, you can also send the files (and a README, see below) to the mailing list.

Please include the following items:

  • Protocol dumps in .sr format (the sigrok session format). Please do not send files in binary, VCD, CSV, or other formats.
  • A README file (example) which contains info such as:
    • Which logic analyzer hardware was used.
    • Which target device was being probed (include vendor, name, description, relevant URLs, and so on, if possible).
    • Which probes (number/name/color) were connected to which pins on the target device.
    • Which exact sigrok-cli command line was used to generate the dump (includes device, samplerate, triggers, probe assignment, and so on).
    • Any other relevant information about your setup, the device being probed, and so on.
  • If you want to release the files under a (freeish) license other than "public domain", please let us know about that.