The crosstalk and hardware guide docs went to the hardware project
(conv-ttl-blo-hw), and the outdated test log and other docs which were no longer
useful were removed.

The changes were done to account for changes in the bits of the status registers
between older versions, where switches and RTM lines were active-low, to the
changes in newer (conv-common-gw) versions, which have the switches and RTM
lines active-high

The ELMA readreg/writereg commands changed some time ago from;

readreg slot reg-index
writereg slot reg-index hex-val-to-write

to

readreg slot reg-hex-addr
writereg slot reg-hex-addr hex-val-to-write

Previously, the ei2c.py script was quickly changed from one version to another
to validate that the hardware works. Now, I finally found the time to make the
addition to support the older versions as well.

The ei2c.py was changed to check (in the open()) function which f/w version we
have on the ELMA SysMon and applies the correct command based on version.

The script now uses the same library files used by mass-multiboot.py, but is a
bit more interactive to the user than mass-multiboot.py.

mass-multiboot.py is intended to be used from the server directly to update
cards in a crate.

multiboot.py is intended to be used locally by a user, either to update a single
card, or to debug which gateware versions are loaded on the card's flash.

Changes:
- added progress string to output of read & write, instead of long address dumps
- more descriptive output in read and write
- increased timeout on IPROG command

This essential module is missing when cloning the repo, probably due to some
misunderstanding in the module's history of being added and removed from
.gitignore, for the sake of it being added ONCE and only ONCE and not having
to be modified ever again.

Hoping this issue will be once and FOR ALL solved...

The script now checks the board ID and if the board's a BLO PR, it checks the
version of the gateware and adapts the starting address of the MultiBoot
hardware module according to the gateware's memory map.

This is necessary due to the fact that the (soon-to-be-released) v3.0 gateware
changes the memory map and places the MultiBoot module at a different address.

NOTE: not yet tested with old gateware versions, but should work

Two scripts were implemented. The first reads out the channel and the second
clears them.

Apart from that, a small change was added to pulsetest, which now displays a
correct message when the board ID is not the ASCII for "TBLO".