From: Fabio Estevam <festevam@gmail.com>
To: Clemens Gruber <clemens.gruber@pqgruber.com>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Nandor Han" <nandor.han@ge.com>,
"Lucas Stach" <l.stach@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: imx: RS-485 problems during TX, maybe DMA related
Date: Sun, 8 Jan 2017 00:30:24 -0200 [thread overview]
Message-ID: <CAOMZO5DedNURGV_k5Y=nt1O98SojsvrOd69PEPEzi8F7N3dJuw@mail.gmail.com> (raw)
In-Reply-To: <20170107230624.GA21729@archie.localdomain>
Hi Clemens,
On Sat, Jan 7, 2017 at 9:06 PM, Clemens Gruber
<clemens.gruber@pqgruber.com> wrote:
> Just remuxed GPIO signals to these pads, applied your two patches and
> used rts-gpios in the DT but I still see the same problem :/
>
> When transmit something, I get doubled characters, then zeros and at the
> end garbled data of previous transmissions, same as described in my
> first post (Logic analyzer: https://pqgruber.com/rs485_results.png)
> The data is always 4096 bytes long, this explains why the echo command
> is blocking for about 4 seconds (<- 4096 bytes at a baudrate of 9600).
> The TE line is also high until all 4096 bytes are sent.
>
> I think this comes from the UART_XMIT_SIZE which is defined to the page
> size.
> Maybe there is something wrong in imx_transmit_buffer and leads to the
> whole circular buffer being sent out all the time, not stopping..
>
> Do these debug logs tell you anything?
> https://gist.github.com/clemensg/1ac5ee8a8ea32acc9145c5aa8407aea5
>
> I am analyzing the signals coming directly from the i.MX6Q, so this must
> be a software problem, but I don't understand why it works for you, if
> we use the same software.
>
> Do you use any other patches on top of mainline and do you use the SDMA
> scripts from the ROM?
No, I use the original 4.9 + the two patches I sent. Yes, I do use the
SDMA scripts from ROM.
Here is the procedure I did to try to reproduce the issue you reported:
(The rs485conf is available at:
https://github.com/mniestroj/rs485conf/blob/master/main.c )
First of all I enable rs485 for ttymxc3 using the rs485conf application:
root@imx6qsabresd:/home# ./rs485conf /dev/ttymxc3 -e 1
[ 27.106517] random: crng init done
= Current configuration:
RS485 enabled: false
RTS on send: high
RTS after send: low
RTS delay before send: 0
RTS delay after send: 0
Receive during sending data: true
= New configuration:
RS485 enabled: true
RTS on send: high
RTS after send: low
RTS delay before send: 0
RTS delay after send: 0
Receive during sending data: true
= Saved configuration:
RS485 enabled: true
RTS on send: high
RTS after send: low
RTS delay before send: 0
RTS delay after send: 0
Receive during sending data: true
root@imx6qsabresd:/ho
Then
root@imx6qsabresd:/home# echo A > /dev/ttymxc3
(wait 10 seconds)
root@imx6qsabresd:/home# echo B > /dev/ttymxc3
(wait 10 seconds)
root@imx6qsabresd:/home# echo C > /dev/ttymxc3
On the serial console at 9600bps only the:
A
B
C
are seen, so not duplicated characters, nor noise is seen on the console.
Regards,
Fabio Estevam
next prev parent reply other threads:[~2017-01-08 2:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 16:00 imx: RS-485 problems during TX, maybe DMA related Clemens Gruber
2017-01-06 21:22 ` Fabio Estevam
2017-01-06 22:50 ` Clemens Gruber
2017-01-07 0:31 ` Fabio Estevam
2017-01-07 13:45 ` Clemens Gruber
2017-01-07 14:57 ` Fabio Estevam
2017-01-07 15:34 ` Clemens Gruber
2017-01-07 16:48 ` Fabio Estevam
2017-01-07 20:59 ` Clemens Gruber
2017-01-07 21:43 ` Fabio Estevam
2017-01-07 23:06 ` Clemens Gruber
2017-01-08 2:30 ` Fabio Estevam [this message]
2017-01-08 18:06 ` Clemens Gruber
2017-01-08 21:46 ` Fabio Estevam
2017-01-11 0:33 ` Clemens Gruber
2017-01-11 11:51 ` Fabio Estevam
2017-01-08 15:12 ` Fabio Estevam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOMZO5DedNURGV_k5Y=nt1O98SojsvrOd69PEPEzi8F7N3dJuw@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=clemens.gruber@pqgruber.com \
--cc=gregkh@linuxfoundation.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nandor.han@ge.com \
--cc=s.hauer@pengutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).