TFT01-2.2S with notro's fbtft module

[desmondttm123]

sorry i meant what operating system are you using? is it the kernel given? THANKS!

[desmondttm123]

it worked!!!!! Thanks so much!!!!!!!!! may i ask, what is your configuration for setting it up for startup?
cheers!!

[wouterel]

I created a file /etc/modprobe.d/fbtft_device.conf containing the following line:

Code: Select all

options fbtft_device custom name=fb_ili9341 speed=32000000 buswidth=8 gpios=reset:23,led:24,dc:25 rotate=180 bgr=1

and added a line to /etc/modules:

Code: Select all

fbtft_device

Operating system is a recent raspbian with the most recent version of notro's kernel installed.

[desmondttm123]

hi , thanks for that code =) do i need to paste the fbtft_device directory in rc.local?
also, is there a way to view the terminal boot up? as in the terminal view before it enters the GUI =)

thanks!

[wouterel]

this is about kernel modules... no need to do anything with rc.local. /etc/modules and files in /etc/modprobe.d are all you need to worry about to get a working framebuffer device for your tft module.
I'm not sure what you mean by your other question... if it is about using the tft screen as your console during boot, please read this: https://github.com/notro/fbtft/wiki/Boot-console. In fact, there are a few more pages on that wiki that could be helpful to you to know what you can do with the screen. If you have any more specific questions, feel free to post here.

[desmondttm123]

hi, thanks for the reply =)
the instructions were useful =) but what i am planning to do is that as soon as the pi is powered on, it displays the boot up process, showing all the text. then only boots to desktop

something like this

http://www.youtube.com/watch?v=IDMe5PkReMw
any idea how? thanks!!

[wouterel]

In that movie the display only turns on when the boot process is already well on its way (to be precise: when the kernel modules are loaded). If that is good enough for you, you don't need to compile your own kernel and you can just follow the instructions "#2" in the link I shared in my previous post. You will need to edit /boot/cmdline.txt as described on that page. Starting X with it is also explained in a different page on the same wiki https://github.com/notro/fbtft/wiki/Framebuffer-use.

[desmondttm123]

hi,thanks for your posts again =) just wondering, can u play videos on the tft?

[wouterel]

yes. mplayer works. read that wiki I linked to in my previous posts.

[Thorin Oakenshield]

Hi! I Why my lcd ili9341 says me FATAL: Module fbtft_device not found?

[fiskius]

Hi, I'd be grateful if anyone could give me a hand with this...
I've been playing around with a few TFT's and I've got a 1.8" version working and a HY2.8" version working, but I'm having problems with my 2.2" (like this, http://www.ebay.de/itm/2-2-Serial-SPI-T ... 2ec8b7b394 or this: http://www.raspberrypirobot.com/product ... d-monitor/)

I'm using the adafruit22a driver since I'm sure this uses the same chip, but just getting a blank black screen, which is odd, since the other TFT's worked first time.

Software: Downloaded notro's Raspbian image with drivers already installed
Line in modules: fbtft_device name=adafruit22fb speed=32000000 buswidth=8 gpios=reset:25,led:18,cs:8,cd:24, bgr=1
(I've tried all permutations of this line with and without various options, not quite sure if the gpio refers to the pin number of pin name, but I've tried both to no avail)

Wiring:
RPI pin --- TFT pin ---- Rpi name
21——MISIO———–GPIO09
12——LED————-GPIO18
23——SCK————-GPIO11
19——MOSI————GPIO10
18——D/C————-GPIO24
22——RESET———–GPIO25
24——CS————–GPIO08
6——-GND————-GND (-)
1——-VCC————-VCC +3V3

Anyone any ideas?

PS: dmesg shows the driver is loaded and working but there is no fb1 file in /dev which is also a bit odd...


Andy

[notro]

It looks to be same as this display: https://github.com/notro/fbtft/wiki/Mor ... tft01-22sp
From the blog post:

Code: Select all

