From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Tom Evans <tom_usenet@optusnet.com.au>, linux-can@vger.kernel.org
Subject: Re: [PATCH v5 0/5] Consolidate and unify state change handling
Date: Thu, 18 Dec 2014 08:22:56 +0100 [thread overview]
Message-ID: <549280D0.6060507@hartkopp.net> (raw)
In-Reply-To: <loom.20141218T070747-796@post.gmane.org>
On 18.12.2014 07:09, Tom Evans wrote:
> Andri Yngvason <andri.yngvason <at> marel.com> writes:
>> Tested on sja1000 using
>> cangen -Ii -g 100 can0
>> and
>> candump -ta -e can0,0:0,#FFFFFFFF
>>
>> Disconnected bus:
>> (1417614605.207964) can0 07D [6] 49 6E A1 7A 2A 3D
>> (1417614605.308206) can0 07E [8] 5F 18 AA 0F E5 82 CA 11
>> (1417614605.408107) can0 07F [5] 3E 12 B0 68 1A
>> (1417614605.514235) can0 20000004 [8] 00 08 00 00 00 00 60 00
> ERRORFRAME
>> controller-problem{tx-error-warning}
>> error-counter-tx-rx{{96}{0}}
>
> Is the version of candump that supports "-e" and prints the errors
> available? It would be very useful in my current testing.
>
The candump in can-utils provide this option:
https://gitorious.org/linux-can/can-utils/
You may "git clone" the latest version and build it from source.
If you have a recent Debian or Ubuntu-style distro on your Linux-box:
apt-get install can-utils
will make it.
Regards,
Oliver
next prev parent reply other threads:[~2014-12-18 7:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 17:54 [PATCH v5 0/5] Consolidate and unify state change handling Andri Yngvason
2014-12-07 19:16 ` Wolfgang Grandegger
2014-12-07 23:35 ` Marc Kleine-Budde
2014-12-08 7:40 ` Wolfgang Grandegger
2014-12-18 6:09 ` Tom Evans
2014-12-18 7:22 ` Oliver Hartkopp [this message]
2014-12-18 12:15 ` Andri Yngvason
2014-12-18 13:03 ` Oliver Hartkopp
2014-12-18 13:52 ` Oliver Hartkopp
2014-12-19 0:05 ` Tom Evans
2014-12-19 9:33 ` Oliver Hartkopp
[not found] ` <3595849.EjdlQbi96i@heinz>
2014-12-18 13:45 ` Oliver Hartkopp
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=549280D0.6060507@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=tom_usenet@optusnet.com.au \
/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.