= Useful tools =

== Checking library dependencies ==

=== Windows ===
* [http://www.dependencywalker.com DependencyWalker]
* [http://www.totalcmd.net/plugring/peviewer.html PE Viewer] plug-in for [http://www.totalcmd.net TotalCommander] (aka ''!WindowsCommander'')
* [http://www.totalcmd.net/plugring/fileinfo.html FileInfo] plug-in for [http://www.totalcmd.net TotalCommander] (aka ''!WindowsCommander'')

=== Linux ===
* [https://en.wikipedia.org/wiki/ldd_(Unix) ldd]
* [https://en.wikipedia.org/wiki/nm_(Unix) nm]
* [http://sourceforge.net/projects/binscan BinScan] (integrates ```ldd``` and ```nm``` into a single GUI)
* [http://www.purinchu.net/software/elflibviewer.php ELF Library Viewer]

== Debugging COM port connection ==

=== Windows ===
* [[attachment:hypertrm.zip|HyperTerminal]] ([http://windows.microsoft.com/en-us/windows-vista/what-happened-to-hyperterminal available on Windows before Vista])
* [http://www.putty.org/ PuTTy] (some problems occur with binary data)

=== Linux ===
* [https://en.wikipedia.org/wiki/Kermit_(protocol) kermit]
* [https://en.wikipedia.org/wiki/Minicom minicom]

Writing to a COM port using terminal (supposing that we use port ```ttyS0```/COM1):
{{{#!sh
cat /dev/ttyS0
}}}

Reading from a COM port using terminal (supposing that we use port ```ttyS0```/COM1):
{{{#!sh
echo "message" > /dev/ttyS0
}}}

**Note:** on Linux, ```ttyS0``` corresponds to ```COM1```, ```ttyS1``` to ```COM2```, etc. (0-based counting).