From: Andri Yngvason <andri.yngvason@marel.com>
To: Paul Lever <svjeorgia@gmail.com>
Cc: linux-can@vger.kernel.org
Subject: Re: candump error flags
Date: Fri, 7 Nov 2014 14:13:17 +0000 [thread overview]
Message-ID: <20141107141317.GA11664@shannon> (raw)
In-Reply-To: <CAHuoermNC-Cc79pK_qxkS4t+SjU=JkKtbxN9oZoBZRDUEnvYmA@mail.gmail.com>
On Fri, Nov 07, 2014 at 09:57:41AM -0400, Paul Lever wrote:
> I'm trying to use the candump -e and -d options to catch errors. I
> know that frames are being dropped, as I can see missing packets in
> known sequences, yet I never see anything printed from candump
> indicating any errors or dropped packets. Is there additional steps
> needed to get output from -e/-d options? This is on a Beaglebone Black
> platform.
> My cmd line is:
> candump -t a -e -d -r 16000 can0 > /media/testdata.raw&
>
Hi Paul,
Error handling is different between platforms. On some platforms you need to
enable berr-reporting to get errors. Some platforms support a limited set of
errors (or even no errors at all?)
You can grep for "CAN_ERR" in the driver for your platform to find out which
errors are implemented.
--
Cheers,
Andri
next prev parent reply other threads:[~2014-11-07 14:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 13:57 candump error flags Paul Lever
2014-11-07 14:13 ` Andri Yngvason [this message]
2014-11-07 14:30 ` Marc Kleine-Budde
2014-11-07 14:56 ` Oliver Hartkopp
2014-11-08 14:47 ` Paul Lever
2014-11-08 15:00 ` Oliver Hartkopp
2014-11-08 15:14 ` Paul Lever
2014-11-08 15:29 ` Oliver Hartkopp
2014-11-08 15:34 ` Paul Lever
2014-11-08 16:44 ` Oliver Hartkopp
2014-11-09 14:50 ` Paul Lever
2014-11-08 16:46 ` Marc Kleine-Budde
2014-11-09 14:52 ` Paul Lever
2014-11-09 15:01 ` Marc Kleine-Budde
2014-11-09 15:23 ` Paul Lever
2014-11-10 5:29 ` Pankajkumar Misra (RBEI/EEA2)
2014-11-13 10:20 ` mcp251x (was: Re: candump error flags) Marc Kleine-Budde
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=20141107141317.GA11664@shannon \
--to=andri.yngvason@marel.com \
--cc=linux-can@vger.kernel.org \
--cc=svjeorgia@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.