*Note: After sourcing the Vivado settings scripts, you need to unset the LD_LIBRARY_PATH environment variable to avoid linking errors:*`unset LD_LIBRARY_PATH`
*Note: After sourcing the Vivado settings scripts, you need to unset the LD_LIBRARY_PATH environment variable to avoid linking errors:*`unset LD_LIBRARY_PATH`
---
---
\ No newline at end of file
**Q:***I set `LIBTPC_DEBUG=-1` and `LIBPLATFORM_DEBUG=-1` (as described in [GETTINGSTARTED-zynq.md](GETTINGSTARTED-zynq.md)), but I get no log output. Also tried setting `LIBTPC_LOGFILE=libtpc.log` and `LIBPLATFORM_LOGFILE=libplatform.log`, but the files are not created during execution or remain empty.*
**A:** Make sure you're using the debug libraries: Logging is deactivated completely in release mode libs, for performance reasons. Try to rebuild the libs via `tcp-build-libs --mode debug` (if linking statically, you'll also need to rebuild your application). If this does not work, check if the correct libraries are referenced by your application via `ldd <application>`.
---
**Q:***I'm not sure if the bitstream was loaded correctly. Is there any way to enumerate the function IDs that are present in the current configuration?*
**A:** There is a debug tool called `tpc-debug` that can print the current function map of the bitstream (among other things). You need to build it manually:
```
mkdir $TPC_HOME/arch/tests/build && cd $TPC_HOME/arch/tests/build
cmake .. && make && make install
```
Now `tpc-debug` should already be in the `$PATH`, you can run it without parameters. The tool is not documented at the moment, sorry about that, we'll try and write some documentation as soon as possible.
