Hallo zusammen,
ich bin gerade dabei einen Prüfstand mit einem Raspberry Pi aufzubauen. Unsere Custom Platine mit einem MX8MM von NXP soll im Prüfablauf auch über USB programmiert werden. Um den ganzen Programmiervorgang mal zu testen, hab ich mir einen Raspberry Pi 4 Model B zu Hand genommen (Im Prüfaufbau wird ein Revolution PI verwendet, wo auch ein RP4 verbaut ist). Leider erkenne ich mit lsusb nichts.
Zu meinem Aufbau:-
Netzteil: KSA-15E-051300HE (5.1V / 3.0A)
grep -E "Model|Revision" /proc/cpuinfo
Revision : c03112
Model : Raspberry Pi 4 Model B Rev 1.2
cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Alles anzeigen
uname -a
Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
Device wird nicht mit LSUSB nicht erkannt, hab alle USB Ports getestet. Andere USB-Geräte funktionieren (Maus, USB-Stick)
lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Außerdem wird mit dmesg folgendes ausgegeben:
sudo dmesg | grep usb
[ 0.143635] usbcore: registered new interface driver usbfs
[ 0.143695] usbcore: registered new interface driver hub
[ 0.143762] usbcore: registered new device driver usb
[ 0.144145] usb_phy_generic phy: supply vcc not found, using dummy regulator
[ 0.144360] usb_phy_generic phy: dummy supplies not allowed for exclusive requests
[ 1.491965] usbcore: registered new interface driver r8152
[ 1.492038] usbcore: registered new interface driver lan78xx
[ 1.492114] usbcore: registered new interface driver smsc95xx
[ 1.495783] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
[ 1.495803] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.495819] usb usb1: Product: xHCI Host Controller
[ 1.495832] usb usb1: Manufacturer: Linux 6.1.21-v8+ xhci-hcd
[ 1.495844] usb usb1: SerialNumber: 0000:01:00.0
[ 1.497642] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01
[ 1.497663] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.497677] usb usb2: Product: xHCI Host Controller
[ 1.497690] usb usb2: Manufacturer: Linux 6.1.21-v8+ xhci-hcd
[ 1.497702] usb usb2: SerialNumber: 0000:01:00.0
[ 1.501158] usbcore: registered new interface driver uas
[ 1.501260] usbcore: registered new interface driver usb-storage
[ 1.512467] usbcore: registered new interface driver usbhid
[ 1.512481] usbhid: USB HID core driver
[ 1.750709] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 1.901303] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
[ 1.901340] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1.901356] usb 1-1: Product: USB2.0 Hub
[ 6.475382] usbcore: registered new interface driver brcmfmac
[ 777.383059] usb 1-1.1: new low-speed USB device number 3 using xhci_hcd
[ 777.492888] usb 1-1.1: New USB device found, idVendor=1a81, idProduct=2223, bcdDevice= 1.05
[ 777.492923] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 777.492940] usb 1-1.1: Product: USB Laser Mouse
[ 777.492955] usb 1-1.1: Manufacturer: SINO WEALTH
[ 777.511207] input: SINO WEALTH USB Laser Mouse as /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:1A81:2223.0001/input/input2
[ 777.511908] hid-generic 0003:1A81:2223.0001: input,hidraw0: USB HID v1.10 Mouse [SINO WEALTH USB Laser Mouse] on usb-0000:01:00.0-1.1/input0
[ 777.519680] hid-generic 0003:1A81:2223.0002: hiddev96,hidraw1: USB HID v1.10 Device [SINO WEALTH USB Laser Mouse] on usb-0000:01:00.0-1.1/input1
[ 788.826458] usb 1-1.1: USB disconnect, device number 3
[ 799.279654] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[ 800.151652] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[ 800.152182] usb 1-1-port3: attempt power cycle
[ 801.339377] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[ 802.211601] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[ 802.212111] usb 1-1-port3: unable to enumerate USB device
Alles anzeigen
Updates habe ich auch schon aktualisiert:
sudo apt update
Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Da ich mich gerade im HO befinde, hab ich Private eine Raspberry PI 3 Model B+, da wird allerdings das Device erkannt(gleiches USB-Kabel):-
lsusb
Bus 001 Device 004: ID 0424:7800 Microchip Technology, Inc. (formerly SMSC)
Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
sudo dmesg | grep usb
[ 0.129471] usbcore: registered new interface driver usbfs
[ 0.129536] usbcore: registered new interface driver hub
[ 0.129590] usbcore: registered new device driver usb
[ 0.129802] usb_phy_generic phy: supply vcc not found, using dummy regulator
[ 0.129969] usb_phy_generic phy: dummy supplies not allowed for exclusive requests
[ 2.172984] usbcore: registered new interface driver lan78xx
[ 2.173045] usbcore: registered new interface driver smsc95xx
[ 3.102610] dwc_otg 3f980000.usb: DWC OTG Controller
[ 3.102644] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[ 3.102682] dwc_otg 3f980000.usb: irq 89, io mem 0x00000000
[ 3.102958] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
[ 3.102977] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.102992] usb usb1: Product: DWC OTG Controller
[ 3.103005] usb usb1: Manufacturer: Linux 6.1.21-v7+ dwc_otg_hcd
[ 3.103017] usb usb1: SerialNumber: 3f980000.usb
[ 3.104659] usbcore: registered new interface driver usb-storage
[ 3.110224] usbcore: registered new interface driver usbhid
[ 3.110236] usbhid: USB HID core driver
[ 3.438844] usb 1-1: new high-speed USB device number 2 using dwc_otg
[ 3.679104] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
[ 3.679142] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 3.998850] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[ 4.129190] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
[ 4.129227] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 5.158882] usb 1-1.1.1: new high-speed USB device number 4 using dwc_otg
[ 5.289401] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800, bcdDevice= 3.00
[ 5.289438] usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 10.278525] usbcore: registered new interface driver brcmfmac
[ 170.476052] usb 1-1.1.2: new high-speed USB device number 5 using dwc_otg
[ 170.606576] usb 1-1.1.2: New USB device found, idVendor=1fc9, idProduct=0134, bcdDevice= 1.01
[ 170.606611] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 170.606627] usb 1-1.1.2: Product: SE Blank M845S
[ 170.606639] usb 1-1.1.2: Manufacturer: NXP SemiConductors Inc
[ 170.619809] hid-generic 0003:1FC9:0134.0001: hiddev96,hidraw0: USB HID v1.00 Device [NXP SemiConductors Inc SE Blank M845S ] on usb-3f980000.usb-1.1.2/input0
Alles anzeigen
Auf beiden PI's befindet sich ein frisch aufgesetztes OS. Der RP3 wird auch mit einem anderen Netzteil versorgt: KW15-050E30 (5.0V / 3.0A).
Da ich mich gerade in der Einarbeitungsphase für Linux/Raspberry befinden, würde ich mich freuen, wenn mir jemand weiterhelfen könnte.
Ich vermute, dass auf den unterschiedlichen PI's verschiedene USB-Treiber verbaut sind und das OS was in der Konfiguration verbockt.
Morgen bin ich wieder im Betrieb und werde am Revolution PI die USB-Schnittstelle auch testen. Ändert aber nix daran, dass die Schnittstelle genauso auf dem Test PI funktionieren sollte.
Vielen Dank im Vorraus
Chris
P.S Habe auch schon einen anderen RP4 getestet, genau das gleiche Fehlerbild