You are not logged in.

#1 2020-12-16 15:12:16

fran42
Member
Registered: 2020-11-16
Posts: 57

Strange DLP connection with RPI

Hi,

I am using nanodlp with a DLP light projector (wintech PRO6500) and a raspberry 4.

I have seen that the raspberry allows me to define /dev/ttyAMA0 referring to the projector. But /dev/ttyAMA0 already exists with the projector unplugged. Is it possible that that once the node is generated (when plugged in for first time) it remains present?

Also, it is strange, because with that address I can turn on and off the projector without getting any error, or at least the raspberry thinks I can do it, but no real result is happening. I mean if I have the light ON and I turn OFF the projector the light will not turn off.
For doing this I have to turn on the projector with the computer, and leave the light ON and then connect it to the raspberry, then I can control if I want to display an image or not with the raspberry, but it has no relation with the TURN ON or TURN OFF of the projector.

I have (* 0 IR 001) and (*0 IR 002) as commands to turn ON and OFF the display. Could it be that /dev/ttyAMA0 is the correct address but I have wrong codes?

I have tried controlling the projector with other addresses that are generated while connecting the projector, but I get the following error in the RPI software:
1.    Error – Projector - USB port could not be activated is a directory if I use /dev/usb
2.    Error – Projector - USB port could not be activated Invalid serial port if I use /dev/hidraw0

And I can choose between the following communication types, but none of them makes a better difference:
•    Disabled
•    USB / Serial Port – ASCII (\r\n)
•    USB / Serial Port – ASCII (\r)
•    USB / Serial Port – ASCII (\n)
•    USB / Serial Port – Binary
•    Execution Only

Do you think that /dev/ttyAMA0 can be the real address of the projector? I can only explain that if I have the wrong codes for turning ON and OFF the projector. And so the raspberry sees no error because is sending a command to the projector (correct address) and no result is occurring because of the wrong code.

If I do ‘dmesg’ in the raspberry I get this about the projector:
[    2.319611] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.322393] usb 1-1.1: Product: DLPC900
[    2.325120] usb 1-1.1: Manufacturer: Texas Instruments Inc.
[    2.327838] usb 1-1.1: SerialNumber: C900
[    2.347778] hid-generic 0003:0451:C900.0001: hiddev96,hidraw0: USB HID v1.11 Device [Texas Instruments Inc. DLPC900] on usb-0000:01:00.0-1.1/input0
[    2.353106] usbhid 1-1.1:1.1: couldn't find an input interrupt endpoint

Here it seems that it is associated with /dev/hidraw0 and not /dev/ttyAMA0. But there is a final error.

What do you think about all this?

Thank you very much!
Francesc

Offline

#2 2020-12-17 10:11:23

Shahin
Administrator
Registered: 2016-02-17
Posts: 3,400

Re: Strange DLP connection with RPI

Maybe ttyAMA0 is a normal file created by mistake, then it should choose ttyAMA1.
Use lsusb verify if the appears when you connect and disappear when you disconnect it.

Offline

#3 2020-12-17 10:19:11

fran42
Member
Registered: 2020-11-16
Posts: 57

Re: Strange DLP connection with RPI

Hi,

I don't have any ttyAMA1.
I already checked and the node ttyAMA0 already exists with the projector unplugged. So that is what makes me think maybe it is not the projector, what else could it be with a name like that?
Or maybe it is the projector and the node remains even when I unplug the projector?


Thanks

Offline

#4 2020-12-17 17:44:16

Shahin
Administrator
Registered: 2016-02-17
Posts: 3,400

Re: Strange DLP connection with RPI

Use "lsusb"

Offline

#5 2020-12-21 08:58:46

fran42
Member
Registered: 2020-11-16
Posts: 57

Re: Strange DLP connection with RPI

WITHOUT THE PROJECTOR:

pi@raspberrypi:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 2341:0010 Arduino SA Mega 2560 (CDC ACM)
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


WITH THE PROJECTOR:

pi@raspberrypi:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 2341:0010 Arduino SA Mega 2560 (CDC ACM)
Bus 001 Device 004: ID 0451:c900 Texas Instruments, Inc.
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

How can this help?

Offline

#6 2020-12-21 09:50:29

fran42
Member
Registered: 2020-11-16
Posts: 57

Re: Strange DLP connection with RPI

Do you think it is possible I have to change to "mUVe3d" version in IP/printer/distro/change?

