Hello, I am connecting to the UDOO board 2 modems with Serial Output using a USB-SERIAL converter (chip FT232RL). The chip is recognized for the OS without problems (/dev/ttyUSB0 is created correctly) but I haven't aswer of the modem of my commands using minicom. The chip is working under Windows. root@udoo-neo:~# lsusb Bus 001 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC 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 root@udoo-neo:~# dmesg [ 7.574992] usbcore: registered new interface driver usbserial_generic [ 7.575507] usbserial: USB Serial support registered for generic [ 7.601720] usbcore: registered new interface driver ftdi_sio [ 7.603720] usbserial: USB Serial support registered for FTDI USB Serial Device [ 7.603892] ftdi_sio 1-1.1:1.0: FTDI USB Serial Device converter detected [ 7.613330] usb 1-1.1: Detected FT232RL [ 7.613344] usb 1-1.1: Number of endpoints 2 [ 7.613352] usb 1-1.1: Endpoint 1 MaxPacketSize 64 [ 7.613360] usb 1-1.1: Endpoint 2 MaxPacketSize 64 [ 7.613367] usb 1-1.1: Setting MaxPacketSize 64 [ 7.617133] usb 1-1.1: FTDI USB Serial Device converter now attached to ttyUSB0 MINICOM configuration: A - Serial Device : /dev/ttyUSB0 B - Lockfile Location : /var/lock C - Callin Program : D - Callout Program : E - Bps/Par/Bits : 115200 8N1 F - Hardware Flow Control : Yes G - Software Flow Control : No Thanks in advance!
Yes, I have checked all the combinations and it is not working: HW FC -> yes ; SW FC -> yes HW FC -> yes ; SW FC -> no HW FC -> no ; SW FC -> yes HW FC -> no ; SW FC -> no *HW FC -> Hardware Flow Control *SW FC -> Software Flow Control
How are you connecting to the Neo (to run minicom) through the serial console or a ssh session? Instead of minicom try an alternative like screen eg: screen /dev/ttySUSB0
We have used minicom and another application that we use to manage the modems. This application is working with the same modems in another boards (OMAP) without problems.
hmm, I believe I tested a similar USB-Serial convertor connected from Udoo USB to Udoo Arduino Serial1 without any problems. With Uart6 it didn't work (but you fixed that with the patch). Did you try it also with a not patched Udoobuntu?
The problem is that the UART6 is used for manage another component and I have connected a HUB USB to the usb1 to connect 2 modems (1 Thuraya modem and 1 GSM modem). The GSM modem is working without problems, but the Thuraya is recognized and created the tty file (/dev/ttyUSB0). I have tried with the not pathed image of Udoo-Ubuntu and the result is the same. I have executed the setserial command to obtain the current configuration of the port and I have obtained the following output: root@udoo-neo:~# setserial /dev/ttyUSB0 -a /dev/ttyUSB0, Line 0, UART: unknown, Port: 0x0000, IRQ: 0 Baud_base: 24000000, close_delay: 0, divisor: 0 closing_wait: infinite Flags: spd_normal low_latency
If you disconnect all other devices, and only put your ftdi USB to TTL in usb1 and connect the wires to uart6 or Arduino Serial1, can you setup a serial connection both ways? If that is working you can try to connect the wires to the other Neo and see if it still is working. Then one by one add your other devices and check where it goes wrong.
I have tried without the USB-HUB and with another USB-HUB and it is working. The problem is that I need use the USB-HUB installed previously because I cannot change it. This hub USB has connected another 2 modems and are working without problems... It is very strange
Perhaps power supply is not strong enough for your setup from USB port of the Neo. I had to use a powered USB hub because a not powered hub gave connection issues with my peripherals ( mouse, keyboard and RFID card reader).
