public inbox for linux-can@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Keith Jones <keith.rjones@yahoo.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [Socketcan-users] Flexcan on i.mx536 Infotainment Platform
Date: Mon, 04 Jun 2012 23:52:57 +0200	[thread overview]
Message-ID: <4FCD2E39.3060809@pengutronix.de> (raw)
In-Reply-To: <1338845698.76889.YahooMailNeo@web140802.mail.bf1.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 2108 bytes --]

Hello Keith,

please switch to the "linux-can@vger.kernel.org" mailinglist, the
berlios list is obsolete.

On 06/04/2012 11:34 PM, Keith Jones wrote:
> I booted up my new Infotainment demo board after ported 2.6.39
> flexcan (flexcan.h flexcan.c) support into my 2.6.35 linux distro.

Use v3.4 or better, this version contains some vital fixes against error
irq floods.

> After seeing flexcan driver register and performing the following
> commands, I get constant interrupts and error packets visualized
> using my Canoe CANbus sniffer. I am using 250K baud. Did not check
> termination. No oscilloscope was used as yet. Can not receive any
> packets. can state goes from ERROR-ACTIVE to ERROR-PASSIVE.

Please check the Termination, do you have a second CAN member on the bus?

> Any clues?

> root@freescale ~$ cansend can0 123#1122334455
> root@freescale /usr/bin$ ip -d -s link show can0
> 2: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN qlen 10
>     link/can
>     can state ERROR-PASSIVE (berr-counter tx 128 rx 0) restart-ms 0
>     bitrate 250000 sample-point 0.875
>     tq 250 prop-seg 6 phase-seg1 7 phase-seg2 2 sjw 1
>     flexcan: tseg1 4..16 tseg2 2..8 sjw 1..4 brp 1..256 brp-inc 1
>     clock 24000000
>     re-started bus-errors arbit-lost error-warn error-pass bus-off
>     0          0          0          5          5          0
>     RX: bytes  packets  errors  dropped overrun mcast
>     80         10       0       0       0       0
>     TX: bytes  packets  errors  dropped carrier collsns
>     5          0        0       0       0       0

If the tx error counter goes up, the device may be the only device on
the CAN bus. Your sniffer is probably totally passive, which means it
doesn't qualify as a second station.

cheers, Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

       reply	other threads:[~2012-06-04 21:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1338845698.76889.YahooMailNeo@web140802.mail.bf1.yahoo.com>
2012-06-04 21:52 ` Marc Kleine-Budde [this message]
2012-06-04 21:55   ` [Socketcan-users] Flexcan on i.mx536 Infotainment Platform Marc Kleine-Budde
2012-06-05  5:00   ` Keith Jones
     [not found] ` <4FD9DB62.50302@grandegger.com>
2012-06-15  5:51   ` Wolfgang Grandegger
2012-06-15  6:42     ` 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=4FCD2E39.3060809@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=keith.rjones@yahoo.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