From cffef197b177d0bb12dd839b265a7f08dbf66c68 Mon Sep 17 00:00:00 2001 From: Marcus10110 Date: Mon, 3 Oct 2016 16:55:01 -0700 Subject: [PATCH] added readme --- readme.md | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 readme.md diff --git a/readme.md b/readme.md new file mode 100644 index 0000000..627fc79 --- /dev/null +++ b/readme.md @@ -0,0 +1,35 @@ +# Saleae Analyzer SDK Sample Analyzer +The Saleae Analyzer SDK is used to create custom plugins for the Saleae Logic software. These plugins are used to decode protocol data from captured waveforms. + +The libraries required to build a custom analyzer are stored in another git repository, located here: +[https://github.com/saleae/AnalyzerSDK](https://github.com/saleae/AnalyzerSDK) + +This repository should be used to create new analyzers for the Saleae software. + +First, fork, clone or download this repository. Forking is recommended if you plan to use version control or share your custom analyzer publicly. + +Note - This repository contains a submodule. Be sure to include submodules when cloning. If you download the repository from Github, the submodules are not included. In that case you will also need to download the AnalyzerSDK repository linked above and place the AnalyzerSDK folder inside of the SampleAnalyzer folder. + +Once downloaded, first run the script rename_analyzer.py. This script is used to rename the sample analyzer automatically. Specifically, it changes the class names in the source code, it changes the text name that will be displayed once the custom analyzer has been loaded into the Saleae Logic software, and it updates the visual studio project. + +There are two names you need to provide to rename_analyzer. The first is the class name. For instance, if you are developing a SPI analyzer, the class names would be SPIAnalyzer, SPIAnalyzerResults, SPIAnalyzerSettings, etc. +The file names would be similar, like SPIAnalyzer.cpp, etc. + +All analyzer classes should end with "Analyzer," so the rename script will add that for you. In the first prompt after starting the script, enter "SPI". The analyzer suffix will be added for you. This needs to be a valid C++ class name - no spaces, it can't start with a number, etc. + +Second, the script will prompt you for the display name. This will appear in the software in the list of analyzers after the plugin has loaded. This string can have spaces, since it will always be treated as a string, and not as the name of a class. + +After that, the script will complete the renaming process and exit. + + python rename_analyzer.py + SPI + Mark's SPI Analyzer + +To build on Windows, open the visual studio project in the Visual Studio folder, and build. The Visual Studio solution has configurations for 32 bit and 64 bit builds. You will likely need to switch the configuration to 64 bit and build that in order to get the analyzer to load in the Windows software. + +To build on Linux or OSX, run the build_analyzer.py script. The compiled libraries can be found in the newly created debug and release folders. + + python build_analyzer.py + + +