Probe #2911b2782c of Raspberry Pi Foundation Raspberry Pi 3 Model...
|
Host
| System |  NixOS 22.05 |
|---|---|
| Arch | aarch64 |
| Kernel | 5.15.47 |
| Vendor | Raspberry Pi Foundation » |
| Model | Raspberry Pi 3 Model B+ » |
| HWid | BD229 » |
| Type | system on chip |
| Display Server | Tty |
Devices (16)
| BUS | ID / Class | Vendor | Device | Type | Driver | Status | |
|---|---|---|---|---|---|---|---|
| USB | 0424:7800 » / ff-00-ff |
Microchip Technology, Inc. (formerly SMS... | LAN7800 | network | lan78xx | works
|
|
| USB | 0403:8050 » / ff-ff-ff |
Future Technology Devices International,... | Belimo ZTH | - | fixed
|
||
| USB | 0424:2514 » / 09-00-01 |
Microchip Technology, Inc. (formerly SMS... | USB 2.0 Hub | hub | hub | detected | |
| USB | 1d6b:0002 » / 09-00-00 |
Linux Foundation | 2.0 root hub | hub | hub | detected | |
| SYS | arm-0-4-0-processor » | ARM | Processor | cpu | - | works | |
| SYS | ram-modules-1gb-dimm | RAM Module(s) 1GB DIMM | memory | - | works | ||
| INT | 6015-0001-sd-controller-0 » | SD Controller 0 | mmc controller | mmcblk | works
|
||
| INT | 6015-0002-sdio-controller-1 » | SDIO Controller 1 | mmc controller | - | detected | ||
| SDIO | 02d0-a9a6 » / 07 |
Broadcom Corp. | BCM43438 combo WLAN and Bluetooth Low Energy (BLE) # As in RPi3B | network | brcmfmac | detected
|
|
| SDIO | broadcom-a9a6-bcm43430-wlan-card » | Broadcom Corp. | BCM43430 WLAN card | network | brcmfmac | works
|
|
| MMC | mmc-card-16gb » | MMC Card 16GB | disk | sdhost_bcm2835, mmcblk | works
|
||
| SERIAL | serial-console » | serial console | keyboard | - | detected
|
Logs (28)
Board
|
Boot
|
CPU
|
|||||||
Drive
|
Filesystem
|
Graphics
|
|||||||
Kernel
|
Modules
|
Network
|
|||||||
PCI
|
Processes
|
System
|
|||||||
USB
|
Wireless
|
Failed because the Linux Kernel Drivers do not contain this specific idProduct (0x8050). By using FT_Prog (A tool from FTDI), the idProduct could be changed to 0x6015, if so, everything works out of the box. The takeaway is, that this device with the idProduct 0x8050 should be handled the same way as if it would be a 0x6015.