Problem with waterott 2.8" Display

Max2Play Home 2016 (en) Forums Max2Play on Raspberry PI Problem with waterott 2.8" Display

This topic contains 8 replies, has 2 voices, and was last updated by  Heiner Moderator 7 months ago.

Viewing 9 posts - 1 through 9 (of 9 total)
  • 3. January 2017 at 20:09 #25434

    Hi,

    I installed that display within webgui and in jivelite I downloaded the the design from bogdandimitru for 320×240. Unfortunately the screen does not show anything. It is lit up and touch seems to work, becaue I just pressed alittle and all of a sudden the player started a song. I have no clue where to look for. In Xorg.0.log I found this

    [  1284.314] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  1289.331] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  1294.403] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  1299.430] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  1304.446] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  1309.461] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  1314.477] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  1319.493] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  1324.509] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  1329.525] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  1334.542] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  1339.557] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    

    What else could I try?

    Regards, Heinzelrumpel

    3. January 2017 at 20:25 #25435

    hier mal etwas ausführlicher nach dem jivelite Neustart

    
    
    [  2558.566]    ABI class: X.Org ANSI C Emulation, version 0.4
    [  2558.567] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  2558.569] (==) FBDEV(0): Backing store enabled
    [  2558.570] (==) FBDEV(0): DPMS enabled
    [  2558.571] (==) RandR enabled
    [  2558.653] (II) SELinux: Disabled on system
    [  2558.664] (II) AIGLX: Screen 0 is not DRI2 capable
    [  2558.665] (EE) AIGLX: reverting to software rendering
    [  2559.050] (II) AIGLX: Loaded and initialized swrast
    [  2559.051] (II) GLX: Initialized DRISWRAST GL provider for screen 0
    [  2559.842] (II) config/udev: Adding input device ADS7846 Touchscreen (/dev/input/event0)
    [  2559.844] (**) ADS7846 Touchscreen: Applying InputClass "evdev touchscreen catchall"
    [  2559.847] (**) ADS7846 Touchscreen: Applying InputClass "Touchscreen"
    [  2559.849] (II) LoadModule: "evdev"
    [  2559.853] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [  2559.861] (II) Module evdev: vendor="X.Org Foundation"
    [  2559.947]    compiled for 1.17.2, module version = 2.9.2
    [  2559.948]    Module class: X.Org XInput Driver
    [  2559.948]    ABI class: X.Org XInput driver, version 21.0
    [  2559.948] (II) Using input driver 'evdev' for 'ADS7846 Touchscreen'
    [  2559.948] (**) ADS7846 Touchscreen: always reports core events
    [  2559.949] (**) evdev: ADS7846 Touchscreen: Device: "/dev/input/event0"
    [  2559.952] (--) evdev: ADS7846 Touchscreen: Vendor 0 Product 0
    [  2559.956] (--) evdev: ADS7846 Touchscreen: Found absolute axes
    [  2559.958] (--) evdev: ADS7846 Touchscreen: Found x and y absolute axes
    [  2559.960] (--) evdev: ADS7846 Touchscreen: Found absolute touchscreen
    [  2559.961] (**) Option "InvertX" "0"
    [  2559.964] (**) Option "InvertY" "1"
    [  2559.966] (**) Option "SwapAxes" "1"
    [  2559.968] (II) evdev: ADS7846 Touchscreen: Configuring as touchscreen
    [  2559.969] (**) Option "EmulateThirdButton" "1"
    [  2559.970] (**) Option "EmulateThirdButtonTimeout" "1500"
    [  2559.973] (**) Option "EmulateThirdButtonMoveThreshold" "30"
    [  2559.981] (**) evdev: ADS7846 Touchscreen: YAxisMapping: buttons 4 and 5
    [  2559.981] (**) evdev: ADS7846 Touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [  2559.983] (**) Option "config_info" "udev:/sys/devices/platform/soc/20204000.spi/spi_master/spi0/spi0.1/input/input0/event0"
    [  2559.985] (II) XINPUT: Adding extended input device "ADS7846 Touchscreen" (type: TOUCHSCREEN, id 6)
    [  2559.990] (II) evdev: ADS7846 Touchscreen: initialized for absolute axes.
    [  2559.994] (**) ADS7846 Touchscreen: (accel) keeping acceleration scheme 1
    [  2559.997] (**) ADS7846 Touchscreen: (accel) acceleration profile 0
    [  2559.999] (**) ADS7846 Touchscreen: (accel) acceleration factor: 2.000
    [  2560.001] (**) ADS7846 Touchscreen: (accel) acceleration threshold: 4
    [  2560.008] (II) config/udev: Adding input device ADS7846 Touchscreen (/dev/input/mouse0)
    [  2560.011] (**) ADS7846 Touchscreen: Applying InputClass "Touchscreen"
    [  2560.013] (II) No input driver specified, ignoring this device.
    [  2560.017] (II) This device may have been added with another device file.
    [  2560.078] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  2573.034] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  2578.045] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  2578.809] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  2583.063] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  2583.837] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  2588.077] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [  2588.852] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    
    
    13. January 2017 at 16:18 #25869

    Hi HeinzelRumpel,
    Sorry about the late response. I just tested 2,8″ waterott screen with a Raspberry Pi 3 and our newest image. I did, unfortunately, not encounter your error. Please try burning a fresh image, installing the RPi Display, selecting the 2,8″ installation, rebooting, selecting the QVGA skin installation in Jivelite, rebooting and check the output again. Our test Pi showed the correct skin immediately, but you might have to go to settings and select the skin that’s written in ALL CAPS.

    13. January 2017 at 20:04 #25910

    Hi,

    I did exactly as you described. Maybe the problem lies with in the fact, that I was not using an Pi 3. I digged out my Model B from 2012 and display of the same age. That Rassberry has lesser gpio pins than Pi3, so I suppose the watterott Display cannot be use with newer raspberries.

    18. January 2017 at 15:17 #26028

    Please try out a different Pi if this is possible to rule out yours as the source of error.

    18. January 2017 at 16:45 #26042

    I already did.

    18. January 2017 at 17:03 #26046

    So it worked on the Pi3?

    18. January 2017 at 22:53 #26110

    No, the Display is not made for PIN because of the ammount of pins. I just tested it on another Model B.

    20. January 2017 at 15:40 #26164

    As mentioned above, the display definitely fits on a Raspberry Pi 3. The very tight fit of the board is not a problem for its performance.

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.

Register here