Linux CAN drivers development
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: Michael Muldoon <mbmuldoon07@gmail.com>
Cc: Linux-CAN <linux-can@vger.kernel.org>
Subject: Re: can acknowledgment
Date: Thu, 05 Sep 2013 21:24:50 +0200	[thread overview]
Message-ID: <5228DA82.4050203@grandegger.com> (raw)
In-Reply-To: <CAJU5jU+F6t+WSLnsF8j7V2v9WBW+BVqQFf=00E2469RybocjzA@mail.gmail.com>

On 09/05/2013 07:17 PM, Michael Muldoon wrote:
> Linux version 3.2.20 (tomh@turbo_tom) (gcc version 4.5.3 (Buildroot
> 2012.05) ) and no I didn't do it myself it came setup.

Well, not that old but a few issues have been fixed in the meantime. Any
chance to switch to a more recent kernel version?

What hardware do you use? MCP2510 or MCP2515? Could you show the boot
log (output of "dmesg)?

Wolfgang,

> 
> On Thu, Sep 5, 2013 at 11:55 AM, Wolfgang Grandegger <wg@grandegger.com> wrote:
>> On Thu, 5 Sep 2013 11:33:19 -0400, Michael Muldoon <mbmuldoon07@gmail.com>
>> wrote:
>>> So I noticed that the can state is always UNKNOWN or DOWN could this
>>> be the problem?
>>> can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN
>>> mode DEFAULT qlen 10
>>>     link/can
>>>     can state BUS-OFF restart-ms 100
>>>     bitrate 125000 sample-point 0.875
>>>     tq 500 prop-seg 6 phase-seg1 7 phase-seg2 2 sjw 1
>>>     mcp251x: tseg1 3..16 tseg2 2..8 sjw 1..4 brp 1..64 brp-inc 1
>>>     clock 10000000
>>>     re-started bus-errors arbit-lost error-warn error-pass bus-off
>>>     0          0          0          327        327        0
>>>     RX: bytes  packets  errors  dropped overrun mcast
>>>     84592      10574    0       0       0       0
>>>     TX: bytes  packets  errors  dropped carrier collsns
>>>     0          0        0       0       0       0
>>> When I tried "# ip link set can0 type can reastart" can0 was definitely
>> on.
>>
>> Just to be sure: s/reastart/restart/
>>
>>> I tried change the settings you suggested still no changes.
>>
>> OK, what kernel version and distribution do you use?
>> Did you do the mc251x platform setup yourself?
>>
>> Wolfgang.
> 
> 


  parent reply	other threads:[~2013-09-05 19:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 19:47 can acknowledgment Michael Muldoon
2013-09-04 20:19 ` Aiken, Scott
2013-09-04 20:40   ` Michael Muldoon
2013-09-04 20:52     ` Aiken, Scott
     [not found]       ` <CAJU5jUKBdqRjZrxJ7P149_c_6n=JbtxvfBxr_Fh+WH4w5gxXag@mail.gmail.com>
2013-09-04 21:15         ` Aiken, Scott
2013-09-05  8:31     ` Wolfgang Grandegger
2013-09-05 12:47       ` Michael Muldoon
2013-09-05 13:45         ` Wolfgang Grandegger
2013-09-05 14:10           ` Michael Muldoon
2013-09-05 15:15             ` Wolfgang Grandegger
     [not found]               ` <CAJU5jULTsLvi4BrB5kuKC7QGVeUjTKY4ad_UA7sJ9aoXNax__g@mail.gmail.com>
     [not found]                 ` <57acf912689fb58466cb5aaac1993a59@grandegger.com>
     [not found]                   ` <CAJU5jU+F6t+WSLnsF8j7V2v9WBW+BVqQFf=00E2469RybocjzA@mail.gmail.com>
2013-09-05 19:24                     ` Wolfgang Grandegger [this message]
2013-09-05 19:45                       ` Michael Muldoon
2013-09-05 20:12                         ` Wolfgang Grandegger
2013-09-05 19:47                       ` Michael Muldoon

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=5228DA82.4050203@grandegger.com \
    --to=wg@grandegger.com \
    --cc=linux-can@vger.kernel.org \
    --cc=mbmuldoon07@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox