[SOLVED] VU7+ touch screen not working

Post Reply
Spada
Posts: 35
Joined: Tue Oct 18, 2016 1:23 am
languages_spoken: english
ODROIDs: C2, XU4
Has thanked: 1 time
Been thanked: 2 times
Contact:

[SOLVED] VU7+ touch screen not working

Post by Spada »

Hello everyone,

After a long time of not using my VU7+, yesterday I connected it to a newly flashed C2. The display shows the image, but it seems that the touch is not working. I know it worked in the past, but it is no longer working, for some reason. I've checked the forum for various fixes, but nothing has worked. Can you please advise what to check?

Ubuntu version & Kernel:

Code: Select all

odroid@odroid:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.6 LTS
Release:        20.04
Codename:       focal
odroid@odroid:~$ uname -a
Linux odroid 3.16.85-65 #1 SMP PREEMPT Mon Jan 18 13:32:38 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
odroid@odroid:~$
boot.ini file:

Code: Select all

odroid@odroid:~$ cat /media/boot/boot.ini
ODROIDC2-UBOOT-CONFIG

########################################################################
# Changes made to this are overwritten every time there's a new upgrade
# To make your changes permanent change it on
# boot.ini.default
# After changing it on boot.ini.default run the bootini command to
# rewrite this file with your personal permanent settings.
# Documentation: http://odroid.com/dokuwiki/doku.php?id=en:c2_persistent_bootini
########################################################################

# Possible screen resolutions
# Uncomment only a single Line! The line with setenv written.
# At least one mode must be selected.

# Custom modeline!
# To use custom modeline you need to disable all the below resolutions
# and setup your own!
# For more information check our wiki:
# http://odroid.com/dokuwiki/doku.php?id=en:c2_hdmi_autosetting
# Example below:
# setenv m "custombuilt"
# setenv modeline "1920,1200,154000,74040,60,1920,1968,2000,2080,1200,1202,1208,1235,1,0,1"

# Auto Detection of Monitor settings based on your Screen information
# See: http://odroid.com/dokuwiki/doku.php?id=en:c2_auto_detect_display
setenv display_autodetect "true"

# 480 Lines (720x480)
# setenv m "480i60hz" # Interlaced 60Hz
# setenv m "480i_rpt" # Interlaced for Rear Projection Televisions 60Hz
# setenv m "480p60hz" # 480 Progressive 60Hz
# setenv m "480p_rpt" # 480 Progressive for Rear Projection Televisions 60Hz

# 576 Lines (720x576)
# setenv m "576i50hz" # Interlaced 50Hz
# setenv m "576i_rpt" # Interlaced for Rear Projection Televisions 50Hz
# setenv m "576p50hz" # Progressive 50Hz
# setenv m "576p_rpt" # Progressive for Rear Projection Televisions 50Hz

# 720 Lines (1280x720)
# setenv m "720p50hz" # 50Hz
# setenv m "720p60hz" # 60Hz

# 1080 Lines (1920x1080)
# setenv m "1080i60hz" # Interlaced 60Hz
setenv m "1080p60hz" # Progressive 60Hz
# setenv m "1080i50hz" # Interlaced 50Hz
# setenv m "1080p50hz" # Progressive 50Hz
# setenv m "1080p24hz" # Progressive 24Hz

# 4K (3840x2160)
# setenv m "2160p30hz"    # Progressive 30Hz
# setenv m "2160p25hz"    # Progressive 25Hz
# setenv m "2160p24hz"    # Progressive 24Hz
# setenv m "smpte24hz"    # Progressive 24Hz SMPTE
# setenv m "2160p50hz"    # Progressive 50Hz
# setenv m "2160p60hz"    # Progressive 60Hz
# setenv m "2160p50hz420" # Progressive 50Hz with YCbCr 4:2:0 (Requires TV/Monitor that supports it)
# setenv m "2160p60hz420" # Progressive 60Hz with YCbCr 4:2:0 (Requires TV/Monitor that supports it)

