- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, i own a light engine which uses cypress dual channel module. the problem is, when i plug it to my RPi, the node is not created in /dev directory. so i can not communicate with the port.
the device is listed when i run "lsusb" as bellow:
pi@raspberrypi:~ $ lsusb
Bus 001 Device 006: ID 04b4:000a Cypress Semiconductor Corp.
Bus 001 Device 004: ID 0424:7800 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
and here is "dmesg" result:
[ 52.751717] usb 1-1.3: new full-speed USB device number 5 using dwc_otg
[ 52.887623] usb 1-1.3: New USB device found, idVendor=04b4, idProduct=000a, bcdDevice= 0.00
[ 52.887637] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 52.887647] usb 1-1.3: Product: USB-Serial (Dual Channel)
[ 52.887656] usb 1-1.3: Manufacturer: Cypress Semiconductor
[ 78.311765] usb 1-1.3: USB disconnect, device number 5
[ 941.075651] usb 1-1.3: new full-speed USB device number 6 using dwc_otg
[ 941.211630] usb 1-1.3: New USB device found, idVendor=04b4, idProduct=000a, bcdDevice= 0.00
[ 941.211647] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 941.211657] usb 1-1.3: Product: USB-Serial (Dual Channel)
[ 941.211666] usb 1-1.3: Manufacturer: Cypress Semiconductor
it just mounted in: /dev/bus/usb/001 and not mapped to /dev
i installed the CyUSBSerial_SDK_Linux and modified the 90-cyusb.rules but nothing happened.
anybody can help me?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
In you application the USB-Serial Device is configured to vendor SPI/I2C class (PID 00A), only the devices configured as CDC class (eg UART CDC mode) which are bound to Linux CDC ACM driver will create a node under /dev/ttyACM and you can communicate with it using applications such as minicom (similar to teraterm in windows). Refer to Testing a USB-Serial Bridge Controller Configured as USB-UART with Linux® – KBA92551 .
Can you please let me know how you want to communicate with the device? You can use the TestUtility.c application as well.
You can install the CyUSBSerial_SDK_Linux from https://www.cypress.com/documentation/software-and-drivers/usb-serial-software-development-kit and run the Test utility.
Please refer to the README.txt file in the path : installation directory-> CyUSBSerial_SDK_Linux -> linux -> testUtility on how to use the testUtility.
Best Regards,
Yatheesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
In you application the USB-Serial Device is configured to vendor SPI/I2C class (PID 00A), only the devices configured as CDC class (eg UART CDC mode) which are bound to Linux CDC ACM driver will create a node under /dev/ttyACM and you can communicate with it using applications such as minicom (similar to teraterm in windows). Refer to Testing a USB-Serial Bridge Controller Configured as USB-UART with Linux® – KBA92551 .
Can you please let me know how you want to communicate with the device? You can use the TestUtility.c application as well.
You can install the CyUSBSerial_SDK_Linux from https://www.cypress.com/documentation/software-and-drivers/usb-serial-software-development-kit and run the Test utility.
Please refer to the README.txt file in the path : installation directory-> CyUSBSerial_SDK_Linux -> linux -> testUtility on how to use the testUtility.
Best Regards,
Yatheesh