Offline

#7 2020-12-21 21:05:13

Shahin
Administrator
Registered: 2016-02-17
Posts: 3,400

Re: Strange DLP connection with RPI

No it would not make difference.
Try ls /dev/tty* before and after connecting the projector.

Offline

#8 2020-12-22 00:20:53

fran42
Member
Registered: 2020-11-16
Posts: 57

Re: Strange DLP connection with RPI

There is no /dev/tty* appearing when connecting the projector.
When checking the devices with and without the projector the only nodes that appear are /dev/usb (which is a directory) and /dev/hidraw0 (which is a serial, but doesn't work for turning on and off the projector).

Whith /dev/ttyAMA0 the projector accepts the orders but does not turn on or off in reality.


what are exactly the mUVe3D profiles? I read that it might have a firmware or something like that?

My projector is like this one: https://www.nanodlp.com/forum/viewtopic.php?id=737
I see you have solved some problems with it before.

Could it be something about the version of nanodlp? Or about the raspberry?

Offline

#9 2020-12-22 10:38:02

fran42
Member
Registered: 2020-11-16
Posts: 57

Re: Strange DLP connection with RPI

This problem I get when I debug "[    2.353106] usbhid 1-1.1:1.1: couldn't find an input interrupt endpoint" what does it stand for?
Maybe solving this the projector would work properly.

Offline

#10 2020-12-22 12:55:23

fran42
Member
Registered: 2020-11-16
Posts: 57

Re: Strange DLP connection with RPI

I attach my comand.txt, the problem should come from here right?
Maybe you see something that don't make sense to you.


# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (force DMT 1920x1080 @60Hz)
hdmi_group=2
hdmi_mode=82

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
disable_camera_led=1
hdmi_pixel_encoding=2
start_x=1
gpu_mem=128
enable_uart=1

Offline

#11 2020-12-22 14:13:20

fran42
Member
Registered: 2020-11-16
Posts: 57

Re: Strange DLP connection with RPI

I have seen that /dev/ttyAMA0 already appears while doing 'dmesg' without the projector connected, in the Arduino Mega 2560.
So it cannot be the projector from Texas Instruments right? Or maybe I have to call it from here?


[    2.324347] usb 1-1.3: New USB device found, idVendor=2341, idProduct=0010, bc  Device= 0.01
[    2.327111] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=220
[    2.329865] usb 1-1.3: Product: Arduino Mega 2560
[    2.332635] usb 1-1.3: Manufacturer: Arduino (www.arduino.cc)
[    2.335363] usb 1-1.3: SerialNumber: 5563231353835140B092
[    2.367121] systemd[1]: Set hostname to <raspberrypi>.
[    3.002949] random: systemd: uninitialized urandom read (16 bytes read)
[    3.015705] random: systemd: uninitialized urandom read (16 bytes read)
[    3.024019] systemd[1]: Listening on fsck to fsckd communication Socket.
[    3.031074] random: systemd: uninitialized urandom read (16 bytes read)
[    3.034157] systemd[1]: Listening on initctl Compatibility Named Pipe.
[    3.041097] systemd[1]: Reached target Swap.
[    3.048275] systemd[1]: Listening on udev Kernel Socket.
[    3.055513] systemd[1]: Started Dispatch Password Requests to Console Director y Watch.
[    3.063478] systemd[1]: Listening on Journal Socket.
[    3.070502] systemd[1]: Condition check resulted in Kernel Module supporting R PCSEC_GSS being skipped.
[    3.843973] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    3.949185] systemd-journald[126]: Received request to flush runtime journal f rom PID 1
[    4.458142] rpivid-mem feb00000.hevc-decoder: rpivid-hevcmem initialised: Registers at 0xfeb00000 length 0x00010000
[    4.467525] rpivid-mem feb10000.rpivid-local-intc: rpivid-intcmem initialised:  Registers a 0xfeb10000 length 0x00001000
[    4.469405] rpivid-mem feb20000.h264-decoder: rpivid-h264mem initialised: Registers at 0xfeb20000 length 0x00010000
[    4.469863] rpivid-mem feb30000.vp9-decoder: rpivid-vp9mem initialised: Registers at 0xfeb30000 length 0x00010000
[    4.504715] snd_bcm2835: module is from the staging directory, the quality is  unknown, you have been warned.
[    4.507652] vc_sm_cma: module is from the staging directory, the quality is un known, you have been warned.
[    4.509809] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[    4.509833] [vc_sm_connected_init]: start
[    4.512127] mc: Linux media interface: v0.10
[    4.518606] [vc_sm_connected_init]: installed successfully
[    4.539166] bcm2835_audio bcm2835_audio: card created with 4 channels
[    4.544468] bcm2835_audio bcm2835_audio: card created with 4 channels
[    4.549944] videodev: Linux video capture interface: v2.00
[    4.587420] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    4.588623] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    4.593027] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[    4.596126] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[    4.606446] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
[    4.871766] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0
[    4.913844] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
[    4.918582] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    4.920474] usbcore: registered new interface driver cdc_acm
[    4.920489] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    5.031966] vc4-drm gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4])
[    5.031987] checking generic (3e402000 7f8000) vs hw (0 ffffffffffffffff)
[    5.032001] fb0: switching to vc4drmfb from simple
[    5.034117] Console: switching to colour dummy device 80x30
[    5.034409] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    5.034423] [drm] No driver support for vblank timestamp query.
[    5.034434] [drm] Setting vblank_disable_immediate to false because get_vblank_timestamp == NULL
[    5.040107] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1
[    5.063607] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    5.138623] brcmfmac: F1 signature read @0x18000000=0x15264345
[    5.151616] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    5.152479] usbcore: registered new interface driver brcmfmac
[    5.173219] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2
[    5.224484] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
[    5.224910] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
[    5.225341] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
[    5.225755] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
[    5.225777] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
[    5.225796] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
[    5.225813] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
[    5.225829] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
[    5.226009] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
[    5.227777] Console: switching to colour frame buffer device 240x67
[    5.254847] vc4-drm gpu: fb0: vc4drmfb frame buffer device
[    5.269479] bcm2835-v4l2: scene mode selected 0, was 0
[    5.270487] bcm2835-v4l2: V4L2 device registered as video0 - stills mode > 1280x720
[    5.276969] bcm2835-v4l2: Broadcom 2835 MMAL video capture ver 0.0.2 loaded.
[    5.301720] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[    5.301806] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[    5.311542] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[    5.311589] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[    5.319804] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[    5.319857] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[    5.421011] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    5.435904] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 23 2020 02:19:54 version 7.45.206 (r725000 CY) FWID 01-88ee44ea
[    7.059974] uart-pl011 fe201000.serial: no DMA platform data
[    7.067839] random: crng init done
[    7.067859] random: 7 urandom warning(s) missed due to ratelimiting
[    7.123183] 8021q: 802.1Q VLAN Support v1.8
[    7.329458] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[    7.350947] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
[    7.520215] bcmgenet: Skipping UMAC reset
[    7.521697] bcmgenet fd580000.ethernet: configuring instance for external RGMII
[    7.521878] bcmgenet fd580000.ethernet eth0: Link is Down
[   10.651047] bcmgenet fd580000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[   10.651089] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   13.794900] Bluetooth: Core ver 2.22
[   13.794989] NET: Registered protocol family 31
[   13.795002] Bluetooth: HCI device and connection manager initialized
[   13.795321] Bluetooth: HCI socket layer initialized
[   13.795341] Bluetooth: L2CAP socket layer initialized
[   13.795373] Bluetooth: SCO socket layer initialized
[   13.807836] Bluetooth: HCI UART driver ver 2.3
[   13.807855] Bluetooth: HCI UART protocol H4 registered
[   13.807949] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   13.809686] Bluetooth: HCI UART protocol Broadcom registered
[   13.981889] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   13.981896] Bluetooth: BNEP filters: protocol multicast
[   13.981910] Bluetooth: BNEP socket layer initialized