### VESA modes ###
# setenv m "640x480p60hz"
# setenv m "800x480p60hz"
# setenv m "480x272p60hz"
# setenv m "480x320p60hz"
# setenv m "480x800p60hz"
# setenv m "800x600p60hz"
# setenv m "1024x600p60hz"
# setenv m "1024x768p60hz"
# setenv m "1280x800p60hz"
# setenv m "1280x1024p60hz"
# setenv m "1360x768p60hz"
# setenv m "1440x900p60hz"
# setenv m "1600x900p60hz"
# setenv m "1680x1050p60hz"
# setenv m "1600x1200p60hz"
# setenv m "1920x1200p60hz"
# setenv m "2560x1080p60hz"
# setenv m "2560x1440p60hz"
# setenv m "2560x1600p60hz"
# setenv m "3440x1440p60hz"

# HDMI BPP Mode
setenv m_bpp "32"
# setenv m_bpp "24"
# setenv m_bpp "16"

# HDMI DVI/VGA modes
# By default its set to HDMI, if needed change below.
# Uncomment only a single Line.
# setenv vout "dvi"
# setenv vout "vga"

# HDMI HotPlug Detection control
# Allows you to force HDMI thinking that the cable is connected.
# true = HDMI will believe that cable is always connected
# false = will let board/monitor negotiate the connection status
setenv hpd "true"
# setenv hpd "false"

# Monitor output
# Controls if HDMI PHY should output anything to the monitor
setenv monitor_onoff "false" # true or false

# Server Mode (aka. No Graphics)
# Setting nographics to 1 will disable all video subsystem
# This mode is ideal of server type usage. (Saves ~300Mb of RAM)
setenv nographics "0"

# Meson Timer
# 1 - Meson Timer
# 0 - Arch Timer
# Using meson_timer improves the video playback however it breaks KVM (virtualization).
# Using arch timer allows KVM/Virtualization to work however you'll experience poor video
setenv mesontimer "1"

# UHS (Ultra High Speed) MicroSD mode enable/disable
setenv disableuhs "false"

# MicroSD Card Detection enable/disable
# Force the MMC controlled to believe that a card is connected.
setenv mmc_removable "true"

# USB Multi WebCam tweak
# Only enable this if you use it.
setenv usbmulticam "false"

# Disable/Enable ODROID-VU7 Touchscreen
setenv disable_vu7 "false"

# Default Console Device Setting
setenv condev "console=ttyS0,115200n8 console=tty0"   # on both

# CPU Frequency / Cores control
###########################################
### WARNING!!! WARNING!!! WARNING!!!
# Before changing anything here please read the wiki entry:
# http://odroid.com/dokuwiki/doku.php?id=en:c2_set_cpu_freq
#
# MAX CPU's
# setenv maxcpus "1"
# setenv maxcpus "2"
# setenv maxcpus "3"
setenv maxcpus "4"

# MAX Frequency
# setenv max_freq "2016"  # 2.016GHz
# setenv max_freq "1944"  # 1.944GHz
# setenv max_freq "1944"  # 1.944GHz
# setenv max_freq "1920"  # 1.920GHz
# setenv max_freq "1896"  # 1.896GHz
# setenv max_freq "1752"  # 1.752GHz
# setenv max_freq "1680"  # 1.680GHz
# setenv max_freq "1656"  # 1.656GHz
setenv max_freq "1536"  # 1.536GHz



###########################################

# Boot Arguments
if test "${display_autodetect}" = "true"; then usb pwren; hdmitx edid; fi
if test "${m}" = "custombuilt"; then setenv cmode "modeline=${modeline}"; fi
if test "${disable_vu7}" = "false"; then setenv hid_quirks "usbhid.quirks=0x0eef:0x0005:0x0004"; fi

setenv bootargs "root=/dev/mmcblk0p2 rootwait rw ${condev} no_console_suspend hdmimode=${m} ${cmode} m_bpp=${m_bpp} vout=${vout} fsck.repair=yes net.ifnames=0 elevator=noop disablehpd=${hpd} max_freq=${max_freq} maxcpus=${maxcpus} monitor_onoff=${monitor_onoff} disableuhs=${disableuhs} mmc_removable=${mmc_removable} usbmulticam=${usbmulticam} ${hid_quirks}"

# Booting

setenv loadaddr "0x11000000"
setenv dtb_loadaddr "0x1000000"
setenv initrd_loadaddr "0x13000000"

fatload mmc 0:1 ${initrd_loadaddr} uInitrd
fatload mmc 0:1 ${loadaddr} Image
fatload mmc 0:1 ${dtb_loadaddr} meson64_odroidc2.dtb
fdt addr ${dtb_loadaddr}

