Melanrz Posted April 27, 2016 Posted April 27, 2016 Tutorial for ili9325 and spfd5408 soon tutorial for fastes ili9341 8
mutant9 Posted May 18, 2016 Posted May 18, 2016 Great work, Would you please share how did you get the ili9341 to work, I can't get it or the adafruit18 clone to work on the OPI one. Keep up the good work.
Melanrz Posted May 19, 2016 Author Posted May 19, 2016 Great work, Would you please share how did you get the ili9341 to work, I can't get it or the adafruit18 clone to work on the OPI one. Keep up the good work. MOSI - 19, MISO - 21, SCK (SPI_CLK) - 23, CS - 24, RESET, DC and LED - 11, 13, 15. power supply and ground as usual sudo modprobe fbtft_device custom name=fb_ili9341 gpios=reset:1,dc:0,led:3 speed=48000000 fps=25 rotate=90 bgr=1 txbuflen=65536 2
mutant9 Posted May 19, 2016 Posted May 19, 2016 Thanks a ton, it worked like a charm, and for the adafruit 1.8" clone, the gpio was the same "no MISO": MOSI - 19, SCK (SPI_CLK) - 23, CS - 24, RESET, DC and LED - 11, 13, 15. power supply and ground as usual and the modprobe is: sudo modprobe fbtft_device name=adafruit18 gpios=reset:1,dc:0,led:3 speed=16000000 fps=25 rotate=90 thanks again and keep up the good work.
Unoqueva Posted June 3, 2016 Posted June 3, 2016 MOSI - 19, MISO - 21, SCK (SPI_CLK) - 23, CS - 24, RESET, DC and LED - 11, 13, 15. power supply and ground as usual sudo modprobe fbtft_device custom name=fb_ili9341 gpios=reset:1,dc:0,led:3 speed=48000000 fps=25 rotate=90 bgr=1 txbuflen=65536 Are you sure, I marked in red what I think it is not right. I think it should be like this MOSI - 19, MISO - 21, SCK (SPI_CLK) - 23, CS - 24, RESET, DC and LED - 11, 13, 15. power supply and ground as usual sudo modprobe fbtft_device custom name=fb_ili9341 gpios=reset:0,dc:2,led:3 speed=48000000 fps=25 rotate=90 bgr=1 txbuflen=65536
markbirss Posted June 5, 2016 Posted June 5, 2016 Hi, thank you i have connected 2 spfd5408 displays (one to orange pi pc and one to orange pi 2) configured them with Armbian and console output and fb video output is working How about configuration of the touchscreen ?
Neo Posted December 7, 2016 Posted December 7, 2016 I bought a LCD with a link that you set up and followed all the steps that you suggested but without success. OPI lite, Armbian 5.20. I can see some activity on the screen but not pictures, video, watch. Only dark images and sometimes a little brighter.
horai Posted February 27, 2017 Posted February 27, 2017 Dear Sir, I am really excited by the capabilities of Orange Pi. I recently purchased Orange Pi Lite and wanted to reproduce running of the emulator depicted in your video, but I am really struggling to proceed any further with reasonable performance. Therefore I would like to kindly ask you for a help. I will briefly described my way. I am running Pi Lite on Armbian. I decided to compile Mupen64Plus this way: Before the standalone compilation, I installed the display according to your instructions finally obtaining /dev/fb8 as a display driver output. Then I installed Mali 400 hardware acceleration support via X11 following instructions here: http://linux-sunxi.org/Mali_binary_driver. I paid attention to installation of libdri2 which I think is necessary to obtain X11 fbturbo driver GLES acceleration.Anyway I ended up with compiled 'test' utility which was unable to draw mentioned triangles, anyway I proceeded to emulator compilation. I did this way: ./m64p_build.sh USE_GLES=1 NEON=1 to get GLES support, with a bit of tweaking and installing sdl 2.0, I was able to get the binaries. Without GLES the emulator runs on that tiny screen well, but it's very slow, probably not because of limited SPI framerate, but I guess because of lack of hardware acceleration but build with GLES=1 provides me binaries which refuse to run under X11. Anyway, the final error I got to is this: Core Error: SDL_SetVideoMode failed: GLX is not supported Video Error: Failed to set 32-bit video mode Core status: Rom closed Actually this output is with GLX option disable in X11, I guess GLX support is for pure OpenGL not for GLES, but somehow it's searching for GLX, maybe it's related to SDL layer only and X11 works correctly. I am running this emulator via X11 because I don't know whether it has support for DirectFB or anything else, but am I able to run this emulator in console with hardware acceleration via GLES? Anyway, maybe I have to recompile SDL with GLES support to proceed further with my error even though I have SDL2 which looks like it has support at least for OpenGL or maybe I am missing some essential piece of information or maybe I don't understand the matter fully and my way is not even possible. All Mali packages and Xorg packages, SDL are installed from repositories. Thank you very much Best regards Ivo
horai Posted February 28, 2017 Posted February 28, 2017 Hello, thank you very much, I did not handle SDL properly. Now it runs super fast hardware accelerated on this small display, only text textures are missing. Anyway, it's amazing what this hardware can do. Please, if you have some other more efficient way how to run this emulator (probably without X windows), me and I guess many other people would be very greateful for posting it. Thank you very much Ivo
aliceander Posted April 9, 2017 Posted April 9, 2017 Was unsuccessful when using an orange pi one. Dmesg has entries which look like a good spi device being registered, but the display only flickered a little - no images at all. Has anyone interfaced one of these Arduino displays with an orange pi one?
nopnop2002 Posted April 12, 2017 Posted April 12, 2017 On 2017/4/9 at 10:30 AM, aliceander said: Was unsuccessful when using an orange pi one. Dmesg has entries which look like a good spi device being registered, but the display only flickered a little - no images at all. Has anyone interfaced one of these Arduino displays with an orange pi one? There is many kind of TFT for Arduino. Various kinds of controllers are used. Melanrz uses TFT of ILI9341. Your TFT may not be ILI9341. When there is a picture of your TFT, It will be more clearly
Aung Naing Myat Thu Posted April 15, 2017 Posted April 15, 2017 hello,@Melanrz how can i get ili9481 3.5" lcd to get it working on orange pi? btw this is the library given by the seller http://pan.baidu.com/s/1c1jafW8 but its for uno. thanks
Magnets Posted April 20, 2017 Posted April 20, 2017 On 07/12/2016 at 4:49 PM, Neo said: I bought a LCD with a link that you set up and followed all the steps that you suggested but without success. OPI lite, Armbian 5.20. I can see some activity on the screen but not pictures, video, watch. Only dark images and sometimes a little brighter. I bought the same LCD but how do you know how to connect the pins? Is there a wiring guide anywhere?
aliceander Posted April 20, 2017 Posted April 20, 2017 Got a display that looks like the one in the OP but it's really dim. It's almost like the backlight is not on. I'm on an Orange Pi One with a 5V3A power supply. To init the display I ran modprobe fbtft_device name=itdb28 speed=48000000 fps=30 rotate=90 gpios=reset:20,dc:1,wr:3,cs:10,db00:0,db01:14,db02:2,db 03:21,db04:18,db05:19,db06:8,db07:9 My test python script is: #!/usr/bin/env python import pygame, osfrom time import sleep os.putenv('SDL_FBDEV','/dev/fb8') pygame.init() screen = pygame.display.set_mode((0,0)) screen.fill((0,0,180)) rfont = pygame.font.SysFont(None,30) size = screen.get_rect() resolutiontext = rfont.render("%d x %d" % (size[2],size[3]), 1, (255,255,255)) resrect = resolutiontext.get_rect() resrect.centerx = size.centerx resrect.centery = size.centery screen.blit(resolutiontext, resrect) pygame.display.flip() sleep(5) pygame.quit() I've followed @Melanrz's hookup instructions to the best of my ability but something must be wrong. Assuming I got the connections right, how can I control the backlight to see if that's the problem (how to turn on/turn off the backlight)? Or, is there something else?
nopnop2002 Posted April 21, 2017 Posted April 21, 2017 22 hours ago, Magnets said: I bought the same LCD but how do you know how to connect the pins? Is there a wiring guide anywhere? As far as it's judged from a picture, a voltage regulator isn't mounted on this TFT. I think that this module drive 3.3V. And If it's ILI9325 really, this program (NOT frame buffer driver) will works. https://github.com/nopnop2002/ili9325_rpi
Magnets Posted April 21, 2017 Posted April 21, 2017 8 hours ago, nopnop2002 said: As far as it's judged from a picture, a voltage regulator isn't mounted on this TFT. I think that this module drive 3.3V. And If it's ILI9325 really, this program (NOT frame buffer driver) will works. https://github.com/nopnop2002/ili9325_rpi You're correct, it seems the 5v input doesn't actually do anything, you need to drive the 3.3v input to get the backlight
aliceander Posted April 21, 2017 Posted April 21, 2017 OMG -- I think I just understood your point! The backlight might be powered by the 3v pin on the display. I've been applying power to the display's 5v pin and not connecting the 3v pin. It kind of makes perfect sense. I'll try this as soon as I get home. And thank you for repeating the information until I got it.
Magnets Posted April 22, 2017 Posted April 22, 2017 I'm not having any luck getting an image. I've connected mine (same model as Neo) as shown in the first video. If I don't connect the backlight (3v3) then the screen flashes faintly sometimes when using test programs. When the backlight is connected it doesn't appear to do anything - just a white screen
nopnop2002 Posted April 22, 2017 Posted April 22, 2017 17 hours ago, Magnets said: I'm not having any luck getting an image. I've connected mine (same model as Neo) as shown in the first video. If I don't connect the backlight (3v3) then the screen flashes faintly sometimes when using test programs. When the backlight is connected it doesn't appear to do anything - just a white screen I have 3.6 inches of TFT. There is a marking of 61503 in the back. It's akin to your TFT. This is the model number of the driver IC. Your TFT may be S6D0154. mcufriend.com has a lot of variations. http://domoticx.com/arduino-shield-2-4-tft-lcd-touch/ When you'd like to know the model number of the ILITEK driver IC, use this one. https://github.com/nopnop2002/lcd_id Something may be understood. 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) 93 25 ID: ILI9320, ILI9325, ILI9335, ... reg(0x0004) 00 00 00 00 Manufacturer ID reg(0x0009) 00 00 00 00 00 Status Register reg(0x000A) 00 00 Get Powsr Mode reg(0x000C) 00 00 Get Pixel Format reg(0x0061) 00 00 RDID1 HX8347-G reg(0x0062) 00 00 RDID2 HX8347-G reg(0x0063) 00 00 RDID3 HX8347-G reg(0x0064) 00 00 RDID1 HX8347-A reg(0x0065) 00 00 RDID2 HX8347-A reg(0x0066) 00 00 RDID3 HX8347-A reg(0x0067) 00 00 RDID Himax HX8347-A reg(0x0070) 00 00 Panel Himax HX8347-A reg(0x00A1) 00 00 00 00 00 RD_DDB SSD1963 reg(0x00B0) 00 00 RGB Interface Signal Control reg(0x00B4) 00 00 Inversion Control reg(0x00B6) 00 00 00 00 00 Display Control reg(0x00B7) 00 00 Entry Mode Set reg(0x00BF) 00 00 00 00 00 00 ILI9481, HX8357-B reg(0x00C0) 00 00 00 00 00 00 00 00 00 Panel Control reg(0x00C8) 00 0A 00 0A 00 0A 00 0A 00 0A 00 0A 00 GAMMA reg(0x00CC) 00 04 Panel Control reg(0x00D0) 00 33 00 Power Control reg(0x00D2) 00 FF 00 FF 00 NVM Read reg(0x00D3) 00 3F 00 3F ILI9341, ILI9488 reg(0x00DA) 00 00 RDID1 reg(0x00DB) 00 00 RDID2 reg(0x00DC) 00 00 RDID3 reg(0x00E0) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 GAMMA-P reg(0x00E1) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 GAMMA-N reg(0x00EF) 12 31 12 31 12 31 ILI9327 reg(0x00F2) 00 00 00 00 00 00 00 00 00 00 00 00 Adjust Control 2 reg(0x00F6) 00 00 00 00 Interface Control
Magnets Posted April 23, 2017 Posted April 23, 2017 12 hours ago, nopnop2002 said: When you'd like to know the model number of the ILITEK driver IC, use this one. https://github.com/nopnop2002/lcd_id Mine is: 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) 15 80 ID: ILI9320, ILI9325, ILI9335, ... reg(0x0004) 00 01 00 01 Manufacturer ID reg(0x0009) 00 01 00 01 00 Status Register reg(0x000a) 00 00 Get Powsr Mode reg(0x000c) 00 00 Get Pixel Format reg(0x0061) 00 00 RDID1 HX8347-G reg(0x0062) 00 01 RDID2 HX8347-G reg(0x0063) 00 00 RDID3 HX8347-G reg(0x0064) 00 00 RDID1 HX8347-A reg(0x0065) 00 00 RDID2 HX8347-A reg(0x0066) 00 00 RDID3 HX8347-A reg(0x0067) 00 00 RDID Himax HX8347-A reg(0x0070) 00 00 Panel Himax HX8347-A reg(0x00a1) 00 00 00 00 00 RD_DDB SSD1963 reg(0x00b0) 00 00 RGB Interface Signal Control reg(0x00b4) 00 00 Inversion Control reg(0x00b6) 00 00 00 00 00 Display Control reg(0x00b7) 00 00 Entry Mode Set reg(0x00bf) 00 00 00 00 00 00 ILI9481, HX8357-B reg(0x00c0) 00 00 00 00 00 00 00 00 00 Panel Control reg(0x00c8) 00 14 00 14 00 14 00 14 00 14 00 14 00 GAMMA reg(0x00cc) 00 02 Panel Control reg(0x00d0) 00 5a 00 Power Control reg(0x00d2) 00 be 00 be 00 NVM Read reg(0x00d3) 00 ff 00 ff ILI9341, ILI9488 reg(0x00da) 00 00 RDID1 reg(0x00db) 00 00 RDID2 reg(0x00dc) 00 00 RDID3 reg(0x00e0) 16 06 16 06 16 06 16 06 16 06 16 06 16 06 16 06 GAMMA-P reg(0x00e1) 07 88 07 88 07 88 07 88 07 88 07 88 07 88 07 88 GAMMA-N reg(0x00ef) 00 00 00 00 00 00 ILI9327 reg(0x00f2) 00 00 00 00 00 00 00 00 00 00 00 00 Adjust Control 2 reg(0x00f6) 00 54 00 54 Interface Control The number on the back is: 61580 The board looks exactly like the one Neo posted further up, i.e. without the 3.3v regulator
nopnop2002 Posted April 23, 2017 Posted April 23, 2017 50 minutes ago, Magnets said: The number on the back is: 61580 reg(0x0000) 15 80 ID: ILI9320, ILI9325, ILI9335, ... The device code “1580”h is Renesas R61580. See following page 39. Device Code Read (R00h). http://aitendo3.sakura.ne.jp/aitendo_data/product_img/lcd/tft/DST2401PH/DST2401PH_eR61580_Rev1.01.pdf This is the rare driver which isn't also in the following page. http://domoticx.com/arduino-library-tft-lcd-shield/ fbtft isn't supporting it.
An Li Posted June 9, 2017 Posted June 9, 2017 hi guys! I'm working on ili9341 display with orange pi one.But whatever I do just nothing display on my TFT!!Here is my configure and hardware connection MOSI (pin19), MISO(pin21), SCK(pin23), CS(pin24), RESET(pin11), DC(pin13) ,LED(pin15). root@orangepione:~# sudo modprobe fbtft_device custom name=fb_ili9341 gpios=reset:1,dc:0,led:3 speed=48000000 fps=25 rotate=90 bgr=1 txbuflen=65536 root@orangepione:~# startx Here is log info form Xorg.0.log [ 7547.069] X.Org X Server 1.18.4 Release Date: 2016-07-19 [ 7547.070] X Protocol Version 11, Revision 0 [ 7547.070] Build Operating System: Linux 4.4.0-45-generic armv7l Ubuntu [ 7547.070] Current Operating System: Linux orangepione 3.4.113-sun8i #46 SMP PREEMPT Mon May 29 15:47:28 CEST 2017 armv7l [ 7547.072] Build Date: 02 November 2016 10:05:15PM [ 7547.072] xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see http://www.ubuntu.com/support) [ 7547.072] Current version of pixman: 0.33.6 [ 7547.073] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 7547.073] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 7547.075] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jun 9 17:34:02 2017 [ 7547.076] (==) Using config file: "/etc/X11/xorg.conf" [ 7547.077] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 7547.077] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 7547.080] (==) No Layout section. Using the first Screen section. [ 7547.080] (==) No screen section available. Using defaults. [ 7547.080] (**) |-->Screen "Default Screen Section" (0) [ 7547.081] (**) | |-->Monitor "<default monitor>" [ 7547.082] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 7547.082] (**) | |-->Device "Allwinner A10/A13 FBDEV" [ 7547.082] (**) | |-->GPUDevice "Allwinner A10/A13 FBDEV" [ 7547.082] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 7547.083] (**) Option "BlankTime" "0" [ 7547.083] (**) Option "StandbyTime" "0" [ 7547.083] (**) Option "SuspendTime" "0" [ 7547.083] (**) Option "OffTime" "0" [ 7547.083] (==) Automatically adding devices [ 7547.083] (==) Automatically enabling devices [ 7547.083] (==) Automatically adding GPU devices [ 7547.084] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 7547.084] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 7547.084] Entry deleted from font path. [ 7547.084] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 7547.084] Entry deleted from font path. [ 7547.084] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 7547.084] Entry deleted from font path. [ 7547.084] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. [ 7547.084] Entry deleted from font path. [ 7547.084] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 7547.084] Entry deleted from font path. [ 7547.085] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 7547.085] Entry deleted from font path. [ 7547.126] compiled for 1.18.4, module version = 0.0.2 [ 7547.126] ABI class: X.Org Video Driver, version 20.0 [ 7547.126] (II) FBTURBO(0): using /dev/fb8 [ 7547.126] (II) FBTURBO(1): using /dev/fb8 [ 7547.126] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 7547.126] (EE) Screen 1 deleted because of no matching config section. [ 7547.126] (II) UnloadModule: "fbturbo" [ 7547.126] (II) UnloadSubModule: "fbdevhw" [ 7547.126] (II) FBTURBO(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 16/16 [ 7547.127] (==) FBTURBO(0): Depth 16, (==) framebuffer bpp 16 [ 7547.127] (==) FBTURBO(0): RGB weight 565 [ 7547.127] (==) FBTURBO(0): Default visual is TrueColor [ 7547.127] (==) FBTURBO(0): Using gamma correction (1.0, 1.0, 1.0) [ 7547.127] (II) FBTURBO(0): hardware: fb_ili9341 (video memory: 150kB) [ 7547.127] (**) FBTURBO(0): Option "fbdev" "/dev/fb8" [ 7547.127] (**) FBTURBO(0): Option "SwapbuffersWait" "true" [ 7547.127] (II) FBTURBO(0): processor: ARM Cortex-A7 [ 7547.127] (II) FBTURBO(0): checking modes against framebuffer device... [ 7547.127] (II) FBTURBO(0): checking modes against monitor...[ 7547.127] (--) FBTURBO(0): Virtual size is 320x240 (pitch 320) [ 7547.128] (**) FBTURBO(0): Built-in mode "current" [ 7547.128] (==) FBTURBO(0): DPI set to (96, 96) [ 7547.128] (II) Loading sub module "fb" [ 7547.128] (II) LoadModule: "fb" [ 7547.128] (II) Loading /usr/lib/xorg/modules/libfb.so [ 7547.129] (II) Module fb: vendor="X.Org Foundation" [ 7547.129] compiled for 1.18.4, module version = 1.0.0 [ 7547.129] ABI class: X.Org ANSI C Emulation, version 0.4 [ 7547.129] (II) FBTURBO(0): FBIOBLANK: Invalid argument (Screen blanking not supported by kernel - disabling) [ 7547.129] (II) FBTURBO(0): using backing store heuristics [ 7547.137] (II) FBTURBO(0): can't load 'g2d_23' kernel module [ 7547.137] (II) FBTURBO(0): failed to enable the use of sunxi display controller [ 7547.137] (II) FBTURBO(0): No sunxi-g2d hardware detected (check /dev/disp and /dev/g2d) [ 7547.137] (II) FBTURBO(0): G2D hardware acceleration can't be enabled [ 7547.137] (II) FBTURBO(0): enabled VFP/NEON optimizations [ 7547.137] (==) FBTURBO(0): Backing store enabled [ 7547.138] (==) FBTURBO(0): DPMS enabled [ 7547.138] (II) FBTURBO(0): failed to enable hardware cursor [ 7547.138] (II) FBTURBO(0): failed to enable hardware cursor [ 7547.159] (II) FBTURBO(0): can't load 'sunxi_cedar_mod' kernel module [ 7547.159] (II) Loading sub module "dri2" [ 7547.159] (II) LoadModule: "dri2" [ 7547.159] (II) Module "dri2" already built-in [ 7547.160] (II) FBTURBO(0): display controller hardware overlays can't be used for DRI2 [ 7547.160] (II) FBTURBO(0): Wait on SwapBuffers? enabled [ 7547.160] (II) FBTURBO(0): [DRI2] Setup complete [ 7547.160] (II) FBTURBO(0): [DRI2] DRI driver: lima [ 7547.160] (II) FBTURBO(0): using DRI2 integration for Mali GPU (UMP buffers) [ 7547.160] (II) FBTURBO(0): Mali binary drivers can only accelerate EGL/GLES [ 7547.160] (II) FBTURBO(0): so AIGLX/GLX is expected to fail or fallback to software please help me!!I'm going crazy with tft display!!thx!!!!!
nopnop2002 Posted June 11, 2017 Posted June 11, 2017 On 2017/6/10 at 3:14 AM, An Li said: please help me!!I'm going crazy with tft display!!thx!!!!! $ sudo modprobe fbtft_device name=flexfb gpios=dc:0,reset:1 speed=3200000 $ sudo modprobe flexfb width=320 height=240 buswidth=8 init=\ -1,0x28,-2,20,\ -1,0xCF,0x00,0x83,0x30,\ -1,0xED,0x64,0x03,0x12,0x81,\ -1,0xE8,0x85,0x01,0x79,\ -1,0xCB,0x39,0x2c,0x00,0x34,0x02,\ -1,0xF7,0x20,\ -1,0xEA,0x00,0x00,\ -1,0xC0,0x26,\ -1,0xC1,0x11,\ -1,0xC5,0x35,0x3E,\ -1,0xC7,0xBE,\ -1,0xB1,0x00,0x1B,\ -1,0xB6,0x0a,0x82,0x27,0x00,\ -1,0xB7,0x07,\ -1,0x3A,0x55,\ -1,0x36,0x38,\ -1,0x11,-2,120,\ -1,0x29,-2,20,\ -3 You can get framebuffer device. $con2fbmap 1 8
An Li Posted June 13, 2017 Posted June 13, 2017 On Sun Jun 11 2017 at 11:00 PM, nopnop2002 said: $ sudo modprobe fbtft_device name=flexfb gpios=dc:0,reset:1 speed=3200000 $ sudo modprobe flexfb width=320 height=240 buswidth=8 init=\ -1,0x28,-2,20,\ -1,0xCF,0x00,0x83,0x30,\ -1,0xED,0x64,0x03,0x12,0x81,\ -1,0xE8,0x85,0x01,0x79,\ -1,0xCB,0x39,0x2c,0x00,0x34,0x02,\ -1,0xF7,0x20,\ -1,0xEA,0x00,0x00,\ -1,0xC0,0x26,\ -1,0xC1,0x11,\ -1,0xC5,0x35,0x3E,\ -1,0xC7,0xBE,\ -1,0xB1,0x00,0x1B,\ -1,0xB6,0x0a,0x82,0x27,0x00,\ -1,0xB7,0x07,\ -1,0x3A,0x55,\ -1,0x36,0x38,\ -1,0x11,-2,120,\ -1,0x29,-2,20,\ -3 You can get framebuffer device. $con2fbmap 1 8 thanks a lot!I will try and report
Mohammad Mubin Posted July 16, 2017 Posted July 16, 2017 sudo modprobe fbtft_device custom name=flexpfb speed=48000000 fps=60 gpios=reset:20,dc:1,wr:3,cs:10,db00:0,db01:14,db02:2,db03:21,db04:18,db05:19,db06:8,db07:9 sudo modprobe flexfb width=320 height=480 buswidth=8 init=-1,0x11,-2,200,-1,0x36,-1,0x3A,0x05,-1,0x36,0x48,-1,0x13,-1,0x29,-1,0x2C,-3 i edited the X11 config files to match it with the frame buffer and wrote startx i also tried displaying images but i get the same thing 1
thedon Posted August 1, 2017 Posted August 1, 2017 On 5/19/2016 at 5:05 PM, Melanrz said: MOSI - 19, MISO - 21, SCK (SPI_CLK) - 23, CS - 24, RESET, DC and LED - 11, 13, 15. power supply and ground as usual sudo modprobe fbtft_device custom name=fb_ili9341 gpios=reset:1,dc:0,led:3 speed=48000000 fps=25 rotate=90 bgr=1 txbuflen=65536 Great tutorial buddy; I am using a ILI9341 but I dont see any MOSI/MISO/SCK pins on it; also what is LED pin? is there a complete wiring guide? I am trying to hookup to orangepi one and have not seen any success till now; my lcd module is similar to what you have used but it has ILI9341 written on back; Please help and share a wiring diagram; following are the pins my LCD module has (LCD_RST, LCD_CS, LCD_RS, LCD_WR, LCD_RD, GND, 5V, 3V3, LCD_D0, LCD_D1, LCD_D2, LCD_D3, LCD_D4, LCD_D5, LCD_D6, LCD_D7, SD_SS, SD_DI, SD_D0, SD_SCK); I want to use only the display to show camera stream, nothing else is needed, no need of touch or sd card capability, just need to show the camera video stream on the display; please help;
pfeerick Posted August 2, 2017 Posted August 2, 2017 I'm not familiar with using this type of LCD on linux, but it sounds like your LCD is a parallel type connection (D0-D7 + others) rather than a SPI type connection (MOSI, MOSI, CLK, CS/SS), so won't work with these instructions. And the LED pin will be the pin that that controls the LED backlight for the display.
thedon Posted August 2, 2017 Posted August 2, 2017 4 hours ago, pfeerick said: I'm not familiar with using this type of LCD on linux, but it sounds like your LCD is a parallel type connection (D0-D7 + others) rather than a SPI type connection (MOSI, MOSI, CLK, CS/SS), so won't work with these instructions. And the LED pin will be the pin that that controls the LED backlight for the display. I get what you are saying but I will wait for the post author to respond since the lcd module he has shown in the first video is same as what I have except that it has a ili9341 chipset; the pins are exactly same and then someone has asked about ili9341 and he gave some specific wiring changes so I have mentioned the board and the pins it has so that there is no confusion; 1
nopnop2002 Posted August 2, 2017 Posted August 2, 2017 On 2017年8月2日 at 2:59 PM, thedon said: I get what you are saying but I will wait for the post author to respond since the lcd module he has shown in the first video is same as what I have except that it has a ili9341 chipset; the pins are exactly same and then someone has asked about ili9341 and he gave some specific wiring changes so I have mentioned the board and the pins it has so that there is no confusion; 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
Recommended Posts