Is it possible that nanodlp tries to get the image from this Arduino instead than using the projector? And this creates the error?

Offline

#12 2020-12-23 20:51:18

Shahin
Administrator
Registered: 2016-02-17
Posts: 3,400

Re: Strange DLP connection with RPI

Each USB, serial or any other device get connected being detected as a file on Linux. And send data, nanodlp does open these files and send it based on type of the port.
No mega does not have anything to do with TI and nanodlp does not try to load image.

I do not see TI details on dmesg.

https://rolfblijleven.blogspot.com/2015 … es-on.html

Offline

#13 2020-12-29 12:02:28

fran42
Member
Registered: 2020-11-16
Posts: 57

Re: Strange DLP connection with RPI

The TI details where not visible because the projector was turned off.
I just uploaded another dmesg in the following post: https://www.nanodlp.com/forum/viewtopic … 286#p11286

Offline

#14 2020-12-30 17:11:08

Shahin
Administrator
Registered: 2016-02-17
Posts: 3,400

Re: Strange DLP connection with RPI

Please, update single thread.
Based on the below details and above guide on the previous post fix address for the projector.
[    2.316814] usb 1-1.1: New USB device found, idVendor=0451, idProduct=c900, bcdDevice= 0.00

Offline

#15 2021-01-05 15:04:32

