# What is the tty of Arduino? **URL:** \ **Category:** mangOH Green\ **Created:** [October 2, 2018, 9:22pm UTC](https://mangoh.discourse.group/t/what-is-the-tty-of-arduino/1970 "2018-10-02T21:22:45Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![fefer](https://avatars.discourse-cdn.com/v4/letter/f/e36b37/32.png) [@fefer](https://mangoh.discourse.group/u/fefer)\ **Post date:** [October 2, 2018, 9:22pm UTC](https://mangoh.discourse.group/t/what-is-the-tty-of-arduino/1970/1 "2018-10-02T21:22:45Z")
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 ---
**Author:** ![awneil](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/awneil/32/486_2.png) [@awneil](https://mangoh.discourse.group/u/awneil)\ **Post date:** [October 3, 2018, 8:11am UTC](https://mangoh.discourse.group/t/what-is-the-tty-of-arduino/1970/2 "2018-10-03T08:11:35Z")
Have you seen this: [https://littlesliceofmangoh.com/tutorials/UsingTheArduinoOnTheMangOHGreen-Pt1.html](https://littlesliceofmangoh.com/tutorials/UsingTheArduinoOnTheMangOHGreen-Pt1.html) ---
**Author:** ![fefer](https://avatars.discourse-cdn.com/v4/letter/f/e36b37/32.png) [@fefer](https://mangoh.discourse.group/u/fefer)\ **Post date:** [October 3, 2018, 12:48pm UTC](https://mangoh.discourse.group/t/what-is-the-tty-of-arduino/1970/3 "2018-10-03T12:48:32Z")
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 ---
**Author:** ![dfrey](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/dfrey/32/303_2.png) [@dfrey](https://mangoh.discourse.group/u/dfrey)\ **Post date:** [October 4, 2018, 11:40pm UTC](https://mangoh.discourse.group/t/what-is-the-tty-of-arduino/1970/4 "2018-10-04T23:40:30Z")
On WP85 Release 16 ```nohighlight 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 ```nohighlight 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: ```nohighlight [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. ```nohighlight 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 ``` ---
**Author:** ![fefer](https://avatars.discourse-cdn.com/v4/letter/f/e36b37/32.png) [@fefer](https://mangoh.discourse.group/u/fefer)\ **Post date:** [October 5, 2018, 12:11pm UTC](https://mangoh.discourse.group/t/what-is-the-tty-of-arduino/1970/5 "2018-10-05T12:11:43Z")
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](https://us1.discourse-cdn.com/flex016/uploads/mangoh/original/1X/1e5832af3d5e992825584c1df736508ebf10cd36.png) ---
**Author:** ![dfrey](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/dfrey/32/303_2.png) [@dfrey](https://mangoh.discourse.group/u/dfrey)\ **Post date:** [October 5, 2018, 3:12pm UTC](https://mangoh.discourse.group/t/what-is-the-tty-of-arduino/1970/6 "2018-10-05T15:12:09Z")
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 ---
**Author:** ![fefer](https://avatars.discourse-cdn.com/v4/letter/f/e36b37/32.png) [@fefer](https://mangoh.discourse.group/u/fefer)\ **Post date:** [October 5, 2018, 4:22pm UTC](https://mangoh.discourse.group/t/what-is-the-tty-of-arduino/1970/7 "2018-10-05T16:22:43Z")
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 ---
**Author:** ![fefer](https://avatars.discourse-cdn.com/v4/letter/f/e36b37/32.png) [@fefer](https://mangoh.discourse.group/u/fefer)\ **Post date:** [October 10, 2018, 12:40pm UTC](https://mangoh.discourse.group/t/what-is-the-tty-of-arduino/1970/8 "2018-10-10T12:40:49Z")
Can someone give me a hint of what’s wrong? ---
**Author:** ![fefer](https://avatars.discourse-cdn.com/v4/letter/f/e36b37/32.png) [@fefer](https://mangoh.discourse.group/u/fefer)\ **Post date:** [November 1, 2018, 2:16pm UTC](https://mangoh.discourse.group/t/what-is-the-tty-of-arduino/1970/9 "2018-11-01T14:16:50Z")
@dfrey, Do you think updating the ditro may solve this? I´m not sure, but I believe my kernel is 3.18