Touch Screen issue on Beagleplay

General Discussion
1

I have connected my beagle play to a 7 inch HDMI LCD display from Odroid, the Vu7A+ and can’t get the touch screen to work.
Here is the message I get with lsusb -v

Bus 001 Device 005: ID 16b4:0705 iStation By ZH851
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x16b4 iStation
idProduct 0x0705
bcdDevice 2.00
iManufacturer 1 RPI_TOUCH
iProduct 2 By ZH851
iSerial 3 t4H3530F150
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0029
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 33
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 16
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 16

2

I have absolutely no clue in the world what is going on with this since we don’t have a config like that. This is my plan of action for getting it up.

  1. It appears you are missing a .ini or .config file
  2. Is the device tree configured properly?

Get a pi4 and see how they have it configured, this will get you started and make adjustments that are specific to the BP board.

3

It works with the odroid boards. It is not for RPI. I read that it got blocked as of kernel 5.4 and then someone made a patch for Odroid. Not sure if it was put upstream. If it uses the waveshare driver that would explain it. Waveshare apparently violated the GPL by having a binary blob, if they copied the waveshare board and use the same driver that would explain it.
I need to check the kernel. I have not done any change to it, I am using the debian that came with it, I am working on a pascal GUI program to use a can device and the NeoVI-RPI and want it to work for the beagleplay also. Intrepidcs provides the linux kernel for their RPI that is in the device so that should be transparent as my J1939 program will use the kernel module.
This touch screen issue is just an annoyance, my more important task is to get the CAN inferface up and running. I have to create a devicetree file for it if it doesn’t exist. From what I see in the schematic, it looks like I can bring up the CAN port on the click board connector so I don’t have to use the MCP2518FD click board.

Michel

4

If you get it going I am pretty sure that you will make BP users very happy if you post the fix.

Without good touch screen support the board does not have much hope of gaining solid traction. Competitors have out of the box touch screen support so those making the money on this board would benefit the most and thus should provide solid support for end users.

5

Once I figure out the fix for the touch screen I would publish the fix on my website.

I ordered a board from seeed with 5 CAN drivers for my beaglebone ai 64, I didn’t realize that 6 were available, I missed CAN0.

Michel