From de5edbe20b612c9abbfa9fb551e7e5a8f8df36dd Mon Sep 17 00:00:00 2001 From: Johannes Demel Date: Wed, 29 Jan 2014 16:40:23 -0800 Subject: debug_prints_tool: New tool to plot the output of DEBUG_TXRX-enabled output. --- tools/uhd_txrx_debug_prints_README.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 tools/uhd_txrx_debug_prints_README.md (limited to 'tools/uhd_txrx_debug_prints_README.md') diff --git a/tools/uhd_txrx_debug_prints_README.md b/tools/uhd_txrx_debug_prints_README.md new file mode 100644 index 000000000..1425a4d96 --- /dev/null +++ b/tools/uhd_txrx_debug_prints_README.md @@ -0,0 +1,17 @@ +UHD TX/RX DEBUG PRINTS +====================== + +A tool for extensive debugging with UHD. + +Install +------- +Activate it by ticking `UHD_TXRX_DEBUG_PRINTS` in cmake-gui for your UHD installation. Then recompile and reinstall UHD. + +Use +--- +Run your application and pipe stderr to a file. +this is mostly done by
+`app_call 2> dbg_print_file.txt`
+After finishing the application offline processing of the gathered data is done with a python script called
+`uhd_txrx_debug_prints_graph.py`
+There are a lot of functions that help to preprocess your data and that describe the actual meaning of all the data points. in the end though, it comes down to the users needs what he wants to plot and see. \ No newline at end of file -- cgit v1.2.3