libsigrokdecode.git - libsigrokdecode

Age	Commit message (Collapse)	Author
2013-11-27	Automate protocol decoder installation.	Bert Vermeulen
	This automatically figures out the files to install for each protocol decoder, without involving autotools. All python files (filenames ending in .py) are always installed. If a protocol decoder requires installation of a non-python file, a small file called 'config' can be created in that protocol decoder's directory, with the following content: # comments are ok extra-install vendorlist.txt commands.txt
2013-04-23	GPL headers: Use correct project name.	Uwe Hermann

2012-11-24	All PDs: Name the files pd.py consistently.	Uwe Hermann
	The Python module name is determined by the directory name (e.g. dcf77), the *.py file names in that directory don't matter and can be kept consistent.
2012-06-14	srd: Add experimental uart_dump decoder.	Uwe Hermann
	This PD stacks on top of the UART protocol decoder, and ouputs the decoded UART data in the "canonical" format, one byte after the other without any metadata (start bits, stop bits, parity bits, errors) and without any sample-numbers and such. This is basically what you would see in a terminal program, such as minicom. Per default it outputs to stdout, but using the 'filename' option and/or the 'filename_rx'/'filename_tx' options it can also output to files. Using the 'tx' and 'rx' options you can also select whether both, or only one of the data direction's data should be output. Example: sigrok-cli -i foo.sr \ -a uart:rx=0:tx=1,uart_dump:rx=no:tx=yes:filename=foo.txt \ -s uart,uart_dump This PD is just an experiment for now, it's possible that it will be replaced / reimplemented via a different sigrok facility later on.