Hi,
since today the PiTFT is my own.
On my PI I have installed the current available 2014-01-07-wheezy-raspbian image.
I have installed the software step by step as you described in you homepage.
During installation - everything is working well till i should start X-Window.
The screen is goint to black - and nothing happens more.
Only a black screen.
Please be so kind and help me
Thx
Uwe
Problem with PiTFT MiniKit
Moderators: adafruit_support_bill, adafruit
Forum rules
Talk about Adafruit Raspberry Pi® accessories! Please do not ask for Linux support, this is for Adafruit products only! For Raspberry Pi help please visit: http://www.raspberrypi.org/phpBB3/
Talk about Adafruit Raspberry Pi® accessories! Please do not ask for Linux support, this is for Adafruit products only! For Raspberry Pi help please visit: http://www.raspberrypi.org/phpBB3/
- pkourany
- Posts: 51
- Joined: Wed Nov 27, 2013 12:57 pm
Re: Problem with PiTFT MiniKit
There is an entire tutorial for this product at http://learn.adafruit.com/adafruit-pitf ... i/overview.
Have fun!
Have fun!
-
- Posts: 6
- Joined: Thu Feb 06, 2014 7:07 pm
Re: Problem with PiTFT MiniKit
Thank you - but I have done all steps from this manual without success.
The screen is black - nothing else!
Should the software run under the Wheezy image from Januar 2014?
The screen is black - nothing else!
Should the software run under the Wheezy image from Januar 2014?
- Franklin97355
- Posts: 23910
- Joined: Mon Apr 21, 2008 2:33 pm
Re: Problem with PiTFT MiniKit
No success on any of them or did some of them work?but I have done all steps from this manual without success.
I guess the next thing would be some large, clear pictures, front and back.
-
- Posts: 6
- Joined: Thu Feb 06, 2014 7:07 pm
Re: Problem with PiTFT MiniKit
sudo modprobe spi-bcm2708
sudo modprobe fbtft_device name=adafruitts rotate=90
export FRAMEBUFFER=/dev/fb1
startx
After these steps - black screen - X-Window is not visible on the TFT.
sudo modprobe fbtft_device name=adafruitts rotate=90
export FRAMEBUFFER=/dev/fb1
startx
After these steps - black screen - X-Window is not visible on the TFT.
-
- Posts: 6
- Joined: Thu Feb 06, 2014 7:07 pm
Re: Problem with PiTFT MiniKit
ok - one other strage behavior!
I installed the Rasp-Wheezy image new. Updated the system - installed all neccessary driver and the screen is white. No reaction - no switching to black or something else.
At this point I don't know what to do - the best is I send back this monitor.
I installed the Rasp-Wheezy image new. Updated the system - installed all neccessary driver and the screen is white. No reaction - no switching to black or something else.
At this point I don't know what to do - the best is I send back this monitor.
-
- Posts: 6
- Joined: Thu Feb 06, 2014 7:07 pm
Re: Problem with PiTFT MiniKit
This is what was displayed on putty after installing all drivers and starting X-Window.
Normally, X-Window should now be visibl on the TFT.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
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.6.11+ #26 PREEMPT Tue Nov 26 18:19:51 SGT 2013 armv6l
Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708.boardrev=0xe bcm2708.serial=0xfc3e1739 smsc95xx.macaddr=B8:27:EB:3E:17:39 sdhci-bcm2708.emmc_clock_freq=100000000 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/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
Build Date: 18 December 2013 05:20:52PM
xorg-server 2:1.12.4-6+deb7u2 (Julien Cristau <[email protected]>)
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.0.log", Time: Fri Feb 7 15:30:28 2014
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
FATAL: Module g2d_23 not found.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
At the moment, I am very frustrated!
Normally, X-Window should now be visibl on the TFT.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
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.6.11+ #26 PREEMPT Tue Nov 26 18:19:51 SGT 2013 armv6l
Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708.boardrev=0xe bcm2708.serial=0xfc3e1739 smsc95xx.macaddr=B8:27:EB:3E:17:39 sdhci-bcm2708.emmc_clock_freq=100000000 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/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
Build Date: 18 December 2013 05:20:52PM
xorg-server 2:1.12.4-6+deb7u2 (Julien Cristau <[email protected]>)
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.0.log", Time: Fri Feb 7 15:30:28 2014
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
FATAL: Module g2d_23 not found.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
At the moment, I am very frustrated!
-
- Posts: 6
- Joined: Thu Feb 06, 2014 7:07 pm
Re: Problem with PiTFT MiniKit
this one says dmesg:
159.053829] fbtft_device: Setting pin 24 to 2
[ 159.130848] stmpe-spi spi0.1: unknown chip id: 0xffff
[ 159.130896] stmpe-spi: probe of spi0.1 failed with error -22
[ 159.130927] fbtft_device: Deleting spi0.0 (spi0.0)
[ 159.131515] fbtft_device: GPIOS used by 'adafruitts':
[ 159.131537] fbtft_device: 'dc' = GPIO25
[ 159.131546] fbtft_device: SPI devices registered:
[ 159.131562] fbtft_device: stmpe610 spi0.1 500kHz 8 bits mode=0x00
[ 159.131575] fbtft_device: fb_ili9340 spi0.0 16000kHz 8 bits mode=0x00
[ 159.402577] graphics fb1: fb_ili9340 frame buffer, 320x240, 150 KiB video memory, 16 KiB buffer memory, fps=20, spi0.0 at 16 MHz
I think the screen is broken!
159.053829] fbtft_device: Setting pin 24 to 2
[ 159.130848] stmpe-spi spi0.1: unknown chip id: 0xffff
[ 159.130896] stmpe-spi: probe of spi0.1 failed with error -22
[ 159.130927] fbtft_device: Deleting spi0.0 (spi0.0)
[ 159.131515] fbtft_device: GPIOS used by 'adafruitts':
[ 159.131537] fbtft_device: 'dc' = GPIO25
[ 159.131546] fbtft_device: SPI devices registered:
[ 159.131562] fbtft_device: stmpe610 spi0.1 500kHz 8 bits mode=0x00
[ 159.131575] fbtft_device: fb_ili9340 spi0.0 16000kHz 8 bits mode=0x00
[ 159.402577] graphics fb1: fb_ili9340 frame buffer, 320x240, 150 KiB video memory, 16 KiB buffer memory, fps=20, spi0.0 at 16 MHz
I think the screen is broken!
- adafruit_support_mike
- Posts: 67446
- Joined: Thu Feb 11, 2010 2:51 pm
Re: Problem with PiTFT MiniKit
The 'unknown chip ID' line is normal. You're probably seeing the effects of a known incompatibility between the PiTFT and recent versions of Wheezy.
About a month ago, the RasPi Foundation made a new, hardware accelerated framebuffer the default for handling all video data. The PiTFT driver was written to work with the older framebuffer, and we haven't gotten one that works with the accelerated version working as reliably as we want yet (the change kind of caught us by surprise).
the good news is that the old framebuffer is still included in the latest versions of Wheezy, so all you have to do is tell the OS /not/ to use the new one. We've recently added instructions on how to do that to the PiTFT tutorial:
About a month ago, the RasPi Foundation made a new, hardware accelerated framebuffer the default for handling all video data. The PiTFT driver was written to work with the older framebuffer, and we haven't gotten one that works with the accelerated version working as reliably as we want yet (the change kind of caught us by surprise).
the good news is that the old framebuffer is still included in the latest versions of Wheezy, so all you have to do is tell the OS /not/ to use the new one. We've recently added instructions on how to do that to the PiTFT tutorial:
If you have a version of Raspbian more recent than Sept. 2013, you'll need to turn off the accelerated X framebuffer here, run "sudo mv /usr/share/X11/xorg.conf.d/99-fbturbo.conf ~" to remove the accelerated X buffer and save it in your home directory
-
- Posts: 2
- Joined: Tue Feb 25, 2014 1:00 pm
Re: Problem with PiTFT MiniKit
when I was trying this one :adafruit_support_mike wrote:The 'unknown chip ID' line is normal. You're probably seeing the effects of a known incompatibility between the PiTFT and recent versions of Wheezy.
About a month ago, the RasPi Foundation made a new, hardware accelerated framebuffer the default for handling all video data. The PiTFT driver was written to work with the older framebuffer, and we haven't gotten one that works with the accelerated version working as reliably as we want yet (the change kind of caught us by surprise).
the good news is that the old framebuffer is still included in the latest versions of Wheezy, so all you have to do is tell the OS /not/ to use the new one. We've recently added instructions on how to do that to the PiTFT tutorial:
If you have a version of Raspbian more recent than Sept. 2013, you'll need to turn off the accelerated X framebuffer here, run "sudo mv /usr/share/X11/xorg.conf.d/99-fbturbo.conf ~" to remove the accelerated X buffer and save it in your home directory
"sudo mv /usr/share/X11/xorg.conf.d/99-fbturbo.conf ~"
it said "command not found
I downloaded raspbian yesterday
- adafruit_support_mike
- Posts: 67446
- Joined: Thu Feb 11, 2010 2:51 pm
Re: Problem with PiTFT MiniKit
Hunh.. that's wierd. According to the error the system can't find either the `sudo` or `mv` commands.
What do you get from:
What do you get from:
Code: Select all
which sudo
which mv
-
- Posts: 1
- Joined: Mon Mar 17, 2014 12:38 pm
Re: Problem with PiTFT MiniKit
i am facing the same problem:
when I was trying this one :
"sudo mv /usr/share/X11/xorg.conf.d/99-fbturbo.conf ~"
it said "no such file and directory"
can you help solve this?
when I was trying this one :
"sudo mv /usr/share/X11/xorg.conf.d/99-fbturbo.conf ~"
it said "no such file and directory"
can you help solve this?
- adafruit_support_mike
- Posts: 67446
- Joined: Thu Feb 11, 2010 2:51 pm
Re: Problem with PiTFT MiniKit
A "no such file" error means you asked it to move something that didn't exist.
In this case, you should be able to ignore the error and move on. The whole point of that command is to remove a file that causes trouble, so if there's no file there's no problem.
In this case, you should be able to ignore the error and move on. The whole point of that command is to remove a file that causes trouble, so if there's no file there's no problem.
-
- Posts: 1
- Joined: Thu Apr 03, 2014 10:16 pm
Re: Problem with PiTFT MiniKit
I've been having the exact same problem with the TFT.
Is there a solution to this problem?
when I type:
"sudo mv /usr/share/X11/xorg.conf.d/99-fbturbo.conf ~"
Response:
mv: cannot state "/usr/share/X11/xorg.conf.d/99-fbturbo.conf": No such file or directory
when I type:
which sudo
Response:
/usr/bin/sudo
when I type:
which mv
Response:
/bin/mv
when I type:
dmesg
Response:
[ 92.176222] stmpe-spi spi0.1: unknown chip id: 0x00
And whenever i type the startx command my display is frozen on a black screen
Thanks
Is there a solution to this problem?
when I type:
"sudo mv /usr/share/X11/xorg.conf.d/99-fbturbo.conf ~"
Response:
mv: cannot state "/usr/share/X11/xorg.conf.d/99-fbturbo.conf": No such file or directory
when I type:
which sudo
Response:
/usr/bin/sudo
when I type:
which mv
Response:
/bin/mv
when I type:
dmesg
Response:
[ 92.176222] stmpe-spi spi0.1: unknown chip id: 0x00
And whenever i type the startx command my display is frozen on a black screen
Thanks
- fransko
- Posts: 13
- Joined: Fri Mar 28, 2014 12:10 pm
Re: Problem with PiTFT MiniKit
i have the same problem!!!
Forum rules
Talk about Adafruit Raspberry Pi® accessories! Please do not ask for Linux support, this is for Adafruit products only! For Raspberry Pi help please visit: http://www.raspberrypi.org/phpBB3/
Talk about Adafruit Raspberry Pi® accessories! Please do not ask for Linux support, this is for Adafruit products only! For Raspberry Pi help please visit: http://www.raspberrypi.org/phpBB3/