What is the tty of Arduino?


#1

Hi all,

I’m logged in the 192.168.2.2 linux and it seems USB0 is supposed to be the tty of Arduino. However, there is no USB0 there. Thus, I was wondering, which tty is the Arduino? I was able to find HS0 and HSL1, but both of them doesn’t seem to be the answer for it. Can someone give me a hint on this issue?

PS: I’m using a MangOH Green with WP7702

Best,
Daniel


#2

Have you seen this:

https://littlesliceofmangoh.com/tutorials/UsingTheArduinoOnTheMangOHGreen-Pt1.html


#3

Hi Andy,

Thanks for your answer. I haven´t seen this before, but looking at is it seems that the Arduino is connected to the Linux board through “/dev/ttyUSB0”, which I don´t have it here. The only different tty I found is:

-ttyHS0
-ttyHSL1
-ttyAT

Do you have an idea why I´m not able to find ttyUSB0 and what can be done to solve this?

Best,
Daniel


#4

On WP85 Release 16

root@swi-mdm9x15:~# dmesg | grep USB0
[    9.413459] usb 1-1.1: FTDI USB Serial Device converter now attached to ttyUSB0

On WP77 Release 9.1

root@swi-mdm9x28-wp:~# dmesg | grep USB0
root@swi-mdm9x28-wp:~# modprobe ftdi_sio
root@swi-mdm9x28-wp:~# ls -l /dev/ttyUSB0 
crw--w----    1 root     root      188,   0 Jan  6 00:12 /dev/ttyUSB0
root@swi-mdm9x28-wp:~# dmesg | grep USB0
[  393.052155] usb 1-1.1: FTDI USB Serial Device converter now attached to ttyUSB0

So it is possible to get /dev/ttyUSB0, but for some reason you have to manually install the ftdi_sio kernel module for the device to be created. Here’s a snippet of output from dmesg on the wp77:

[    1.850135] usb 1-1.1: new full-speed USB device number 3 using msm_hsic_host
[    1.968353] usb 1-1.1: New USB device found, idVendor=0403, idProduct=6015
[    1.968373] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.968385] usb 1-1.1: Product: FT230X Basic UART
[    1.968396] usb 1-1.1: Manufacturer: FTDI
[    1.968407] usb 1-1.1: SerialNumber: DJ00PT9I

I don’t know all the details of the modules.alias file format, but to me this looks like a match. I believe that a matching entry like this should cause the module to be loaded automatically. I’m not sure why that’s not happening.

root@swi-mdm9x28-wp:~# grep 'v0403p6015' /lib/modules/3.18.44/modules.alias
alias usb:v0403p6015d*dc*dsc*dp*ic*isc*ip*in* ftdi_sio

#5

Hi @dfrey,

Thanks for your answer, I can reproduce most of what you just said. My device is a WP77XX (as a matter of fact, WP7702) and it does not show the dmesg of USB0. While the modprobe command does not give me an error, I´m still not able to find /dev/ttyUSB0. Bellow is the output:

Capture


#6

Please do the following:

  1. Press the reset button
  2. Wait for the device to boot
  3. login
  4. Run modprobe ftdi_sio
  5. Capture the output of dmesg | grep -i 'usb' and paste it into this thread

#7

The output is:

