From: Thor Thayer <tthayer@opensource.altera.com>
To: Richard Andrysek <richard.andrysek@gomtec.de>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: c_can driver sometimes sends first two bytes filled with zeros
Date: Mon, 16 May 2016 13:14:32 -0500 [thread overview]
Message-ID: <573A0E08.4010008@opensource.altera.com> (raw)
In-Reply-To: <0120733A154AE74CA608A286CE7FFD2621D9A343@rg-contact.RG.local>
Hi Richard,
On 05/12/2016 04:23 AM, Richard Andrysek wrote:
> We can reproduce an issue with the canutils. We send messages in the loop with non-zero bytes and from time to time we get first two bytes of the message with zero values. The test script looks so:
>
> #!/bin/sh
>
> echo "Press [CTRL+C] to stop.."
> while true
> do
> cansend can1 --loop=15 -i 933 0xde 0xde 0xde 0xde 0xde 0xde
> done
>
> With CAN analyzer we see normally the right message, but in cycles ~1min we see first two bytes are zero.
>
> If we add some delays between messages, like this:
>
> do
> cansend can1 --loop=1 -i 933 0xde 0xde 0xde 0xde 0xde 0xde
> usleep 5
> cansend can1 --loop=1 -i 933 0xde 0xde 0xde 0xde 0xde 0xde
> usleep 5
> cansend can1 --loop=1 -i 933 0xde 0xde 0xde 0xde 0xde 0xde
> usleep 5
> cansend can1 --loop=1 -i 933 0xde 0xde 0xde 0xde 0xde 0xde
> usleep 5
> cansend can1 --loop=1 -i 933 0xde 0xde 0xde 0xde 0xde 0xde
> usleep 5
> cansend can1 --loop=1 -i 933 0xde 0xde 0xde 0xde 0xde 0xde
> usleep 5
> cansend can1 --loop=1 -i 933 0xde 0xde 0xde 0xde 0xde 0xde
> usleep 5
> cansend can1 --loop=1 -i 933 0xde 0xde 0xde 0xde 0xde 0xde
> usleep 5
> cansend can1 --loop=1 -i 933 0xde 0xde 0xde 0xde 0xde 0xde
> usleep 5
> cansend can1 --loop=1 -i 933 0xde 0xde 0xde 0xde 0xde 0xde
> usleep 5
> cansend can1 --loop=1 -i 933 0xde 0xde 0xde 0xde 0xde 0xde
> usleep 5
>
> done
>
> It works fine.
>
> We use Altera Cyclone V, where the c_can driver is used. It runs with Linux kernel 3.16, but I've checked 4.5 version of a driver and it is a same one.
>
> Have somebody idea how to find a reason for that?
>
> Richard
>
How old are your canutils? I had a similar issue on an older version of
cansend (4.0.6 from the Pengutronix site - with a copyright date of 2009).
There is an old thread (http://comments.gmane.org/gmane.linux.can/2339)
that suggests adding a delay in the cansend utility to work around a
poll/select bug.
I added a delay for 4.0.6 but you may want to grab the latest from
github (https://github.com/linux-can/can-utils).
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2016-05-16 18:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 9:23 c_can driver sometimes sends first two bytes filled with zeros Richard Andrysek
2016-05-16 18:14 ` Thor Thayer [this message]
2016-05-17 17:18 ` AW: " Richard Andrysek
2016-05-18 15:35 ` Thor Thayer
[not found] ` <0120733A154AE74CA608A286CE7FFD2621D9CB60@rg-contact.RG.local>
2016-05-19 23:00 ` AW: " Thor Thayer
2016-05-20 12:01 ` AW: " Richard Andrysek
2016-05-23 14:22 ` Thor Thayer
2016-05-23 18:19 ` Wolfgang Grandegger
2016-06-01 9:40 ` AW: " Richard Andrysek
2016-06-01 13:09 ` Wolfgang Grandegger
2016-06-10 10:49 ` Andy Haydon
2016-06-10 12:55 ` Wolfgang Grandegger
2016-06-10 13:12 ` Andy Haydon
2016-06-10 13:36 ` Wolfgang Grandegger
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=573A0E08.4010008@opensource.altera.com \
--to=tthayer@opensource.altera.com \
--cc=linux-can@vger.kernel.org \
--cc=richard.andrysek@gomtec.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).