if test "${mesontimer}" = "0"; then fdt rm /meson_timer; fdt rm /cpus/cpu@0/timer; fdt rm /cpus/cpu@1/timer; fdt rm /cpus/cpu@2/timer; fdt rm /cpus/cpu@3/timer; fi
if test "${mesontimer}" = "1"; then fdt rm /timer; fi

if test "${nographics}" = "1"; then fdt rm /reserved-memory; fdt rm /aocec; fi
if test "${nographics}" = "1"; then fdt rm /meson-fb; fdt rm /amhdmitx; fdt rm /picdec; fdt rm /ppmgr; fi
if test "${nographics}" = "1"; then fdt rm /meson-vout; fdt rm /mesonstream; fdt rm /meson-fb; fi
if test "${nographics}" = "1"; then fdt rm /deinterlace; fdt rm /codec_mm; fi

booti ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr}
odroid@odroid:~$
Journal logs (while disconnecting and reconnecting the USB cable from the VU7+ to the C2) and devices input:

Code: Select all

odroid@odroid:~$ journalctl -f
-- Logs begin at Sun 2018-01-28 15:58:17 UTC. --
Nov 20 07:02:18 odroid systemd[1]: Starting Time & Date Service...
Nov 20 07:02:18 odroid dbus-daemon[525]: [system] Successfully activated service                                                                                                                                                                                                                                              'org.freedesktop.timedate1'
Nov 20 07:02:18 odroid systemd[1]: Started Time & Date Service.
Nov 20 07:02:48 odroid systemd[1]: systemd-timedated.service: Succeeded.
Nov 20 07:12:16 odroid systemd[1]: Starting Cleanup of Temporary Directories...
Nov 20 07:12:16 odroid systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Nov 20 07:12:16 odroid systemd[1]: Finished Cleanup of Temporary Directories.
Nov 20 07:17:01 odroid CRON[1734]: pam_unix(cron:session): session opened for us                                                                                                                                                                                                                                             er root by (uid=0)
Nov 20 07:17:01 odroid CRON[1735]: (root) CMD (   cd / && run-parts --report /et                                                                                                                                                                                                                                             c/cron.hourly)
Nov 20 07:17:01 odroid CRON[1734]: pam_unix(cron:session): session closed for us                                                                                                                                                                                                                                             er root









