The command udevadmshows me details for a device: udevadm info -a -n /dev/ttyACM0 💡 See about the difference between ACMx and USBx.
This tells me that the device has been recognized and it is handled by the USB CDC ttyACM0 driver. usb 1-1.3: SerialNumber: 000621000000īecause the OpenSDA Segger J-Link is a composite (multiple) USB device, it shows multiple devices: a MSD (Mass Storage Device), a J-Link and USB CDC (ACM). usb 1-1.3: New USB device found, idVendor=1366, idProduct=0105 usb 1-1.3: new full-speed USB device number 9 using dwc_otg FAT-fs (sda): unable to read boot sector to mark fs as dirty usb 1-1.3: USB disconnect, device number 8 sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: Attached SCSI removable disk sd 0:0:0:0: Assuming drive cache: write through scsi 0:0:0:0: Direct-Access SEGGER MSD Volume 1.00 PQ: 0 ANSI: 4 usb-storage 1-1.3:1.3: USB Mass Storage device detected usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1.3: New USB device found, idVendor=1366, idProduct=1015 Or for the Segger USB CDC (OpenSDA): usb 1-1.3: new full-speed USB device number 8 using dwc_otg cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 I should see something like this for my USB CDC implementation on the FRDM board: usb 1-1.3: New USB device found, idVendor=2504, idProduct=0300 The dmesg command prints kernel debug/log information: dmesg These are the values I had specified in the USB device implementation: Where 2504 is the Vendor ID (VID) and 0300 the Product ID (PID) reported by the USB device. 💡 The vendor string is empty because I’m using a ‘generic’ VID and PID, not registered with the USB consortium. If plugging in a Freescale USB CDC (see “ USB CDC with the FRDM-K64F, finally!“) device, then it shows as Bus 001 Device 007: ID 2504:0300 It shows the Segger OpenSDA which has a combined USB CDC implemented. To see which USB devices are attached I can use the lsusb command: lsusbīus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.īus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.īus 001 Device 004: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter īus 001 Device 005: ID 046d:c52b Logitech, Inc. Where is my USB port?Īfter connecting the USB CDC device to the Raspberry, the first problem is to know which device it is using.
WINDOWS SERIAL TERMINAL FOR RASPBERRY PI HOW TO
I’m using USB CDC (see “ Tutorial: USB CDC with the KL25Z Freedom Board“) in many of my projects, so this is an elegant way how to communicate between the Raspberry Pi and an embedded microcontroller. USB CDC is a device class which implements a ‘serial over USB’ protocol. This article describes how to use the Raspberry Pi with devices connected to it using USB CDC. FRDM-K22F and FRDM-K64F attached to Raspberry Pi 2
0 kommentar(er)
