Hi,
I had ByQDtech touchscreen working in Jetson Nano with Jetpack 4.2 without any problem. I have updated the Jetpack version to 4.3 and a problem happened. When I boot the system, the touchscreen starts working right but a couple of minutes later touch function doesn’t work. The jetson is not locked, if you connect a USB mouse, it works perfectly. I have updated to 4.4 and the same happens. With a Jetson TX2 I have the same problem.
I appreciate your help,
Thanks in advance
We don’t have experience to ByQDtech touchscreen.
Do you use this screen on nvidia devkit? What interface is this board using? Why is usb mouse related to this issue? Is your screen based on usb interface?
I use in nvidia devkit.
The interface is HDMI. The touch function is USB.
The USB mouse is related to this issue because as I told before, the interface of the touch function is USB. When it doesn’t work, you plug a USB optical mouse and it works.
Thanks
Could you share the kernel log from both jetpack4.2 and jetpack4.4?
In jetpack4.4, could you share the result of lsusb before and after you plug the usb mouse?
Hi,
At this moment, I have a jetson nano with jetpack 4.2 and a jetson TX2 with jetpack 4.3 that have the same problem with the touchscreen. I cannot update the jetpack because we are testing a solution for a project.
In jetson nano with jetpack 4.2, there is no problem with the touch screen and in jetson TX2 with jetpack 4.3, the problem happened I told you.
Attached, you find the kern.log for jetpack 4.2 in jetson nano and jetpack 4.3 in jetson TX2.
lsusb in jetpack 4.3 when the touch function was working:
vision@vision-tx2:~$ lsusb
Bus 002 Device 002: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 04d9:1702 Holtek Semiconductor, Inc. Keyboard LKS02
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 006: ID 0483:5750 STMicroelectronics LED badge – mini LED display – 11x44
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lsusb in jetpack 4.3 when the touch function stopped working and I plugged a USB mouse:
vision@vision-tx2:~$ lsusb
Bus 002 Device 002: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 045e:0797 Microsoft Corp. Optical Mouse 200
Bus 001 Device 005: ID 04d9:1702 Holtek Semiconductor, Inc. Keyboard LKS02
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 006: ID 0483:5750 STMicroelectronics LED badge – mini LED display – 11x44
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I appreciate your help,
Thanks
kern_jetpack42.log (177.8 KB) kern_jetpack43.log (1.7 MB)
Hi,
Can we just see one kernel log with your error instead of a long log from 10/5 09:43 to 10/6 8:01?
Hi,
Here you are the kernel log since I power on theTX2 until the error happened in the touch function and plug the USB optical mouse.
Regards
kern_jetpack4.3.log (101.5 KB)
Hi Jose,
How long did you have to wait for this “suddenly it cant work anymore”? Also, could you share how do you connect this panel on Nano or TX2 devkit?
Hi,
I have to wait between 1-2 minutes after power on. Please, attached you find a couple of picture where it is shown how the screen is connected to Nano and TX2.
Thanks
Hi,
On TX2, will it make difference if you plug the screen usb cable to the typeA port?
Hi,
No, there is no difference. I did and the behaviour is the same.
Thanks
Please follow similar method on TX2 to reset the power of usb port and see if it would be back to life.
Hi,
What is the equivalent to regulator.35 in TX2?.
vision@vision-tx2:~$ ls -l /sys/class/regulator/
total 0
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.0 → …/…/devices/platform/reg-dummy/regulator/regulator.0
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.1 → …/…/devices/fixed-regulators/fixed-regulators:regulator@0/regulator/regulator.1
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.10 → …/…/devices/bpmp_i2c/i2c-4/4-003c/max77620-pmic/regulator/regulator.10
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.11 → …/…/devices/bpmp_i2c/i2c-4/4-003c/max77620-pmic/regulator/regulator.11
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.12 → …/…/devices/bpmp_i2c/i2c-4/4-003c/max77620-pmic/regulator/regulator.12
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.13 → …/…/devices/bpmp_i2c/i2c-4/4-003c/max77620-pmic/regulator/regulator.13
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.14 → …/…/devices/bpmp_i2c/i2c-4/4-003c/max77620-pmic/regulator/regulator.14
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.15 → …/…/devices/bpmp_i2c/i2c-4/4-003c/max77620-pmic/regulator/regulator.15
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.16 → …/…/devices/fixed-regulators/fixed-regulators:regulator@1/regulator/regulator.16
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.17 → …/…/devices/fixed-regulators/fixed-regulators:regulator@2/regulator/regulator.17
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.18 → …/…/devices/fixed-regulators/fixed-regulators:regulator@3/regulator/regulator.18
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.19 → …/…/devices/fixed-regulators/fixed-regulators:regulator@4/regulator/regulator.19
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.2 → …/…/devices/fixed-regulators/fixed-regulators:regulator@101/regulator/regulator.2
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.20 → …/…/devices/fixed-regulators/fixed-regulators:regulator@5/regulator/regulator.20
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.21 → …/…/devices/fixed-regulators/fixed-regulators:regulator@6/regulator/regulator.21
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.22 → …/…/devices/fixed-regulators/fixed-regulators:regulator@7/regulator/regulator.22
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.23 → …/…/devices/fixed-regulators/fixed-regulators:regulator@8/regulator/regulator.23
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.24 → …/…/devices/fixed-regulators/fixed-regulators:regulator@9/regulator/regulator.24
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.25 → …/…/devices/fixed-regulators/fixed-regulators:regulator@10/regulator/regulator.25
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.26 → …/…/devices/fixed-regulators/fixed-regulators:regulator@11/regulator/regulator.26
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.27 → …/…/devices/fixed-regulators/fixed-regulators:regulator@12/regulator/regulator.27
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.28 → …/…/devices/fixed-regulators/fixed-regulators:regulator@13/regulator/regulator.28
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.29 → …/…/devices/fixed-regulators/fixed-regulators:regulator@14/regulator/regulator.29
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.3 → …/…/devices/bpmp_i2c/i2c-4/4-003c/max77620-pmic/regulator/regulator.3
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.30 → …/…/devices/fixed-regulators/fixed-regulators:regulator@15/regulator/regulator.30
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.31 → …/…/devices/fixed-regulators/fixed-regulators:regulator@16/regulator/regulator.31
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.32 → …/…/devices/fixed-regulators/fixed-regulators:regulator@17/regulator/regulator.32
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.33 → …/…/devices/fixed-regulators/fixed-regulators:regulator@18/regulator/regulator.33
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.34 → …/…/devices/fixed-regulators/fixed-regulators:regulator@118/regulator/regulator.34
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.4 → …/…/devices/bpmp_i2c/i2c-4/4-003c/max77620-pmic/regulator/regulator.4
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.5 → …/…/devices/bpmp_i2c/i2c-4/4-003c/max77620-pmic/regulator/regulator.5
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.6 → …/…/devices/bpmp_i2c/i2c-4/4-003c/max77620-pmic/regulator/regulator.6
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.7 → …/…/devices/bpmp_i2c/i2c-4/4-003c/max77620-pmic/regulator/regulator.7
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.8 → …/…/devices/bpmp_i2c/i2c-4/4-003c/max77620-pmic/regulator/regulator.8
lrwxrwxrwx 1 root root 0 oct 7 07:52 regulator.9 → …/…/devices/bpmp_i2c/i2c-4/4-003c/max77620-pmic/regulator/regulator.9
The type A port on devkit should use regulator@5.
The regulators for usb ports on devkit are #4,5 and 17.
I tried disabled/enabled regulator@5 and the touch function still doesn’t work.
Regards
There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks
Could you use usb mouse to verify regulator@5 controls the type A port to make sure we didn’t make a mistake here?
Hi, I have exactly the same problem with my Jetson Nano and JetPack 4. After 1-2 mins, the touch screen stops with a screen warning.
Hi tarribas2009,
Please help to open a new topic with more details if it’s still an issue. Thanks
Hi i have this issue too. From the system power up, then 1-2 min and not working anymore, until reboot
Here is a syslog cut for the related error. the screen powered via touch-USBport.
syslog.txt (8.6 KB)
Maybe i have a solution what worked for me. I use it now for 10min and no issue.
So the problem is that it uses STm device with 5750 pid what is a led badge, so fwupd recognizes it and try to put to fwupd mode. That is the problem, in this point, touch not communicating.
Solution:
sudo apt remove fwupd
or stop service somehow :)
fwupd is an automatic firmware upgrader program, it checks the vid:pid combo and try to upgrade firmware to the latest.