Nov 20 07:28:07 odroid kernel: Disconnect cb-Host
Nov 20 07:28:07 odroid kernel: usb 2-1: USB disconnect, device number 2
Nov 20 07:28:07 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 07:28:07 odroid kernel: Disconnect cb-Host
Nov 20 07:28:08 odroid kernel: usb 2-1: new full-speed USB device number 3 using dwc_otg
Nov 20 07:28:08 odroid kernel: ERROR::dwc_otg_hcd_urb_enqueue:560: USB Connect status change processing
Nov 20 07:28:08 odroid kernel: ERROR::dwc_otg_hcd_urb_enqueue:560: USB Connect status change processing
Nov 20 07:28:08 odroid kernel: ERROR::dwc_otg_hcd_urb_enqueue:560: USB Connect status change processing
Nov 20 07:28:08 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021101
Nov 20 07:28:08 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 07:28:08 odroid kernel: Disconnect cb-Host
Nov 20 07:28:08 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 07:28:08 odroid kernel: Disconnect cb-Host
Nov 20 07:28:08 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 07:28:08 odroid kernel: Disconnect cb-Host
Nov 20 07:28:08 odroid kernel: Disconnect cb-Host
Nov 20 07:28:08 odroid kernel: Disconnect cb-Host
Nov 20 07:28:08 odroid kernel: Disconnect cb-Host
Nov 20 07:28:09 odroid kernel: Disconnect cb-Host
Nov 20 07:28:09 odroid kernel: Disconnect cb-Host
Nov 20 07:28:09 odroid kernel: Disconnect cb-Host
Nov 20 07:28:09 odroid kernel: Disconnect cb-Host
Nov 20 07:28:09 odroid kernel: Disconnect cb-Host
Nov 20 07:28:09 odroid kernel: Disconnect cb-Host
Nov 20 07:28:09 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 07:28:09 odroid kernel: Disconnect cb-Host
Nov 20 07:28:09 odroid kernel: Disconnect cb-Host
Nov 20 07:28:09 odroid kernel: Disconnect cb-Host
Nov 20 07:28:10 odroid kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Nov 20 07:28:10 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021101
Nov 20 07:28:10 odroid kernel: usb 2-1: new full-speed USB device number 4 using dwc_otg
Nov 20 07:28:10 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 07:28:10 odroid kernel: input: BYZHYYZHY By ZH851 as /devices/dwc2_a/usb2/2-1/2-1:1.0/0003:16B4:0703.0002/input/input3
Nov 20 07:28:10 odroid kernel: hid-multitouch 0003:16B4:0703.0002: input,hiddev0,hidraw0: USB HID v1.10 Mouse [BYZHYYZHY By ZH851] on usb-dwc2_a-1/input0
Nov 20 07:28:10 odroid mtp-probe[1762]: checking bus 2, device 4: "/sys/devices/dwc2_a/usb2/2-1"
Nov 20 07:28:10 odroid mtp-probe[1762]: bus: 2, device: 4 was not an MTP device
Nov 20 07:28:11 odroid kernel: Disconnect cb-Host
Nov 20 07:28:11 odroid kernel: usb 2-1: USB disconnect, device number 4
Nov 20 07:28:25 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 07:28:25 odroid kernel: Disconnect cb-Host
Nov 20 07:28:25 odroid kernel: usb 2-1: new full-speed USB device number 5 using dwc_otg
Nov 20 07:28:25 odroid kernel: ERROR::dwc_otg_hcd_urb_enqueue:560: USB Connect status change processing
Nov 20 07:28:25 odroid kernel: ERROR::dwc_otg_hcd_urb_enqueue:560: USB Connect status change processing
Nov 20 07:28:25 odroid kernel: ERROR::dwc_otg_hcd_urb_enqueue:560: USB Connect status change processing
Nov 20 07:28:25 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021101
Nov 20 07:28:25 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 07:28:25 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 07:28:26 odroid kernel: input: BYZHYYZHY By ZH851 as /devices/dwc2_a/usb2/2-1/2-1:1.0/0003:16B4:0703.0003/input/input4
Nov 20 07:28:26 odroid kernel: hid-multitouch 0003:16B4:0703.0003: input,hiddev0,hidraw0: USB HID v1.10 Mouse [BYZHYYZHY By ZH851] on usb-dwc2_a-1/input0
Nov 20 07:28:26 odroid mtp-probe[1786]: checking bus 2, device 5: "/sys/devices/dwc2_a/usb2/2-1"
Nov 20 07:28:26 odroid mtp-probe[1786]: bus: 2, device: 5 was not an MTP device
Nov 20 07:30:01 odroid CRON[1802]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 20 07:30:01 odroid CRON[1803]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Nov 20 07:30:01 odroid CRON[1802]: pam_unix(cron:session): session closed for user root
Nov 20 07:31:19 odroid systemd[1]: Started Run anacron jobs.
Nov 20 07:31:19 odroid anacron[1804]: Anacron 2.3 started on 2023-11-20
Nov 20 07:31:19 odroid anacron[1804]: Normal exit (0 jobs run)
Nov 20 07:31:19 odroid systemd[1]: anacron.service: Succeeded.
^C
odroid@odroid:~$  ls -l /dev/input*
total 0
drwxr-xr-x 2 root root      60 Nov 20 07:28 by-id
drwxr-xr-x 2 root root      60 Nov 20 07:28 by-path
crwxrwxrwx 1 root input 13, 64 Mar 27  2023 event0
crwxrwxrwx 1 root input 13, 65 Mar 27  2023 event1
crwxrwxrwx 1 root input 13, 66 Nov 20 07:28 event2
crw-rw---- 1 root input 13, 63 Mar 27  2023 mice
crw-rw---- 1 root input 13, 32 Nov 20 07:28 mouse0
odroid@odroid:~$

User avatar
joerg
Posts: 1957
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 200 times
Been thanked: 431 times
Contact:

Re: VU7+ touch screen not working

Post by joerg »

It seems that the wrong kernel modul is loaded: hidraw.
Try with usbhid quirks in boot.ini like this:
setenv hid_quirks "usbhid.quirks=0x16b4:0x0703:0x0004"

Spada
Posts: 35
Joined: Tue Oct 18, 2016 1:23 am
languages_spoken: english
ODROIDs: C2, XU4
Has thanked: 1 time
Been thanked: 2 times
Contact:

Re: VU7+ touch screen not working

