I was wondering what the random pinout was for. Now that I see your adapter, it looks quite neat. I had never seen extra long pin female headers before. I found this on on Ebay
I would do something similar with Protoshield. i.e. solder the header, solder the STM32 board. Solder all the connections with some wire-wrap wire. It ends up with a shallower combination. i.e. the depth of female + male + pcb.
Your construction method looks "quicker" than mine. Soldering headers is fast but the individual wire links take me some time. I have more choice in the actual wiring scheme.
Of course, buying a ready made Adapter Shield for Mega2560 or Due is the quickest of all. (and possibly cheaper)
I use the BluePill as sort of adapter to the parallel interface TFT.
It is fed with serial ascii pure text information from my IoT ESP8266 webserver by another Wemos D1 mini wifi client, to produce a formatted text display.
After having learned how to bitbang from Bodmer's TFT_HX8357_Due, and how to document the mapping, implementing a new mapping becomes quite easy. But for STM32 using a board with FSMC TFT connector is a better way; I will try this soon.
david_prentice:
Why do you want 8080-16 ? 8080-8 works reasonably fast. And uses less pins.
David.
Just because my screen is only 16 bits mode. Here is the screen TFT01-7.0.
david_prentice:
You tell me which pins you want to use. There is no current SPECIAL for 16-bit on a STM32.
Life is a lot simpler if you choose contiguous pins for a data bus. e.g. PA04..PA13, PB03..PB08
Data pins could be random but it makes the SPECIAL very messy to write.
David.
As far as wiring is concerned, I have no special preference.
I know it's better to take contiguous pins for data bus.
If you want to make a SPECIAL for this configuration, I leave you free to choose the pins of the data bus.
You can choose the simplest way for you to do it, I would connect the screen in function of the code that you will write.
I would not want to abuse your time but I would also like to connect other screens that I have and that one has an 8 bit data bus.
So my question you can make a SPECIAL one that supports the 8 bit and 16 bit screens.
ZinggJM:
@François
I have this combination, solved in my GxTFT library:
It should be possible to put this as modified special also into MCUFriend_kbv.
Jean-Marc
Thank you for your proposal but the problem is that I am not yet very comfortable with the low level code and the bitshift and bitwise to be able to integrate your code to the code of the library of David.
Quite honestly, I don't think the BluePill has enough GPIO.
By the time you have taken 16 data, 5 control pins there is nothing much left for your XPT2046 or an SD card.
e.g. PB0,1,3-15, PA15 for data bus.
e.g. PA0-3,8 for control
e.g. PA4-7 for SD, PA9,10 for XPT2046
Of course you can lose USB or SWD or Serial but you need at least one method of uploading the code.
Why do you want to use a small STM32? A Mega or Due would work straight out of the box.
If you choose your pins, I will write a SPECIAL for you. I was going to buy a MapleMini or BluePill and make my own Adapter. But I see little point if I have to sacrifice SPI or SWD or Serial.
David.
Edit. I have written the SPECIAL with the above wiring scheme. It is obviously Untested. I have ordered a BluePill and a 20x2 header. I will make and test an Adapter when these arrive from China. Is that wiring scheme ok for you?
hi I've just bought new 2.4 inch and i couldn't run it here is what i got from lcd id
Read Registers on MCUFRIEND UNO shield
controllers either read as single 16-bit
e.g. the ID is at readReg(0)
or as a sequence of 8-bit values
in special locations (first is dummy)
in order to get right left top and bottom i guess i should run calibration in arduino but when i ran it n i should touch a specific location it doesn't work i touch whole the screen but nothing happen i wanna to know that hardware problem or software
TouchScreen.h GFX Calibration
Making all control and bus pins INPUT_PULLUP
Typical 30k Analog pullup with corresponding pin
would read low when digital is written LOW
e.g. reads ~25 for 300R X direction
e.g. reads ~30 for 500R Y direction
Does your Glass look broken? I suspect that you have a crack across the screen in the X direction.
The 2.4" screens are normally pretty good. They survive the journey from China Post.
I have only ever managed to buy one 3.5" screen that was not cracked.