sudo modprobe fbtft_device custom name=fb_ili9341  gpios=reset:25,dc:24,led:18 speed=16000000 rotate=90 bgr=1

[fiskius]

Hi notro,

Thanks for your help, I've tried that and I've got a follow up question. fb_ili9341 driver as I understand does not come by default in your image - loading it up, I get this message from dmesg:

fbtft_device: `' invalid for parameter `custom'

I can see you have a driver file written in C on your github page, but I couldn't find any instructions on how to add this particular driver into an existing installation. Sorry for the newbie question, I've not really done compiling drivers before!

Thanks

Andy

[notro]

The driver is built, you can demonstrate that by typing: modinfo fb_ili9341 (if you use the normal FBTFT kernel)

modprobe is complaining about wrong use of the 'custom' argument. Do you try to assing a value to it?

[fiskius]

Hi notro, thanks for the reply. I typed in exactly as you said (without sudo modprobe since I put it in the /etc/modules file)

running sudo modinfo fb_ili9341 gives:
ERROR: Module fb_ili9341 not found.

So that's the issue .... I'm using your image : 2014-01-07-wheezy-raspbian-2014-03-12-fbtft-master-firmware.zip

I've not done anything else with it, just a fresh image... do I need the one built into the kernel?

Andy

[notro]

This is what I get with that image:

Code: Select all

[email protected] ~ $ cat /boot/issue.txt
FBTFT image reference 2014-03-12
Raspberry Pi reference 2014-01-07 (armhf)
Generated using spindle, http://asbradbury.org/projects/spindle/, 0e00a4f, stage4-lxde-edu.qed

[email protected] ~ $ uname -a
Linux raspberrypi 3.10.33+ #1 PREEMPT Sat Mar 8 18:15:05 CET 2014 armv6l GNU/Linux

[email protected] ~ $ modinfo fb_ili9341
filename:       /lib/modules/3.10.33+/kernel/drivers/video/fbtft/fb_ili9341.ko
license:        GPL
author:         Christian Vogelgsang
description:    FB driver for the ILI9341 LCD display controller
alias:          platform:fb_ili9341
alias:          spi:fb_ili9341
srcversion:     739E7DD0F62B08CEF42BF9E
depends:        fbtft
intree:         Y
vermagic:       3.10.33+ preempt mod_unload modversions ARMv6

[fiskius]

Yikes!

Raspberry Pi reference 2013-05-25 (armhf)
Generated using spindle, http://asbradbury.org/projects/spindle/, 9c87329, stage 4-lxde-edu.qed

Sorry that's a totally newbie error, must have downloaded the newest image but still had the old one on the SD card. Well at least I learned 'cat' thats a new command for me. I see from the previous posts that driver is 11 months old and my image is 13 months, so I will try that out.

Really appreciate your help notro!

Andy

[fiskius]

OK almost there... just one final issue with 2 or 3 white lines across the width of the screen (in both orientations, console and lxde). Is that likely to be a hardware fault - I could have messed up it trying some different combinations of GPIOs....?



Andy

[notro]

I you change rotation and the lines stay, I would say it's a hardware fault.

[oatking]

Is there some way to have an automatic re-init if the display is (accidentally) disconnected and reconnected?

If I pull the display out and plug it back in all I get is a white screen (the backlight). I would like to keep all settings (e.g. console connected to the fb), and reinitialize the display.

Preferably in an automatic way, although I can live with a manual trigger (e.g. external button).
I'm not even sure if there's a good way to detect when the display is working as intended, even with MISO connected?

For reference, I have a 2.2" ili9341 based display.

[notro]

There is no builtin way to do this.
You need to rmmod fbtft_device and then load it again, loosing /dev/fb1 in the mean time.

[hasani]

Hi guys!
I think it's a great topic but high level! I have a nanopi-m1 board that has 40 GPIO pins similar to raspberry pi and Debian Jessie OS. Also I have the LCD that is mentioned in this topic. and want to connect int directly to my board.

But I am confusing and don't know how can I do it step-by-step! Is there any tutorial for that?