Added the repetitive stuff for the pulse test itself to a function that gets
called with the necessary parameters. Then, some small changes were made to the
pulse test (like clearing the counters before enabling the pulse repetition) to
make the pulse test work.

It now almost works, but we're still not there yet, to be determined if this is
a hardware issue or still script problems (most likely the former).

The pulse test should also have better output (like tell on ERROR on which phase
it fails)

The additions are:
- checking the fail-safe lines before passing the input pulse to the pulse
  counters
- adding a delay to the pulse generators, to account for hardware delay
  appearing on enable

The changes are the addition of chmod commands to set the shell scripts as
executables on make.

The change is to output to the .inf file the SFP EPPROM in "capital"
hexadecimal, i.e., 0x%02X instead of 0x%02x. This was done to keep to the rest
of the test scripts' outputs.

The rename phase (which was previously sed-based) has now been changed to change
the ELMA IP/hostname in the men-on, men-off and get-fan-speeds scripts.
Previously, I had omitted these three scripts and the IP and hostname were
hard-coded.

This has now been changed by environment variables, which "incidentally" have
the same way of definition in shell script as template strings under Python.
Therefore, this nice similarity between Python and shell script was used to
create a Python script that does the renaming where needed.

The renaming is done as follows:
- ptsdefine.py, via three template strings that are replaced by the `rename'
  script
- men-on/men-off/get-fan-speeds, via three template strings that double as
  environment variables; this doubling can be used in the future, should it be
  needed

When you run `make', the `rename' script is called with the necessary params
by the Makefile (assuming you give the Makefile variables -- otherwise the
`rename' script fails, telling you why) and it handles the renaming in all the
places above.

The main additions consist in checking for (and exiting on) wrong RTM detection
line readout, which indicates either a missing RTM, or that the Schmitt trigger
is a dud.

Then, the script also exits when the response of the PTS user to the questions
about the connections is a "no".

These two changes are both done to not waste time and energy on performing tests
on fundamentally wrong test conditions.

Finally, the pulses are enabled when performing fail-safe tests (MUX sel lines
"11"), since otherwise the test would pass without giving any useful information
on this test, as the HDL behaves in the same way if the RS-485 xceivers are
disabled or if they are in fail-safe.

Mainly, the build system changes consist in organizing the makefile better and
building to a local `ubuntu/' folder, which should then be copied directly to
the PTS system.

Then, the flash test changes consist in checking for a BusException error to not
fall in the trap of continuing on other exceptions occuring in the block of code
under `try'. Also, the flash test is more "modular" in that the gateware
versions to be downloaded can be specified at the beginning of the file.

This was necessary because there is an error in the schematics of the V2-0
cards, which has the nets for these two LEDs swapped versus the PCB. The error
will be corrected on the schematics level, and here we swap as well to have them
correctly mapped per the PCB.

Not yet synthesized

This commit:
- adds rs485_pulse.py test script
- adds corresponding bits in ptsdefine.py
- adds the test in the Makefile

This commit:
- adds logic for the RS-485 test (both in top-level and in pts_regs)
- changes names of bits in pts_regs to generate shorter names in the doc

The V2 card has the front-panel LEDs non-negated (the Schmitt-trigger inverters
have been removed) and has LEDs added for each inverter channel. The relevant
changes have been made in this respect as follows:
- changed signal names in UCF and top-level VHDL file
- changed polarity of pulse LED outputs to active-high
- added the inverter LED outputs
- added the inverter LEDs in the LED sequencing scheme for the LED test

This is done to avoid an unnecessary 5 mins wasted on writing the bitstream,
even though we need to re-run the tests due to a failure.