fran42
Member
Registered: 2020-11-16
Posts: 57

Re: Strange DLP connection with RPI

How can I fix the address of the projector?

Should I do it from raspberry configuration, nanodlp, or how?

I would appreciate if you help me with the steps I should follow.

Offline

#16 2021-01-15 13:31:30

fran42
Member
Registered: 2020-11-16
Posts: 57

Re: Strange DLP connection with RPI

Shahin wrote:

Please, update single thread.
Based on the below details and above guide on the previous post fix address for the projector.
[    2.316814] usb 1-1.1: New USB device found, idVendor=0451, idProduct=c900, bcdDevice= 0.00

How is it possible to fix address for the projector?

Offline

#17 2021-01-16 06:39:52

Shahin
Administrator
Registered: 2016-02-17
Posts: 3,400

Re: Strange DLP connection with RPI

Search how to bind USB device to a static name on linux. There are numerous guide on it over internet.

Offline

#18 2021-01-18 17:10:03

fran42
Member
Registered: 2020-11-16
Posts: 57

Re: Strange DLP connection with RPI

I got this. So I think the address I want to work with is /dev/hidraw0.
/dev/ACM0 seems to be something about the arduino, do you know what could it be?
What do you recommend to do?

(I followed the instructions from  here: https://msadowski.github.io/linux-static-port/)

pi@raspberrypi:~ $ udevadm info --name=/dev/ttyACM0 --attribute-walk

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0 /0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0/tty/ttyACM0':
    KERNEL=="ttyACM0"
    SUBSYSTEM=="tty"
    DRIVER==""

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000: 00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0':
    KERNELS=="1-1.3:1.0"
    SUBSYSTEMS=="usb"
    DRIVERS=="cdc_acm"
    ATTRS{bInterfaceNumber}=="00"
    ATTRS{bInterfaceSubClass}=="02"
    ATTRS{bmCapabilities}=="6"
    ATTRS{bAlternateSetting}==" 0"
    ATTRS{authorized}=="1"
    ATTRS{bInterfaceProtocol}=="01"
    ATTRS{bInterfaceClass}=="02"
    ATTRS{supports_autosuspend}=="1"
    ATTRS{bNumEndpoints}=="01"

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000: 00:00.0/0000:01:00.0/usb1/1-1/1-1.3':
    KERNELS=="1-1.3"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{bDeviceClass}=="02"
    ATTRS{bMaxPower}=="100mA"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{bNumInterfaces}==" 2"
    ATTRS{bmAttributes}=="c0"
    ATTRS{configuration}==""
    ATTRS{authorized}=="1"
    ATTRS{devspec}=="(null)"
    ATTRS{rx_lanes}=="1"
    ATTRS{version}==" 1.10"
    ATTRS{serial}=="5563231353835140B092"
    ATTRS{removable}=="unknown"
    ATTRS{devpath}=="1.3"
    ATTRS{maxchild}=="0"
    ATTRS{ltm_capable}=="no"
    ATTRS{busnum}=="1"
    ATTRS{product}=="Arduino Mega 2560"
    ATTRS{idProduct}=="0010"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bMaxPacketSize0}=="8"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{manufacturer}=="Arduino (www.arduino.cc)"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{idVendor}=="2341"
    ATTRS{quirks}=="0x0"
    ATTRS{bcdDevice}=="0001"
    ATTRS{speed}=="12"
    ATTRS{urbnum}=="80"
    ATTRS{tx_lanes}=="1"
    ATTRS{devnum}=="4"
    ATTRS{bDeviceProtocol}=="00"

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000: 00:00.0/0000:01:00.0/usb1/1-1':
    KERNELS=="1-1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{version}==" 2.10"
    ATTRS{bDeviceClass}=="09"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceProtocol}=="01"
    ATTRS{maxchild}=="4"
    ATTRS{bcdDevice}=="0421"
    ATTRS{urbnum}=="39"
    ATTRS{devpath}=="1"
    ATTRS{idVendor}=="2109"
    ATTRS{rx_lanes}=="1"
    ATTRS{speed}=="480"
    ATTRS{busnum}=="1"
    ATTRS{quirks}=="0x0"
    ATTRS{bMaxPower}=="100mA"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{authorized}=="1"
    ATTRS{product}=="USB2.0 Hub"
    ATTRS{configuration}==""
    ATTRS{tx_lanes}=="1"
    ATTRS{bmAttributes}=="e0"
    ATTRS{devspec}=="(null)"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{ltm_capable}=="no"
    ATTRS{devnum}=="2"
    ATTRS{idProduct}=="3431"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{removable}=="unknown"

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000: 00:00.0/0000:01:00.0/usb1':
    KERNELS=="usb1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{busnum}=="1"
    ATTRS{quirks}=="0x0"
    ATTRS{devnum}=="1"
    ATTRS{bmAttributes}=="e0"
    ATTRS{serial}=="0000:01:00.0"
    ATTRS{authorized}=="1"
    ATTRS{manufacturer}=="Linux 5.4.51-v7l+ xhci-hcd"
    ATTRS{speed}=="480"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bcdDevice}=="0504"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{devpath}=="0"
    ATTRS{interface_authorized_default}=="1"
    ATTRS{tx_lanes}=="1"
    ATTRS{bDeviceProtocol}=="01"
    ATTRS{bDeviceClass}=="09"
    ATTRS{maxchild}=="1"
    ATTRS{rx_lanes}=="1"
    ATTRS{idProduct}=="0002"
    ATTRS{bMaxPower}=="0mA"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{removable}=="unknown"
    ATTRS{urbnum}=="22"
    ATTRS{authorized_default}=="1"
    ATTRS{version}==" 2.00"
    ATTRS{ltm_capable}=="no"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{idVendor}=="1d6b"
    ATTRS{devspec}=="(null)"
    ATTRS{product}=="xHCI Host Controller"
    ATTRS{configuration}==""

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000: 00:00.0/0000:01:00.0':
    KERNELS=="0000:01:00.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="xhci_hcd"
    ATTRS{vendor}=="0x1106"
    ATTRS{broken_parity_status}=="0"
    ATTRS{max_link_speed}=="5 GT/s"
    ATTRS{devspec}==""
    ATTRS{subsystem_vendor}=="0x1106"
    ATTRS{class}=="0x0c0330"
    ATTRS{subsystem_device}=="0x3483"
    ATTRS{consistent_dma_mask_bits}=="64"
    ATTRS{irq}=="57"
    ATTRS{driver_override}=="(null)"
    ATTRS{revision}=="0x01"
    ATTRS{enable}=="1"
    ATTRS{dma_mask_bits}=="64"
    ATTRS{local_cpus}=="f"
    ATTRS{device}=="0x3483"
    ATTRS{current_link_speed}=="5 GT/s"
    ATTRS{msi_bus}=="1"
    ATTRS{local_cpulist}=="0-3"
    ATTRS{current_link_width}=="1"
    ATTRS{max_link_width}=="1"
    ATTRS{ari_enabled}=="0"

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000: 00:00.0':
    KERNELS=="0000:00:00.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="pcieport"
    ATTRS{subsystem_device}=="0x0000"
    ATTRS{enable}=="1"
    ATTRS{subsystem_vendor}=="0x0000"
    ATTRS{ari_enabled}=="0"
    ATTRS{irq}=="56"
    ATTRS{consistent_dma_mask_bits}=="32"
    ATTRS{subordinate_bus_number}=="1"
    ATTRS{class}=="0x060400"
    ATTRS{max_link_speed}=="5 GT/s"
    ATTRS{device}=="0x2711"
    ATTRS{local_cpulist}=="0-3"
    ATTRS{msi_bus}=="1"
    ATTRS{max_link_width}=="1"
    ATTRS{vendor}=="0x14e4"
    ATTRS{aer_rootport_total_err_nonfatal}=="0"
    ATTRS{local_cpus}=="f"
    ATTRS{aer_rootport_total_err_cor}=="0"
    ATTRS{secondary_bus_number}=="1"
    ATTRS{devspec}==""
    ATTRS{current_link_speed}=="5 GT/s"
    ATTRS{revision}=="0x10"
    ATTRS{driver_override}=="(null)"
    ATTRS{dma_mask_bits}=="32"
    ATTRS{current_link_width}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{aer_rootport_total_err_fatal}=="0"

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""

  looking at parent device '/devices/platform/scb/fd500000.pcie':
    KERNELS=="fd500000.pcie"
    SUBSYSTEMS=="platform"
    DRIVERS=="brcm-pcie"
    ATTRS{driver_override}=="(null)"

  looking at parent device '/devices/platform/scb':
    KERNELS=="scb"
    SUBSYSTEMS=="platform"
    DRIVERS==""
    ATTRS{driver_override}=="(null)"

  looking at parent device '/devices/platform':
    KERNELS=="platform"
    SUBSYSTEMS==""
    DRIVERS==""

