-
Notifications
You must be signed in to change notification settings - Fork 495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSD1963 problem #138
Comments
You are missing the init sequence. See #58 for examples |
And when I use RPi console: |
Ok, step by step:
|
Most displays are white when not initialized and turn black when the driver is loaded. |
Hi stml89, |
Hi notro and jamesdownsbell, https://www.dropbox.com/s/fo1428em5pq0exx/VIDEO0004.mp4 startx have you tried set the screen as a boot console Also what image are you using as your os? let me know if you want know more. |
Hey stml89, Edit : I just watched the video ,it does look like the screen is starting, what is dmesg putting out ? |
Hi jamesdownsbell, Now when I starting Notro's script: |
Hi stml89, |
Hi, what is dmesg putting out ? Are you getting anything on the screen? |
Hi smtl89, Yes to be honest that's what I would do. Just flash the sd with the image in the link I posted, and enter the commands in the post above Edit : |
Out of curiosity is the screen still staying black ? |
Another quick way to test is to use fbi image viewer. download an image; display to /dev/fb1; |
Hi stml89, |
Hi jamesdownsbell, Hi mwilliams03, i'm really upset.. |
Hi stml89, |
regwidth is the bit width of the register. For SSD1963 this is 16. |
There you go lol :) |
when I changed regwidth to buswidth, display flashes once, at RPi initialization Сontents of my files, could you please check it?
Very sorry for my stupid and noob questions... |
Hi stml89, |
Hi jamesdownsbell, |
Hi stml89, |
Thanks for the quick reply. |
Hi stml89, |
Hi jamesdownsbell, |
Closing issue since there has been no activity for more than 2 months. Reopen if needed. |
Hi notro,
I connected PRI with display( http://www.ebay.com/itm/4-3-TFT-LCD-Module-Display-Touch-Panel-Screen-PCB-Adapter-Build-in-SSD1963-/400556699371?pt=LH_DefaultDomain_0&hash=item5d430a2eeb ) and have problem.
If you have a time help me please.
connected as
LCD -> RaspberryPI
RST -> GPIO29
RS/DC -> GPIO2
WR -> GPIO31
RD -> 3.3V
LED_A -> 3.3V
CS -> GND
db00 -> GPIO11
db01 -> GPIO9
db02 -> GPIO10
db03 -> GPIO22
db04 -> GPIO27
db05 -> GPIO17
db06 -> GPIO4
db07 -> GPIO3
db08 -> GPIO7
db09 -> GPIO8
db10 -> GPIO25
db11 -> GPIO24
db12 -> GPIO23
db13 -> GPIO18
db14 -> GPIO14
db15 -> GPIO15
When I loaded:
sudo modprobe --first-time fbtft_device name=flexpfb debug=3 gpios=reset:29,dc:2,wr:31,db00:11,db01:9,db02:10,db03:22,db04:27,db05:17,db06:4,db07:3,db08:7,db09:8,db10:25,db11:24,db12:23,db13:18,db14:14,db15:15 rotate=0
tft display lights for one second then goes blank
pi@raspberrypi ~ $ FRAMEBUFFER=/dev/fb1 startx
xauth: timeout in locking authority file /home/pi/.Xauthority
X.Org X Server 1.12.4
Release Date: 2012-08-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-2-mx5 armv7l Debian
Current Operating System: Linux raspberrypi 3.12.21+ #1 PREEMPT Sat Jun 14 12:01:42 CEST 2014 armv6l
Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1776 bcm2708_fb.fbheight=952 bcm2708.boardrev=0xe bcm2708.serial=0xf38d989e smsc95xx.macaddr=B8:27:EB:8D:98:9E sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p6 rootfstype=ext4 elevator=deadline rootwait
Build Date: 18 December 2013 05:20:52PM
xorg-server 2:1.12.4-6+deb7u2 (Julien Cristau jcristau@debian.org)
Current version of pixman: 0.29.3
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Wed Jul 30 14:04:03 2014
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
FATAL: Module g2d_23 not found.
No protocol specified
Solution:
Disable option in /usr/share/X11/xorg.conf.d/99-fbturbo.conf
"#"Option "fbdev" "/dev/fb0"
Did not help
The text was updated successfully, but these errors were encountered: