thedon Posted August 4, 2017 Posted August 4, 2017 On 8/3/2017 at 3:35 AM, nopnop2002 said: As far as I experienced, Almost all Seller's information is a mistake. So the thing you should do first is to check the chip of your TFT. https://github.com/nopnop2002/lcd_id If your TFT is ILI9341 really, try this. https://github.com/nopnop2002/ili9325_rpi/wiki Does not work for me; it is definitely ILI9341; ili9341 is printed on the board also; I just get a white screen; no errors on the modprobes; just that nothing goes to the screen;
nopnop2002 Posted August 5, 2017 Posted August 5, 2017 A console appears by the following command. con2fbmap 1 8 When nothing is appears, please show me your result of lcd_id.
pfeerick Posted August 5, 2017 Posted August 5, 2017 3 hours ago, thedon said: Does not work for me; it is definitely ILI9341; ili9341 is printed on the board also; I just get a white screen; no errors on the modprobes; just that nothing goes to the screen; ILI9341 being printed on the board unfortunately sometimes means absolutely nothing nowadays, with Chinese manufacturers re purposing boards and substituting chips. I bought a 3.5" LCD Arduino shield about six months ago, intending to use it with a STM32 project, and had to give up, as it most certainly didn't have the ili9488 chip that it claimed to have... either that or is was faulty, as nothing useful for identifying it was reported by the Arduino equivalent of lcd_id. Please run the lcd_id app as directed by nopnop2002 (pinout is on the github page). Once you've ascertained that the LCD driver chip is a ILIL9341 (and/or is working), then you can start working towards getting it working.
thedon Posted August 5, 2017 Posted August 5, 2017 (edited) 13 hours ago, nopnop2002 said: A console appears by the following command. con2fbmap 1 8 When nothing is appears, please show me your result of lcd_id. I am not able to run lcd_id; its not compiling; first it complained about wiringPi so I got your WiringOP project and compiled it and tried "gpio readall" and I have attached the output it gives if that could be of any use; When I try to compile lcd_id.c I get the following error so not able to run lcd_id also; not sure how to move ahead :-( root@orangepipc:~/Desktop/lcd_id# cc -o lcd_id lcd_id.c -lwiringPi//usr/local/lib/libwiringPi.so: undefined reference to `pthread_join' //usr/local/lib/libwiringPi.so: undefined reference to `pthread_create' //usr/local/lib/libwiringPi.so: undefined reference to `pthread_cancel' collect2: error: ld returned 1 exit status BTW, I have tried this both on an orangepi pc and orangepi one; Edited August 5, 2017 by thedon additional info added
thedon Posted August 8, 2017 Posted August 8, 2017 @nopnop2002 or @pfeerick - please help out if possible folks;
Blast Posted August 9, 2017 Posted August 9, 2017 On 5/8/2017 at 9:19 AM, thedon said: root@orangepipc:~/Desktop/lcd_id# cc -o lcd_id lcd_id.c -lwiringPi Add -pthread after -lwiringPi I think worked for me when I tried making a c program with wiringOP, something like that... In other words you need to specify the pthread library to the compiler also - if I remember right
thedon Posted August 10, 2017 Posted August 10, 2017 On 8/9/2017 at 2:04 PM, Blast said: Add -pthread after -lwiringPi I think worked for me when I tried making a c program with wiringOP, something like that... In other words you need to specify the pthread library to the compiler also - if I remember right I was able to compile and run it;; given below is the output; I can see many ILIXXXX values; what should I consider? Quote root@orangepipc:~/Desktop/lcd_id# ./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) reg(0x0000) 28 28 ID: ILI9320, ILI9325, ILI9335, ... reg(0x0004) 2c 2c 2c 2c Manufacturer ID reg(0x0009) 29 29 29 29 29 Status Register reg(0x000a) 2a 2a Get Powsr Mode reg(0x000c) 2c 2c Get Pixel Format reg(0x0061) 29 29 RDID1 HX8347-G reg(0x0062) 2a 2a RDID2 HX8347-G reg(0x0063) 2b 2b RDID3 HX8347-G reg(0x0064) 2c 2c RDID1 HX8347-A reg(0x0065) 2d 2d RDID2 HX8347-A reg(0x0066) 2e 2e RDID3 HX8347-A reg(0x0067) 2f 2f RDID Himax HX8347-A reg(0x0070) 28 28 Panel Himax HX8347-A reg(0x00a1) a9 a9 a9 a9 a9 RD_DDB SSD1963 reg(0x00b0) a8 a8 RGB Interface Signal Control reg(0x00b4) ac ac Inversion Control reg(0x00b6) ae ae ae ae ae Display Control reg(0x00b7) af af Entry Mode Set reg(0x00bf) af af af af af af ILI9481, HX8357-B reg(0x00c0) a8 a8 a8 a8 a8 a8 a8 a8 a8 Panel Control reg(0x00c8) a8 a8 a8 a8 a8 a8 a8 a8 a8 a8 a8 a8 a8 GAMMA reg(0x00cc) ac ac Panel Control reg(0x00d0) a8 a8 a8 Power Control reg(0x00d2) aa aa aa aa aa NVM Read reg(0x00d3) ab ab ab ab ILI9341, ILI9488 reg(0x00da) aa aa RDID1 reg(0x00db) ab ab RDID2 reg(0x00dc) ac ac RDID3 reg(0x00e0) a8 a8 a8 a8 a8 a8 a8 a8 a8 a8 a8 a8 a8 a8 a8 a8 GAMMA-P reg(0x00e1) a9 a9 a9 a9 a9 a9 a9 a9 a9 a9 a9 a9 a9 a9 a9 a9 GAMMA-N reg(0x00ef) af af af af af af ILI9327 reg(0x00f2) aa aa aa aa aa aa aa aa aa aa aa aa Adjust Control 2 reg(0x00f6) ae ae ae ae Interface Control
nopnop2002 Posted August 10, 2017 Posted August 10, 2017 3 hours ago, thedon said: I was able to compile and run it;; given below is the output; I can see many ILIXXXX values; what should I consider? Check your Wirering. If your TFT is for Arduino MEGA(16bit Parallel), it doesn't work. If your TFT is REAL ILI9341 TFT for Arduino UNO(8bit Parallel), reg(0x00d3) is model id(00 00 93 41).
thedon Posted August 10, 2017 Posted August 10, 2017 6 hours ago, nopnop2002 said: Check your Wirering. If your TFT is for Arduino MEGA(16bit Parallel), it doesn't work. If your TFT is REAL ILI9341 TFT for Arduino UNO(8bit Parallel), reg(0x00d3) is model id(00 00 93 41). I have checked the wiring multiple times; I have wired it exactly as you have suggested on the wiki; its not 16 bit parallel, I am very sure, the board exactly looks same as on the video on this post; the board works well with arduino uno by the way; and from the lcd_id output its value is "ab ab ab ab"? what does that mean?
martinayotte Posted August 10, 2017 Posted August 10, 2017 By looking at the bytes pattern you've posted above, it is really looking strange with multiples duplicated bytes. Something must be wrongly connected ...
thedon Posted August 10, 2017 Posted August 10, 2017 3 minutes ago, martinayotte said: By looking at the bytes pattern you've posted above, it is really looking strange with multiples duplicated bytes. Something must be wrongly connected ... I have just followed the wiring given in the wiki, https://github.com/nopnop2002/ili9325_rpi so even I am wondering what could be wrong;
nopnop2002 Posted August 10, 2017 Posted August 10, 2017 7 hours ago, thedon said: I have just followed the wiring given in the wiki, https://github.com/nopnop2002/ili9325_rpi so even I am wondering what could be wrong; When I made a mistake in wiring, it was indicated as follows. $ sudo ./lcd_id c 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) reg(0x0000) 80 80 ID: ILI9320, ILI9325, ILI9335, ... reg(0x0004) 84 84 84 84 Manufacturer ID reg(0x0009) 89 89 89 89 89 Status Register reg(0x000a) 8a 8a Get Powsr Mode reg(0x000c) 8c 8c Get Pixel Format reg(0x0061) e1 e1 RDID1 HX8347-G reg(0x0062) e2 e2 RDID2 HX8347-G reg(0x0063) e3 e3 RDID3 HX8347-G reg(0x0064) e4 e4 RDID1 HX8347-A reg(0x0065) e5 e5 RDID2 HX8347-A reg(0x0066) e6 e6 RDID3 HX8347-A reg(0x0067) e7 e7 RDID Himax HX8347-A reg(0x0070) f0 f0 Panel Himax HX8347-A reg(0x00a1) a1 a1 a1 a1 a1 RD_DDB SSD1963 reg(0x00b0) b0 b0 RGB Interface Signal Control reg(0x00b4) b4 b4 Inversion Control reg(0x00b6) b6 b6 b6 b6 b6 Display Control reg(0x00b7) b7 b7 Entry Mode Set reg(0x00bf) bf bf bf bf bf bf ILI9481, HX8357-B reg(0x00c0) c0 c0 c0 c0 c0 c0 c0 c0 c0 Panel Control reg(0x00c8) c8 c8 c8 c8 c8 c8 c8 c8 c8 c8 c8 c8 c8 GAMMA reg(0x00cc) cc cc Panel Control reg(0x00d0) d0 d0 d0 Power Control reg(0x00d2) d2 d2 d2 d2 d2 NVM Read reg(0x00d3) d3 d3 d3 d3 ILI9341, ILI9488 reg(0x00da) da da RDID1 reg(0x00db) db db RDID2 reg(0x00dc) dc dc RDID3 reg(0x00e0) e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 e0 GAMMA-P reg(0x00e1) e1 e1 e1 e1 e1 e1 e1 e1 e1 e1 e1 e1 e1 e1 e1 e1 GAMMA-N reg(0x00ef) ef ef ef ef ef ef ILI9327 reg(0x00f2) f2 f2 f2 f2 f2 f2 f2 f2 f2 f2 f2 f2 Adjust Control 2 reg(0x00f6) f6 f6 f6 f6 Interface Control I'm using Armbian_5.30_Orangepipc_Debian_jessie_default_3.4.113 and https://github.com/zhaolei/WiringOP.git
Jason McNzee Posted August 16, 2017 Posted August 16, 2017 @nopnop2002 how is it that i can get your code that is designed for woring pi to work but FBTFT wont work?
Recommended Posts