Its something we need to fix, but it didnt seem urgent, so I we forgot about it.

I did some investigation into what was causing it, but it wasn't obvious why it was happening. However I think we have a work around, as it is possible to determine the connection state of the Serial USB.

So the work around is to make the internals of the Serial USB class, ignore any chars that are printed (or written etc) to it, unless the PC terminal is open.

But we have yet to test in practice if this works, and whether it only works on the PC and with the IDE's terminal or works for other terminal programs and on OSX and Linux...

Things like this are not easy to fix as we need to test on multiple configurations.

To use it with the standard repo SPI library comment out these 3 lines in the header file:
#define SPI_16BIT
#define SPI_MODE_DMA 1
#define SPEED_UP 1 // Enables extra calculations in the circles routine to use fastVLine and fastHLine, only in DMA mode.

Once all is tested the changes to the SPI library will be integrated in Roger's repo.

Please post here if you have any issues with DMA or non-DMA.

A couple of quick questions, was all of this code merged in to Roger's master branch, and thus in to the board manager package, and is it possible to use this library with SPI2 and or SPI3 (if so, how).

To use it with the standard repo SPI library comment out these 3 lines in the header file:
#define SPI_16BIT
#define SPI_MODE_DMA 1
#define SPEED_UP 1 // Enables extra calculations in the circles routine to use fastVLine and fastHLine, only in DMA mode.

Once all is tested the changes to the SPI library will be integrated in Roger's repo.

Please post here if you have any issues with DMA or non-DMA.

A couple of quick questions, was all of this code merged in to Roger's master branch, and thus in to the board manager package, and is it possible to use this library with SPI2 and or SPI3 (if so, how).

Andy, I did not have time to tinker with anything for months, well, I had a little bit, but used it for other things, cause was not enough to do any serious progress on anything with the STM32.

I do not remember if I merged all the ILI libraries to Roger's repo, I believe he instead linked it as a submodule, and may have had to unlink due to issues with the library with the latest Arduino IDE
"It looks like the new IDE version 1.6.6 fails compiles if it finds anything it doesnt like about any libraries

Whatever latest changes I tested with that library, must be in my repo. I haven't done anything in many months now.
If you had been using the library and developed it further, you can merge your version in the repo.

Regarding using other SPI ports, I do not remember the details, but I do remember I wrote a test script that would use one SPI port for the sdcard, reading a wav file and playing it with a timer, and another SPI port using the ILI display to draw a spinning cube and show some CPU usage stats to see how much cpu cicles I was using in all that. It was fairly low usage, so I am almost sure I used DMA in both libraries on both SPI ports.
I would need to find that code to see if I hard coded the SPI2 port in one of the libraries, or modified either library to support any port. I'll try to find it if I get some time.

there seems to be choice in the data format though.
sdcard and touch are likely to be spi interfaces
shield types - uno maybe 8 bit data, i suspect mega shields may well be 16 bit data, again sdcard and touch on spi

connector pin layout - Oh let me count the ways matching a display to a board to the fsmc pinnings to software - i'm still working on that, try a google image search for "tft connector"

reading sources of utft, u8glib or adafruit libraries may give you some insight about initialisation and use of the display, minimally what needs supplying is the init command sequence and plot(x,y).
the rest is fonts and graphics