From: Vladimir Oltean <olteanv@gmail.com>
To: wg@grandegger.com, pankaj.bansal@nxp.com,
pankaj.bansal@oss.nxp.com, mkl@pengutronix.de,
linux-can@vger.kernel.org
Cc: qiangqing.zhang@nxp.com, linux-kernel@vger.kernel.org,
vladimir.oltean@nxp.com
Subject: Re: canfdtest on flexcan loopback
Date: Wed, 16 Sep 2020 14:04:48 +0300 [thread overview]
Message-ID: <20200916110448.dsla6vjzy4fvdr22@skbuf> (raw)
In-Reply-To: <20200916110154.hp4up6yhyokduvf2@skbuf>
[ resending, forgot to copy Wolfgang ]
On Wed 9/2/2020 10:09 AM, Wolfgang Grandegger wrote:
> canfdtest normally runs on the DUT *and* a the host. The DUT receives
> the messages from the host, increments the frame data bytes and then
> sends them back to the host. With "loopback" mode, the data bytes are
> not incremented and that's what you see above.
>
> Wolfgang
Wolfgang is of course right, but we're nonetheless investigating what
seems to be a real problem, and what Pankaj had seen was a red herring.
So currently what I suspect is going on, when I am running canfdtest
between 2 LS1028A-RDB boards, is that the DUT is reordering frames on
TX.
See, for example, the screenshot below:
https://drive.google.com/file/d/1rOeW3aXh3kPh1CJ39lCccRfjFz5JN5I6/view?usp=sharing
I have added trace points to the end of the flexcan_start_xmit function,
which print the entire skb, and the frames appear to be written to the
TX message buffer in the correct order. They are seen, however, in the
incorrect order on the wire.
Thanks,
-Vladimir
next prev parent reply other threads:[~2020-09-16 19:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <VI1PR04MB4093944944C574B138371F51F12F0@VI1PR04MB4093.eurprd04.prod.outlook.com>
2020-09-16 11:01 ` canfdtest on flexcan loopback Vladimir Oltean
2020-09-16 11:04 ` Vladimir Oltean [this message]
2020-09-16 11:32 ` Marc Kleine-Budde
2020-09-16 11:45 ` Vladimir Oltean
2020-09-16 12:01 ` Marc Kleine-Budde
2020-09-16 12:14 ` Vladimir Oltean
2020-09-17 12:59 ` Vladimir Oltean
2020-09-17 13:10 ` Marc Kleine-Budde
2020-09-18 12:27 ` Vladimir Oltean
2020-09-18 12:35 ` Marc Kleine-Budde
2020-09-17 2:28 ` Joakim Zhang
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=20200916110448.dsla6vjzy4fvdr22@skbuf \
--to=olteanv@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=pankaj.bansal@nxp.com \
--cc=pankaj.bansal@oss.nxp.com \
--cc=qiangqing.zhang@nxp.com \
--cc=vladimir.oltean@nxp.com \
--cc=wg@grandegger.com \
/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