Hi
TNX fer all the suggestions.  My 3.5" TFT is built as a shield and has 8 parallel data lines 5 control lines.
Using a I2C to parallel converter with it may be possible but the ones suggested are for use with a 2 or 4 line LCD screen.  It would be beyond my skill level to do this as there will probably be no control libraries available.
There does not seem to be any 3.5" TFT screens available with a serial interface (SPI or I2C)
However there are plenty of 2.8" TFT screens with an SPI available. These look like larger versions of the 2.2" TFT described in the project. As they only cost £7.00.  I think I will go down this route Keep It Simple!

I passed my morse test at 12wpm in 1983.  Its only in the last few years that I have "got back into CW"  I now seem to have reached a plateau at 18wpm.
(Hope its a plateau and not a ceiling HI)
I cannot recognise complete words (apart from the common Q codes) - I have to write everything down. Writing speed becomes a factor.
I hope that by using the MCT with Fansworth spacing I can start to recognise complete words and get my speed up a bit to 20+ wpm.

73
Dave
GM4NFI

On Fri, May 31, 2019 at 12:33 PM, K9HZ wrote:

Here is one… 5 boards for $3:

One thing to look at on those boards is if they come with the pins soldered on or not.  I ordered one a few weeks ago that I just got.  The pins are pre-soldered to it.  Now I have a display with pins and an I2C board with pins.  Not that it is that hard to de-solder the pins, but now I have a another task on my list because I didn't pay attention.

Hi,

I just received a "2.4 Inch SPI TFT Display Module Touch Panel LCD ILI9341 240x320 5V/3.3V" module. Also has a number KMRTM24024-SPI on it. 
Good price too, at $4.90.

This display is compatible with Jack's Morse Code Tutor sketch and I've had a chance to try it out with a Blue Pill board. 

I did come across one issue, so I wanted to mention it for others that have not already solved it themselves. 

The Morse Code Tutor schematic (maybe there is a corrected one) I have shows PA6 of the Blue Pill connected to MISO of the display and MOSI of the display is shown as not connected. MOSI of the display needs to be connected to PA7 of the Blue Pill to receive the display data. I tested disconnecting the PA6 to MISO wire and the display still functioned. 

Additionally I did not have a 10K resistor handy (too lazy to walk up the stairs) so I connected the display's reset pin to PA3 of the Blue Pill.

I changed the tft setup to explicitly define the pins (so the reset would work) as follows:

* Was:
--------------------
Adafruit_ILI9341 tft = Adafruit_ILI9341(TFT_CS, TFT_DC);
--------------------

* Changed to:
--------------------

#define TFT_CS   PA1

#define TFT_DC   PA0

#define TFT_MOSI PA7

#define TFT_CLK  PA5

#define TFT_RST  PA3

#define TFT_MISO PA6

 

Adafruit_ILI9341 tft = Adafruit_ILI9341(TFT_CS, TFT_DC, TFT_MOSI, TFT_CLK, TFT_RST, TFT_MISO);

----------------

Hope this is of some help.

I might experiment with the touch screen, although I was surprised at how slow the screen writing over SPI is. I have a parallel display (one of those Radio Shack discontinued "Seeed" displays) that I have sitting hooked up to a cheap USB logic analyzer trying to debug the interface (using an Adafruit driver that claims it works with the parallel display). I wonder if the parallel interface will be faster and more appropriate for fancier graphical interfaces. Although the Blue Pill has barely enough RAM (as well as flash) for that kind of interface. I have a STM development board with more RAM and a little more horsepower, with a similar 2.4 inch TFT display, using the parallel interface (in a "raw" pixel mode) and it is very fast. But the Blue Pill is way better price wise and I now have a small handful of them along with several cheap eBay displays for projects. 

Tom, wb6b

On Fri, Jun 21, 2019 at 06:06 AM, Steve McGrane wrote:

Feel free to update directly (or by emailing me with your specific changes)!

Hi Steve,

I generated a GitHub pull request with an updated schematic and a couple of small changes to the sketch.

And created a subdirectory where other folks who create community versions of the tutor could put their versions. 

I updated the schematic (as there was only a image file) by copying and pasting little bits of the schematic around and adding a couple of lines in GIMP. It worked out OK but was a slow process to force a photo editor into being a schematic editor. 

Tom, wb6b