Post by Spada »

Apologies for my lack of knowledge, this is what I did on the boot.ini file (commented out the line with the usbhid.quirks and added the new one). If that's not correct, can you please let me know how to do it?

Code: Select all

odroid@odroid:~$ cat /media/boot/boot.ini | grep quirks
#if test "${disable_vu7}" = "false"; then setenv hid_quirks "usbhid.quirks=0x0eef:0x0005:0x0004"; fi
if test "${disable_vu7}" = "false"; then setenv hid_quirks "usbhid.quirks=0x16b4:0x0703:0x0004"; fi
The problem is still present, but by the looks of the journalctl, it seems it's not loading anything(?). Below shows two disconnects/reconnects:

Code: Select all

Nov 20 09:32:33 odroid kernel: Disconnect cb-Host
Nov 20 09:32:33 odroid kernel: Disconnect cb-Host
Nov 20 09:32:34 odroid kernel: Disconnect cb-Host
Nov 20 09:32:34 odroid kernel: Disconnect cb-Host
Nov 20 09:32:34 odroid kernel: Disconnect cb-Host
Nov 20 09:32:34 odroid kernel: Disconnect cb-Host
Nov 20 09:32:34 odroid kernel: usb 2-1: USB disconnect, device number 2
Nov 20 09:32:37 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 09:32:37 odroid kernel: usb 2-1: new full-speed USB device number 3 using dwc_otg
Nov 20 09:32:37 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 09:32:37 odroid mtp-probe[1730]: checking bus 2, device 3: "/sys/devices/dwc2_a/usb2/2-1"
Nov 20 09:32:37 odroid mtp-probe[1730]: bus: 2, device: 3 was not an MTP device




Nov 20 09:33:35 odroid kernel: Disconnect cb-Host
Nov 20 09:33:35 odroid kernel: Disconnect cb-Host
Nov 20 09:33:35 odroid kernel: Disconnect cb-Host
Nov 20 09:33:35 odroid kernel: usb 2-1: USB disconnect, device number 3
Nov 20 09:33:40 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 09:33:40 odroid kernel: Disconnect cb-Host
Nov 20 09:33:40 odroid kernel: Disconnect cb-Host
Nov 20 09:33:40 odroid kernel: Disconnect cb-Host
Nov 20 09:33:40 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 09:33:41 odroid kernel: usb 2-1: new full-speed USB device number 4 using dwc_otg
Nov 20 09:33:41 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 09:33:41 odroid mtp-probe[1743]: checking bus 2, device 4: "/sys/devices/dwc2_a/usb2/2-1"
Nov 20 09:33:41 odroid mtp-probe[1743]: bus: 2, device: 4 was not an MTP device
Nov 20 09:33:41 odroid kernel: Disconnect cb-Host
^C
odroid@odroid:~$

Spada
Posts: 35
Joined: Tue Oct 18, 2016 1:23 am
languages_spoken: english
ODROIDs: C2, XU4
Has thanked: 1 time
Been thanked: 2 times
Contact:

Re: VU7+ touch screen not working

Post by Spada »

OK, so this just happened:

1. I changed back my boot.ini file (commented out the "usbhid.quirks=0x16b4:0x0703:0x0004" and enabled "usbhid.quirks=0x0eef:0x0005:0x0004"):

Code: Select all

odroid@odroid:~$ cat /media/boot/boot.ini | grep quirks
if test "${disable_vu7}" = "false"; then setenv hid_quirks "usbhid.quirks=0x0eef:0x0005:0x0004"; fi
#if test "${disable_vu7}" = "false"; then setenv hid_quirks "usbhid.quirks=0x16b4:0x0703:0x0004"; fi
2. Rebooted

3. I wanted to provide proof again that it's loading the "old" driver, therefore I removed the USB cable and added it back.


Code: Select all

Nov 20 09:59:55 odroid kernel: Disconnect cb-Host
Nov 20 09:59:55 odroid kernel: usb 2-1: USB disconnect, device number 2
Nov 20 09:59:55 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 09:59:55 odroid kernel: usb 2-1: new full-speed USB device number 3 using dwc_otg
Nov 20 09:59:55 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 09:59:55 odroid kernel: input: BYZHYYZHY By ZH851 as /devices/dwc2_a/usb2/2-1/2-1:1.0/0003:16B4:0703.0002/input/input3
Nov 20 09:59:55 odroid kernel: hid-multitouch 0003:16B4:0703.0002: input,hiddev0,hidraw0: USB HID v1.10 Mouse [BYZHYYZHY By ZH851] on usb-dwc2_a-1/input0
Nov 20 09:59:55 odroid mtp-probe[1736]: checking bus 2, device 3: "/sys/devices/dwc2_a/usb2/2-1"
Nov 20 09:59:55 odroid mtp-probe[1736]: bus: 2, device: 3 was not an MTP device



