It turns out that stty is not the issue...at least on my old laptop with Debian installed with kernel 3.2.0-4-amd64. The only trick that makes all serial working is running minicom with -o, like this: minicom -D /dev/ttyUSB0 -o This command gets no data from serial, but after it is closed, all other terminals, including gdb remote, can send and receive without any problem. I dunno why but I'm happy with it... On Sun, Jun 1, 2014 at 11:18 PM, jigsaw <jigsaw@xxxxxxxxx> wrote: > Finally get cu working with such stty options: > > q5xiao@kifissia:~$ stty -F /dev/ttyUSB0 -a > speed 0 baud; rows 0; columns 0; line = 0; > intr = <undef>; quit = <undef>; erase = <undef>; kill = <undef>; eof = > <undef>; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = > <undef>; > stop = <undef>; susp = <undef>; rprnt = <undef>; werase = <undef>; > lnext = <undef>; flush = <undef>; min = 0; time = 0; > -parenb -parodd cs8 -hupcl -cstopb -cread -clocal -crtscts > -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl > -ixon -ixoff -iuclc -ixany -imaxbel -iutf8 > -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 > bs0 vt0 ff0 > -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase > -tostop -echoprt -echoctl -echoke > q5xiao@kifissia:~$ > > Seems that not only -crtscts but also -clocal are required. > > On Sun, Jun 1, 2014 at 10:15 PM, jigsaw <jigsaw@xxxxxxxxx> wrote: >> @Teemu I'd like use cu as well. But your solution doesn't seem to work. Do >> you mean start cu first, then call stty from a 2nd shell, then cu will >> receive from serial? BTW, it should be "stty -crtscts -F /dev/ttyUSB0", I >> guess? >> >> >> On Sun, Jun 1, 2014 at 10:03 PM, Teemu Hakala <temmi@xxxxxx> wrote: >>> >>> Damn, I totally forgot about that we mangled the rts/cts handshaking. >>> >>> I’m traditionally using cu for rs-232 work, setting the line parameters >>> from another shell >>> since the tty devices reset their parameters on fclose(). >>> >>> (shell 1)% cu -l /dev/ttyBLAH >>> /* serial line traffic goes in here */ >>> >>> (shell 2)% stty -crtscts /dev/ttyBLAH >>> >>> - t >>> >>> >>> On 1.6.2014, at 21:13, Jose Granados Vergara <jose.granados@xxxxxx> wrote: >>> >>> I've been using HTerm and Parallax Serial Terminal with Ellduino without >>> problems. >>> >>> -Jose >>> ________________________________ >>> De: ell-i-developers-bounce@xxxxxxxxxxxxx >>> [ell-i-developers-bounce@xxxxxxxxxxxxx] en nombre de jigsaw >>> [jigsaw@xxxxxxxxx] >>> Enviado: domingo, 01 de junio de 2014 06:59 p.m. >>> Para: ell-i-developers@xxxxxxxxxxxxx >>> CC: Teemu Hakala >>> Asunto: [ell-i-developers] Re: How to make serial working? >>> >>> @Pekka OK this is what Ivan and I were trying to figure our during >>> hackthon. We noticed that only Arduino IDE was able to talk over serial. >>> >>> @Jose Thanks for the sample code. I was using same code but wrong GPIO >>> pin. So how do you get the serial working? By hacking Arduino IDE in the >>> same way as Pekka said, or you made another customized terminal? >>> >>> >>> On Sun, Jun 1, 2014 at 6:01 PM, Pekka Nikander <pekka.nikander@xxxxxx> >>> wrote: >>>> >>>> The current Ell-i board (Ellduino) Serial requires that you don't pull >>>> DTR or RTS up(?), IIRC. They are used for reseting the board. If you use >>>> a >>>> standard terminal program, that will pull the handshake signals so that the >>>> board goes to the reset state. >>>> >>>> This is one of the things that will be fixed in the next boards. >>>> >>>> The issue should be documented here: >>>> >>>> https://github.com/Ell-i/Hackathon/wiki/Ellduino-serial-programming-interface >>>> but as of today, it is not. >>>> >>>> Here is how we fix this for the Arduino IDE: >>>> >>>> >>>> https://github.com/Ell-i/Arduino/commit/8748a243f22216370c478d937abc60f03697de4e >>>> >>>> --Pekka >>>> >>>> >>>> On 2014–06–01, at 17:00 , Qinglai Xiao <jigsaw@xxxxxxxxx> wrote: >>>> >>>> > Hi Teemu, >>>> > >>>> > Thanks. Im working with the ell-i board, so the stm32f4 story doesn't >>>> > really help. >>>> > Im working at home, so I don't have logic analyser. I can manage to >>>> > make serial working in a hard way by debugging it with mbed. However it >>>> > could save a lot of time if someone shares the experience of ell-i + >>>> > serial. 发件人: Teemu Hakala >>>> > 发送时间: 2014/6/1 16:47 >>>> > 收件人: ell-i-developers@xxxxxxxxxxxxx >>>> > 主题: [ell-i-developers] Re: How to make serial working? >>>> > Hi >>>> > >>>> > I relayed this question to #ELL-i IRC channel on the Freenode network >>>> > and was given a good link to things the software synth winner used as >>>> > a starting point with the F4 Discovery: >>>> > >>>> > http://vedder.se/2012/07/play-mp3-on-the-stm32f4-discovery/ >>>> > >>>> > Then there’s the usual "is everything properly connected" mantra. Are >>>> > you working on it at home or with Ivan, ie. do you have access to a >>>> > logic analyzer? >>>> > >>>> > - t >>>> > >>>> > On 1.6.2014, at 16:25, jigsaw <jigsaw@xxxxxxxxx> wrote: >>>> > >>>> >> Hi, >>>> >> >>>> >> I first tried to load elli/Runtime/stm32/tests/test_Serial_write_uint8 >>>> >> to ell-i, but nothing is received in minicom or screen. Then I tried to >>>> >> manually initialize RCC and USART ( I tried both USART1 and USART2), but >>>> >> still failed. >>>> >> >>>> >> >>>> >> I'm now trying to port the debugger to ell-i, but without working >>>> >> serial I can't make it. >>>> >> >>>> >> Could anyone give a hand? Has anyone got serial working on ell-i with >>>> >> minicom or any other common terminal? >>>> >> >>>> >> thx & >>>> >> rgds, >>>> >> -Qinglai >>>> > >>> >>> >>