root@swi-mdm9x28-wp:~# modprobe ftdi_sio
root@swi-mdm9x28-wp:~# dmesg | grep -i ‘usb’
[ 0.369025] usbcore: registered new interface driver usbfs
[ 0.369135] usbcore: registered new interface driver hub
[ 0.369346] usbcore: registered new device driver usb
[ 0.987060] usbcore: registered new interface driver asix
[ 0.987165] usbcore: registered new interface driver ax88179_178a
[ 0.987236] usbcore: registered new interface driver cdc_ether
[ 0.987322] usbcore: registered new interface driver smsc95xx
[ 0.987387] usbcore: registered new interface driver net1080
[ 0.987452] usbcore: registered new interface driver cdc_subset
[ 0.987528] usbcore: registered new interface driver zaurus
[ 0.987900] usbcore: registered new interface driver cdc_ncm
[ 0.988167] msm_otg 78d9000.usb: msm_otg probe
[ 0.988476] of_get_named_gpiod_flags: can’t parse ‘qcom,hub-reset-gpio’ property of node ‘/soc/usb@78d9000[0]’
[ 0.988491] of_get_named_gpiod_flags: can’t parse ‘qcom,usbeth-reset-gpio’ property of node ‘/soc/usb@78d9000[0]’
[ 0.988504] of_get_named_gpiod_flags: can’t parse ‘qcom,sw-sel-gpio’ property of node ‘/soc/usb@78d9000[0]’
[ 0.988563] of_get_named_gpiod_flags: parsed ‘qcom,usbid-gpio’ property of node ‘/soc/usb@78d9000[0]’ - status (0)
[ 0.988586] of_get_named_gpiod_flags: can’t parse ‘qcom,hsusb-otg-vddmin-gpio’ property of node ‘/soc/usb@78d9000[0]’
[ 0.990361] msm_otg 78d9000.usb: OTG regs = d08fe000
[ 0.993653] ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
[ 0.994211] 78d9000.usb supply vbus_otg not found, using dummy regulator
[ 0.994600] usbcore: registered new interface driver cdc_acm
[ 0.994613] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 0.994710] usbcore: registered new interface driver usb-storage
[ 0.994782] usbcore: registered new interface driver ums-alauda
[ 0.994841] usbcore: registered new interface driver ums-cypress
[ 0.994898] usbcore: registered new interface driver ums-datafab
[ 0.994954] usbcore: registered new interface driver ums-freecom
[ 0.995009] usbcore: registered new interface driver ums-isd200
[ 0.995062] usbcore: registered new interface driver ums-jumpshot
[ 0.995113] usbcore: registered new interface driver ums-karma
[ 0.995167] usbcore: registered new interface driver ums-onetouch
[ 0.995218] usbcore: registered new interface driver ums-sddr09
[ 0.995269] usbcore: registered new interface driver ums-sddr55
[ 0.995320] usbcore: registered new interface driver ums-usbat
[ 0.995382] usbcore: registered new interface driver usb_ehset_test
[ 0.999187] msm_otg 78d9000.usb: phy_reset: success
[ 1.044501] usbcore: registered new interface driver usbhid
[ 1.044512] usbhid: USB HID core driver
[ 1.045094] of_get_named_gpiod_flags: can’t parse ‘qcom,gpio-mode-sel’ property of node ‘/soc/usb_detect[0]’
[ 1.214513] android_usb gadget: android_usb ready
[ 1.214531] msm_hsusb msm_hsusb: [ci13xxx_start] hw_ep_max = 32
[ 1.214581] msm_hsusb msm_hsusb: CI13XXX_CONTROLLER_RESET_EVENT received
[ 1.214599] msm_hsusb msm_hsusb: CI13XXX_CONTROLLER_UDC_STARTED_EVENT received
[ 10.457094] enable_store: android_usb: already disabled
[ 10.491773] msm_hsusb msm_hsusb: CI13XXX_CONTROLLER_CONNECT_EVENT received
[ 10.494865] msm_otg 78d9000.usb: Avail curr from USB = 2
[ 10.494904] msm_hsusb msm_hsusb: CI13XXX_CONTROLLER_SUSPEND_EVENT received
[ 10.659278] msm_hsusb msm_hsusb: CI13XXX_CONTROLLER_RESUME_EVENT received
[ 10.659365] msm_otg 78d9000.usb: Avail curr from USB = 100
[ 10.722481] android_work: android_work: sent uevent USB_STATE=CONNECTED
[ 10.748537] android_usb gadget: high-speed config #1: 86000c8.android_usb
[ 10.748571] diag: USB channel diag connected
[ 10.748690] msm_otg 78d9000.usb: Avail curr from USB = 500
[ 10.830229] android_work: android_work: sent uevent USB_STATE=CONFIGURED
[ 23.148280] USB QCMAP NL IOCTL Snd GETNEIGH Succ
[ 33.161175] USB QCMAP NL IOCTL Snd GETNEIGH Succ
[ 33.244810] USB QCMAP NL IOCTL Snd GETNEIGH Succ
[ 143.441265] usbcore: registered new interface driver usbserial
[ 143.493499] usbcore: registered new interface driver ftdi_sio
[ 143.493670] usbserial: USB Serial support registered for FTDI USB Serial Device


#8

Can someone give me a hint of what’s wrong?