Nov 20 10:00:04 odroid kernel: Disconnect cb-Host
Nov 20 10:00:04 odroid kernel: Disconnect cb-Host
Nov 20 10:00:04 odroid kernel: usb 2-1: USB disconnect, device number 3
Nov 20 10:00:05 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 10:00:05 odroid kernel: Disconnect cb-Host
Nov 20 10:00:05 odroid kernel: usb 2-1: new full-speed USB device number 4 using dwc_otg
Nov 20 10:00:05 odroid kernel: ERROR::dwc_otg_hcd_urb_enqueue:560: USB Connect status change processing
Nov 20 10:00:05 odroid kernel: ERROR::dwc_otg_hcd_urb_enqueue:560: USB Connect status change processing
Nov 20 10:00:05 odroid kernel: ERROR::dwc_otg_hcd_urb_enqueue:560: USB Connect status change processing
Nov 20 10:00:05 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021101
Nov 20 10:00:05 odroid kernel: Disconnect cb-Host
Nov 20 10:00:05 odroid kernel: Disconnect cb-Host
Nov 20 10:00:05 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 10:00:05 odroid kernel: Disconnect cb-Host
Nov 20 10:00:05 odroid kernel: Disconnect cb-Host
Nov 20 10:00:05 odroid kernel: ERROR::dwc_otg_hcd_urb_enqueue:560: USB Connect status change processing
Nov 20 10:00:05 odroid kernel: ERROR::dwc_otg_hcd_urb_enqueue:560: USB Connect status change processing
Nov 20 10:00:05 odroid kernel: ERROR::dwc_otg_hcd_urb_enqueue:560: USB Connect status change processing
Nov 20 10:00:05 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 10:00:06 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 10:00:06 odroid kernel: Disconnect cb-Host








Nov 20 10:00:23 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 10:00:23 odroid kernel: usb 2-1: new full-speed USB device number 5 using dwc_otg
Nov 20 10:00:23 odroid kernel: dwc_otg: Indeed it is in host mode hprt0 = 00021501
Nov 20 10:00:23 odroid kernel: input: BYZHYYZHY By ZH851 as /devices/dwc2_a/usb2/2-1/2-1:1.0/0003:16B4:0703.0003/input/input4
Nov 20 10:00:23 odroid kernel: hid-multitouch 0003:16B4:0703.0003: input,hiddev0,hidraw0: USB HID v1.10 Mouse [BYZHYYZHY By ZH851] on usb-dwc2_a-1/input0
Nov 20 10:00:23 odroid mtp-probe[1762]: checking bus 2, device 5: "/sys/devices/dwc2_a/usb2/2-1"
Nov 20 10:00:23 odroid mtp-probe[1762]: bus: 2, device: 5 was not an MTP device




Nov 20 10:00:33 odroid kernel: [aml-i2s-dai]i2s dma ffffff80004bc000,phy addr 1560674304,mode 0,ch 2
Nov 20 10:00:33 odroid kernel: ----aml_hw_iec958_init,runtime->rate=44100,sample_rate=5--
Nov 20 10:00:33 odroid kernel: aml_set_spdif_clk rate
Nov 20 10:00:33 odroid kernel: share the same clock
Nov 20 10:00:33 odroid kernel: iec958 mode PCM16
Nov 20 10:00:33 odroid kernel: IEC958 16bit
Nov 20 10:00:33 odroid kernel: hdmitx: audio: aout notify rate 44100
Nov 20 10:00:33 odroid kernel: hdmitx: audio: aout notify size 16
Nov 20 10:00:33 odroid kernel: 958 with i2s
Nov 20 10:00:33 odroid kernel: aiu i2s playback enable
Nov 20 10:00:33 odroid kernel: audio_hw_958_enable 1
Nov 20 10:00:39 odroid kernel: aiu i2s playback disable
Nov 20 10:00:39 odroid kernel: audio_hw_958_enable 0


