Eliminate SCSI pass through, fix F1 targets again, valgrind all the goodies

The F4 code had #ifdefd out the verification, as the page/sector size can be
too large to read in via a single transfer.  Pull the verification out to a
separate function, the flash write was getting far too large anyway.

This branch should work for F1 and F4 devices.  It has currently been tested
with F1 value line, (a VL discovery board) programmed via gdb via both an
stlinkv1 and an stlinkv2.

F4 has _not_ yet been tested on this branch

Conflicts:
	.gitignore
	doc/tutorial/tutorial.pdf
	example/blink/main.c
	gdbserver/Makefile
	gdbserver/gdb-server.c
	src/stlink-common.c
	src/stlink-common.h
	src/stlink-usb.c

Added code for gdbserver to support the full flash size of the STM32F4

gdbserver can now upload up to 1MB projects to flash

Address was hex, size was decimal. Now uniform to be hex

Unable to compile STM32F4 discovery_demo on Linux

Thanks valgrind

And remove dead/duplicate code that is included in the opening of the device

Now that we're not using sg, and we've told the kernel to ignore the device in
usb-mass storage, we don't need to close and wait 5 seconds.  We can just
immediately issue the command to switch modes.

Lots of the debug code is far too verbose for anything but usb tracing.
Likewise, remove all the old scsi code that was simply ifdefd out.

in the top level, make clean cleans all stlink code.
in an application level, it only cleans that application

And update some of the logging to be a bit tidier

It compiles, but I've got bugs preventing me from running this yet :(

These libraries IGNORE assert_param.  Maybe later.

The "libstm32l_discovery" was actually the ST std periph library, plus the
CMSIS core files.  Renamed it as such, and restructured the directories and
naming to make this easier to contain the std periph drivers for more than
just one board.

Verified with the LCD demo makefile, and loading it in sram again.

You cannot read device params when we're not in debug mode and trying to will fill the USB buffer with garbage, and you will have to
unplug and replug and start again.  (which will fail, because, you're in the
wrong mode... :)

The change from run->step breaks the VL cores.  Need to double check that this
still works for L cores.  The whole flash writing needs to be better
abstracted.

Lots more informational debug.

Examples directory update for stm32f4