My meaning was the USB2Serial communication between Renfell USB host IoT card and our wearable FTDI still showed the frequent TTY break error in ftdi_sio driver level.
In summary,
OK…so issue is only seen with your wearable FTDI part now.
Do you see any issue with onboard console?
No issue seen with console FTDI
Can you post the failing log message? Would like to see the messages
It’s not seen in the normal kernel log. It’s seen as the unexpected Null data sequence in the upper application layer.
so there is no way for us to replicate the issue
Unfortunately I think so.
Asyal,
can you let me know how to program USB3503 register? The preferred way is by I2C port(I2C1 on the schematic) configuration via device tree and programming it in the device driver.
we havent tried that part.
Then can you let me know what I2C port of mdm9607 is mapped to I2C1 of wp7702?
In mdm9607 device tree, only I2C4 is configured @78b8000 IO address. Assuming it is mapped to I2C1 of wp7702, I tried to register TCA9546A I2C mux/USB3503 device as I2C4 devices and programmed it through that IO address. However it seems the assumption is wrong.
I could manage to program TCA9546A I2C mux/USB3503 register by writing I2C driver and the proper device tree change and disable the port 1-2 and enable download streaming charging etc. However the issue was still seen.
I’ve got MangOH Green b/d and tested it with both DC adapter power and USB power source. The USB2Serial communication work perfectly with our wearable device!
Definitely the issue only exists in MangOH Red but we don’t know the root cause…
It is good you can program the TCA… Is this now resolving your issue?
Even with TCA programming, the issue - intermittent but iwith high frequency TTY_BREAK error was still seen. By the way the same FW works OK in MangOH Green too. I suspect the subtle signal integrity error on the USB data path though TCA to WP7702 HSIC_DATA. Anyway we will design the custom PCB by referencing MangOH Green instead.
hi, we have connect usb-Rs485 Iot0 in mangoh baord but failed to recognize ttyUSB0 log is attached for reference, would like to know what am missing
Jan 1 06:06:56 swi-mdm9x28-wp user.info kernel: [ 1.395381] android_usb gadget: android_usb ready
Jan 1 06:06:56 swi-mdm9x28-wp user.info kernel: [ 1.395398] msm_hsusb msm_hsusb: [ci13xxx_start] hw_ep_max = 32
Jan 1 06:06:56 swi-mdm9x28-wp user.info kernel: [ 1.395446] msm_hsusb msm_hsusb: CI13XXX_CONTROLLER_RESET_EVENT received
Jan 1 06:06:56 swi-mdm9x28-wp user.info kernel: [ 1.395463] msm_hsusb msm_hsusb: CI13XXX_CONTROLLER_UDC_STARTED_EVENT received
Jan 1 06:06:56 swi-mdm9x28-wp user.info kernel: [ 1.490173] usb 1-1: new high-speed USB device number 2 using msm_hsic_host
Jan 1 06:06:56 swi-mdm9x28-wp user.info kernel: [ 1.640744] usb 1-1: New USB device found, idVendor=0424, idProduct=3503
Jan 1 06:06:56 swi-mdm9x28-wp user.info kernel: [ 1.640761] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan 1 06:06:56 swi-mdm9x28-wp user.info kernel: [ 1.920125] usb 1-1.1: new full-speed USB device number 3 using msm_hsic_host
Jan 1 06:06:56 swi-mdm9x28-wp user.info kernel: [ 2.032607] usb 1-1.1: New USB device found, idVendor=10c4, idProduct=87a0
Jan 1 06:06:56 swi-mdm9x28-wp user.info kernel: [ 2.032625] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 1 06:06:56 swi-mdm9x28-wp user.info kernel: [ 2.032636] usb 1-1.1: Product: CP2130 USB-to-SPI Bridge
Jan 1 06:06:56 swi-mdm9x28-wp user.info kernel: [ 2.032647] usb 1-1.1: Manufacturer: Silicon Laboratories
Jan 1 06:06:56 swi-mdm9x28-wp user.info kernel: [ 2.032658] usb 1-1.1: SerialNumber: 000EB6DF
Jan 1 06:06:56 swi-mdm9x28-wp user.debug kernel: [ 13.232046] LE_KPI: start initscript /etc/rcS.d/S21usb
Jan 1 06:06:57 swi-mdm9x28-wp user.err kernel: [ 13.961684] enable_store: android_usb: already disabled
Jan 1 06:06:57 swi-mdm9x28-wp user.info kernel: [ 13.984338] msm_hsusb msm_hsusb: CI13XXX_CONTROLLER_CONNECT_EVENT received
Jan 1 06:06:57 swi-mdm9x28-wp user.info kernel: [ 13.987429] msm_otg 78d9000.usb: Avail curr from USB = 2
Jan 1 06:06:57 swi-mdm9x28-wp user.info kernel: [ 13.987468] msm_hsusb msm_hsusb: CI13XXX_CONTROLLER_SUSPEND_EVENT received
Jan 1 06:06:57 swi-mdm9x28-wp user.debug kernel: [ 14.117462] LE_KPI: end initscript /etc/rcS.d/S21usb
Jan 1 06:06:57 swi-mdm9x28-wp user.info kernel: [ 14.128892] msm_hsusb msm_hsusb: CI13XXX_CONTROLLER_RESUME_EVENT received
Jan 1 06:06:57 swi-mdm9x28-wp user.info kernel: [ 14.128973] msm_otg 78d9000.usb: Avail curr from USB = 100
Jan 1 06:06:57 swi-mdm9x28-wp user.info kernel: [ 14.416161] android_usb gadget: high-speed config #1: 86000c8.android_usb
Jan 1 06:06:57 swi-mdm9x28-wp user.info kernel: [ 14.416292] msm_otg 78d9000.usb: Avail curr from USB = 500