pi@raspberrypi:~ $ ^C
pi@raspberrypi:~ $ udevadm info --name=/dev/hidraw0 --attribute-walk

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:0451:C900.0001/hidraw/hidraw0':
    KERNEL=="hidraw0"
    SUBSYSTEM=="hidraw"
    DRIVER==""

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:0451:C900.0001':
    KERNELS=="0003:0451:C900.0001"
    SUBSYSTEMS=="hid"
    DRIVERS=="hid-generic"
    ATTRS{country}=="00"

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0':
    KERNELS=="1-1.1:1.0"
    SUBSYSTEMS=="usb"
    DRIVERS=="usbhid"
    ATTRS{bNumEndpoints}=="02"
    ATTRS{interface}=="DLPC900"
    ATTRS{bInterfaceClass}=="03"
    ATTRS{bInterfaceProtocol}=="00"
    ATTRS{bInterfaceNumber}=="00"
    ATTRS{bInterfaceSubClass}=="00"
    ATTRS{bAlternateSetting}==" 0"
    ATTRS{supports_autosuspend}=="1"
    ATTRS{authorized}=="1"

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1':
    KERNELS=="1-1.1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{rx_lanes}=="1"
    ATTRS{ltm_capable}=="no"
    ATTRS{version}==" 1.10"
    ATTRS{devpath}=="1.1"
    ATTRS{urbnum}=="15"
    ATTRS{devspec}=="(null)"
    ATTRS{bDeviceClass}=="00"
    ATTRS{authorized}=="1"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{quirks}=="0x0"
    ATTRS{idVendor}=="0451"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{manufacturer}=="Texas Instruments Inc."
    ATTRS{bMaxPower}=="0mA"
    ATTRS{bNumInterfaces}==" 2"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{busnum}=="1"
    ATTRS{removable}=="unknown"
    ATTRS{bmAttributes}=="c0"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bcdDevice}=="0000"
    ATTRS{speed}=="12"
    ATTRS{idProduct}=="c900"
    ATTRS{tx_lanes}=="1"
    ATTRS{product}=="DLPC900"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{maxchild}=="0"
    ATTRS{devnum}=="3"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{configuration}==""
    ATTRS{serial}=="C900"

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1':
    KERNELS=="1-1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{bDeviceClass}=="09"
    ATTRS{devspec}=="(null)"
    ATTRS{rx_lanes}=="1"
    ATTRS{product}=="USB2.0 Hub"
    ATTRS{busnum}=="1"
    ATTRS{authorized}=="1"
    ATTRS{bDeviceProtocol}=="01"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{quirks}=="0x0"
    ATTRS{bcdDevice}=="0421"
    ATTRS{idProduct}=="3431"
    ATTRS{tx_lanes}=="1"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bMaxPower}=="100mA"
    ATTRS{maxchild}=="4"
    ATTRS{urbnum}=="39"
    ATTRS{configuration}==""
    ATTRS{speed}=="480"
    ATTRS{bmAttributes}=="e0"
    ATTRS{idVendor}=="2109"
    ATTRS{ltm_capable}=="no"
    ATTRS{devnum}=="2"
    ATTRS{version}==" 2.10"
    ATTRS{removable}=="unknown"
    ATTRS{devpath}=="1"
    ATTRS{bDeviceSubClass}=="00"

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1':
    KERNELS=="usb1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{tx_lanes}=="1"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{manufacturer}=="Linux 5.4.51-v7l+ xhci-hcd"
    ATTRS{authorized_default}=="1"
    ATTRS{ltm_capable}=="no"
    ATTRS{rx_lanes}=="1"
    ATTRS{bcdDevice}=="0504"
    ATTRS{idVendor}=="1d6b"
    ATTRS{interface_authorized_default}=="1"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{removable}=="unknown"
    ATTRS{bDeviceClass}=="09"
    ATTRS{devspec}=="(null)"
    ATTRS{serial}=="0000:01:00.0"
    ATTRS{urbnum}=="22"
    ATTRS{idProduct}=="0002"
    ATTRS{bMaxPower}=="0mA"
    ATTRS{maxchild}=="1"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{busnum}=="1"
    ATTRS{configuration}==""
    ATTRS{devpath}=="0"
    ATTRS{bDeviceProtocol}=="01"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bmAttributes}=="e0"
    ATTRS{product}=="xHCI Host Controller"
    ATTRS{speed}=="480"
    ATTRS{authorized}=="1"
    ATTRS{quirks}=="0x0"
    ATTRS{version}==" 2.00"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{devnum}=="1"

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0':
    KERNELS=="0000:01:00.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="xhci_hcd"
    ATTRS{class}=="0x0c0330"
    ATTRS{ari_enabled}=="0"
    ATTRS{driver_override}=="(null)"
    ATTRS{devspec}==""
    ATTRS{max_link_width}=="1"
    ATTRS{max_link_speed}=="5 GT/s"
    ATTRS{subsystem_device}=="0x3483"
    ATTRS{subsystem_vendor}=="0x1106"
    ATTRS{local_cpulist}=="0-3"
    ATTRS{consistent_dma_mask_bits}=="64"
    ATTRS{broken_parity_status}=="0"
    ATTRS{vendor}=="0x1106"
    ATTRS{local_cpus}=="f"
    ATTRS{revision}=="0x01"
    ATTRS{msi_bus}=="1"
    ATTRS{irq}=="57"
    ATTRS{current_link_width}=="1"
    ATTRS{dma_mask_bits}=="64"
    ATTRS{device}=="0x3483"
    ATTRS{enable}=="1"
    ATTRS{current_link_speed}=="5 GT/s"

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0':
    KERNELS=="0000:00:00.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="pcieport"
    ATTRS{consistent_dma_mask_bits}=="32"
    ATTRS{devspec}==""
    ATTRS{device}=="0x2711"
    ATTRS{local_cpulist}=="0-3"
    ATTRS{subsystem_device}=="0x0000"
    ATTRS{irq}=="56"
    ATTRS{broken_parity_status}=="0"
    ATTRS{aer_rootport_total_err_cor}=="0"
    ATTRS{max_link_width}=="1"
    ATTRS{driver_override}=="(null)"
    ATTRS{subordinate_bus_number}=="1"
    ATTRS{secondary_bus_number}=="1"
    ATTRS{current_link_width}=="1"
    ATTRS{ari_enabled}=="0"
    ATTRS{subsystem_vendor}=="0x0000"
    ATTRS{vendor}=="0x14e4"
    ATTRS{local_cpus}=="f"
    ATTRS{enable}=="1"
    ATTRS{current_link_speed}=="5 GT/s"
    ATTRS{msi_bus}=="1"
    ATTRS{max_link_speed}=="5 GT/s"
    ATTRS{class}=="0x060400"
    ATTRS{dma_mask_bits}=="32"
    ATTRS{aer_rootport_total_err_nonfatal}=="0"
    ATTRS{revision}=="0x10"
    ATTRS{aer_rootport_total_err_fatal}=="0"

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""

  looking at parent device '/devices/platform/scb/fd500000.pcie':
    KERNELS=="fd500000.pcie"
    SUBSYSTEMS=="platform"
    DRIVERS=="brcm-pcie"
    ATTRS{driver_override}=="(null)"

  looking at parent device '/devices/platform/scb':
    KERNELS=="scb"
    SUBSYSTEMS=="platform"
    DRIVERS==""
    ATTRS{driver_override}=="(null)"

  looking at parent device '/devices/platform':
    KERNELS=="platform"
    SUBSYSTEMS==""
    DRIVERS==""

pi@raspberrypi:~ $ udevadm info --name=/dev/usb --attribute-walk
Unknown device "/dev/usb": Inappropriate ioctl for device
pi@raspberrypi:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 2341:0010 Arduino SA Mega 2560 (CDC ACM)
Bus 001 Device 003: ID 0451:c900 Texas Instruments, Inc.
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Offline

Board footer

Powered by FluxBB