^C
odroid@odroid:~$
Now it works... No idea why, but happy to see it working. Thank you all for reading and helping, hopefully it will help others.
These users thanked the author Spada for the post:
joerg (Mon Nov 20, 2023 7:38 pm)

User avatar
mad_ady
Posts: 11755
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4 (HC1, HC2), C1+, C2, C4 (HC4), N1, N2, N2L, H2, H3+, Go, Go Advance, M1, M1S
Location: Bucharest, Romania
Has thanked: 656 times
Been thanked: 1197 times
Contact:

Re: VU7+ touch screen not working

Post by mad_ady »

Check to see if it works after a reboot. Some people reported they needed to unplug/replug the cable after a while. If touch stops working, the hotplug can be forced by software with uhubctl.
These users thanked the author mad_ady for the post:
Spada (Mon Nov 20, 2023 7:33 pm)

Spada
Posts: 35
Joined: Tue Oct 18, 2016 1:23 am
languages_spoken: english
ODROIDs: C2, XU4
Has thanked: 1 time
Been thanked: 2 times
Contact:

Re: VU7+ touch screen not working

Post by Spada »

Tested with reboot, still works. Good to know about the "uhubctl".

Spada
Posts: 35
Joined: Tue Oct 18, 2016 1:23 am
languages_spoken: english
ODROIDs: C2, XU4
Has thanked: 1 time
Been thanked: 2 times
Contact:

Re: VU7+ touch screen not working

Post by Spada »

Tried the VU7+ touch screen on Armbian and it doesn't work. Below are the software details.

Code: Select all

root@odroidc2:~# uname -a
Linux odroidc2 6.1.50-current-meson64 #2 SMP PREEMPT Wed Aug 30 14:11:13 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux
root@odroidc2:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.3 LTS
Release:        22.04
Codename:       jammy
root@odroidc2:~#
I created a /media/boot/boot.ini similar to Ubuntu (there was none existent), but that didn't help. Also, I checked /boot, but there is no boot.ini file there. Also tried to create /boot/boot.ini, but that still didn't help. Running "journalctl -f" during unplugging/plugging the USB cable doesn't show anything. Looks like boot.ini is completely ignored, any ideas?

User avatar
joerg
Posts: 1957
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 200 times
Been thanked: 431 times
Contact:

Re: VU7+ touch screen not working

Post by joerg »

On Armbian you need to edit /boot/armbianEnv.txt. But I am not sure how is called the env variable for usbhid quirks.

User avatar
odroid
Site Admin
Posts: 41864
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 3433 times
Been thanked: 1920 times
Contact:

Re: VU7+ touch screen not working

Post by odroid »

I don't think Armbian kernel has the customized Vu series touchscreen device driver by default.
In that case, you need to compile the driver after downloading dwav-usb-mt-1.0.0.tar.gz source code.
https://wiki.odroid.com/odroid-h3/appli ... er_sources

Spada
Posts: 35
Joined: Tue Oct 18, 2016 1:23 am
languages_spoken: english
ODROIDs: C2, XU4
Has thanked: 1 time
Been thanked: 2 times
Contact:

Re: VU7+ touch screen not working

Post by Spada »

OK, so I managed to install the driver, but I cannot disable the USB HID driver:

Code: Select all

odroid@odroidc2:~$ cat /sys/module/usbhid/parameters/quirks
(null),(null),(null),(null)
odroid@odroidc2:~$
I couldn't try the first method (to disable it via GRUB) as I don't believe Armbian is using it. Please correct and advise me if I'm wrong. The second method throws no errors, but still I get the above output. Any ideas where to look?

User avatar
mad_ady
Posts: 11755
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4 (HC1, HC2), C1+, C2, C4 (HC4), N1, N2, N2L, H2, H3+, Go, Go Advance, M1, M1S
Location: Bucharest, Romania
Has thanked: 656 times
Been thanked: 1197 times
Contact:

Re: VU7+ touch screen not working

Post by mad_ady »

If usbhid is build as a module you can blacklist it from being loaded automatically. But note that keyboard/mouse will stop working also:

Code: Select all

# cat /etc/modprobe.d/blacklist-usbhid.conf
blacklist usbhid

Spada
Posts: 35
Joined: Tue Oct 18, 2016 1:23 am
languages_spoken: english
ODROIDs: C2, XU4
Has thanked: 1 time
Been thanked: 2 times
Contact:

Re: VU7+ touch screen not working

Post by Spada »

Blacklisted it, but still no joy. When I run a "journalctl -f" while I unplug/plug the power of the VU7+, I don't see anything in the logs. I remember on Ubuntu I could see the VU7+ being detected or at least getting some messages, but not in this case. Is it possible that the OTG port is just providing power but no data capabilities?

Code: Select all

odroid@odroidc2:~$ journalctl  | grep -i usb1
Nov 23 10:37:13 odroidc2 kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
Nov 23 10:37:13 odroidc2 kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 23 10:37:13 odroidc2 kernel: usb usb1: Product: DWC OTG Controller
Nov 23 10:37:13 odroidc2 kernel: usb usb1: Manufacturer: Linux 6.1.50-current-meson64 dwc2_hsotg
Nov 23 10:37:13 odroidc2 kernel: usb usb1: SerialNumber: c9100000.usb
odroid@odroidc2:~$
Should the VU7+ be visible under lsusb, regardless if the driver is loaded or not?

Code: Select all

odroid@odroidc2:~$ lsusb
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
odroid@odroidc2:~$

User avatar
mad_ady
Posts: 11755
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4 (HC1, HC2), C1+, C2, C4 (HC4), N1, N2, N2L, H2, H3+, Go, Go Advance, M1, M1S
Location: Bucharest, Romania
Has thanked: 656 times
Been thanked: 1197 times
Contact:

Re: VU7+ touch screen not working

Post by mad_ady »

Yes, it should be visible even if it's unclaimed by a driver.
Note that vu7 has a microusb power port (only for power) and a data port (power+data). It should work with only the data port, but it stresses the C2's power supply in the long term (mine failed after ~3 years - a slow and agonizing death :P).
I think the vu7 came with a custom micro-usb to micro-usb cable, so it should work on the c2 microusb port.

Also, beware! At least the mainline kernel on C1 required that 2 usb devices need to be plugged into the bus before they were visible. So try the same with c2. Plug in a mouse/stick/whatever in the same bus as vu7 and reboot and see if both are visible.

Spada
Posts: 35
Joined: Tue Oct 18, 2016 1:23 am
languages_spoken: english
ODROIDs: C2, XU4
Has thanked: 1 time
Been thanked: 2 times
Contact:

Re: VU7+ touch screen not working

Post by Spada »

I think that the two microusb ports are only for the VU7A+ version, whereas I have VU7+. It's either that or I am really in need of a new pair of glasses as I cannot find the second microusb port.

The microusb to microusb cable should be the correct one, the one that came with the display. I am assuming that it is the correct cable since using the same cable the touchscreen is working fine on Ubuntu, but not on Armbian.

Is it correct to assume at this time that the OTG port may not be working correctly since my display is not detected?

User avatar
mad_ady
Posts: 11755
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4 (HC1, HC2), C1+, C2, C4 (HC4), N1, N2, N2L, H2, H3+, Go, Go Advance, M1, M1S
Location: Bucharest, Romania
Has thanked: 656 times
Been thanked: 1197 times
Contact:

Re: VU7+ touch screen not working

Post by mad_ady »

Yes, it's a possibility. Try with a usb-a to microusb cable

Spada
Posts: 35
Joined: Tue Oct 18, 2016 1:23 am
languages_spoken: english
ODROIDs: C2, XU4
Has thanked: 1 time
Been thanked: 2 times
Contact:

Re: VU7+ touch screen not working

Post by Spada »

I wanted to say a curse word here, but refrained at the last second. :) THANK YOU, connecting it to the regular USB/USB-A port made it work instantly! Thank you all, it works perfectly!

User avatar
mad_ady
Posts: 11755
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4 (HC1, HC2), C1+, C2, C4 (HC4), N1, N2, N2L, H2, H3+, Go, Go Advance, M1, M1S
Location: Bucharest, Romania
Has thanked: 656 times
Been thanked: 1197 times
Contact:

Re: VU7+ touch screen not working

Post by mad_ady »

Glad to hear it works. It may be that by default the second usb bus (used by the microusb port) is set in client mode and needs to be forced in host mode. You should be able to do it with some dtb wizardfy...

Post Reply

Return to “ODROID-VU”

Who is online

Users browsing this forum: No registered users and 2 guests