From: Wolfgang Grandegger <wg@grandegger.com>
To: Andri Yngvason <andri.yngvason@marel.com>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH v2 1/4] can: dev: Consolidate and unify state change handling.
Date: Wed, 22 Oct 2014 14:30:07 +0200 [thread overview]
Message-ID: <bf2a11ad672de92b98dfcd31405d2c88@grandegger.com> (raw)
In-Reply-To: <5447998A.5080601@marel.com>
On Wed, 22 Oct 2014 11:48:26 +0000, Andri Yngvason
<andri.yngvason@marel.com> wrote:
> On þri 21.okt 2014 15:21, Wolfgang Grandegger wrote:
>>
>>>>>> To see if the state changes occur as expected could you please
record
>>>>>> error message traces with candump for the following two scenarios:
>>>>>>
>>>>>> 1. send messages with cangen
>>>>>> disconnect the cable
>>>>>> reconnect the cable after a while until the error active state
is
>>>>>> reached.
> After cleaning up my mess, this is the output for the disconnected cable
> test:
> (000.000000) can1 20000004 [8] 00 08 00 00 00 00 60 00
ERRORFRAME
> controller-problem{tx-error-warning}
> error-counter-tx-rx{{96}{0}}
> (000.003953) can1 20000004 [8] 00 20 00 00 00 00 80 00
ERRORFRAME
> controller-problem{tx-error-passive}
> error-counter-tx-rx{{128}{0}}
> (005.959170) can1 20000002 [8] 03 00 00 00 00 00 00 00
ERRORFRAME
> lost-arbitration{at bit 3}
I'm missing an error warning message here... at least on the SJA1000 it's
triggered.
> (000.428328) can1 20000004 [8] 00 40 00 00 00 00 5F 00
ERRORFRAME
> controller-problem{back-to-error-active}
> error-counter-tx-rx{{95}{0}}
>
>>>>>>>> 2. set restart-ms=100
>>>>>>>> send messages with cangen
>>>>>>>> provoke a bus-off short-circuiting CAN low and high
>>>>>>>> remove the short-circuit
>>>>>>>>
> Shorting the can bus yields a loop like this:
> (044.014170) can1 20000004 [8] 00 20 00 00 00 00 88 00
ERRORFRAME
> controller-problem{tx-error-passive}
> error-counter-tx-rx{{136}{0}}
> (000.003175) can1 20000040 [8] 00 00 00 00 00 00 7F 00
ERRORFRAME
> bus-off
> error-counter-tx-rx{{127}{0}}
> (000.099664) can1 20000100 [8] 00 00 00 00 00 00 00 00
ERRORFRAME
> restarted-after-bus-off
> (000.097246) can1 20000004 [8] 00 20 00 00 00 00 88 00
ERRORFRAME
> controller-problem{tx-error-passive}
> error-counter-tx-rx{{136}{0}}
> (000.003160) can1 20000040 [8] 00 00 00 00 00 00 7F 00
ERRORFRAME
> bus-off
> error-counter-tx-rx{{127}{0}}
> (000.099602) can1 20000100 [8] 00 00 00 00 00 00 00 00
ERRORFRAME
> restarted-after-bus-off
And the restart does come when the short-circuit is gone?
Wolfgang.
next prev parent reply other threads:[~2014-10-22 12:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 18:25 [PATCH v2 1/4] can: dev: Consolidate and unify state change handling Andri Yngvason
2014-10-20 19:45 ` Wolfgang Grandegger
2014-10-21 10:42 ` Andri Yngvason
2014-10-21 10:52 ` Wolfgang Grandegger
2014-10-21 14:56 ` Andri Yngvason
2014-10-21 15:21 ` Wolfgang Grandegger
2014-10-22 11:48 ` Andri Yngvason
2014-10-22 12:30 ` Wolfgang Grandegger [this message]
2014-10-22 12:48 ` Andri Yngvason
2014-10-22 12:56 ` Wolfgang Grandegger
2014-10-22 16:32 ` Andri Yngvason
2014-10-22 18:42 ` Wolfgang Grandegger
2014-10-23 12:50 ` Andri Yngvason
2014-10-23 13:10 ` Wolfgang Grandegger
2014-10-23 15:55 ` Andri Yngvason
2014-11-22 17:10 ` Marc Kleine-Budde
2014-11-22 18:15 ` Andri Yngvason
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=bf2a11ad672de92b98dfcd31405d2c88@grandegger.com \
--to=wg@grandegger.com \
--cc=andri.yngvason@marel.com \
--cc=linux-can@vger.kernel.org \
/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).