public inbox for linux-can@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Abdul Khan <akhan@symboticware.com>
Cc: linux-can@vger.kernel.org
Subject: Re: Strange error with jspy utility
Date: Sat, 19 May 2012 11:06:01 +0200	[thread overview]
Message-ID: <4FB76279.6040201@hartkopp.net> (raw)
In-Reply-To: <CA+cPUuTWRQQ0qBnP1pE34wbMHF1OqXoBq5LkwQzkMgWFOyuzrA@mail.gmail.com>

Hi Abdul,

On 18.05.2012 23:50, Abdul Khan wrote:

> I am facing strange error with jspy utility provided with j1939-utils
> package. I am using can-j1939-utils, iproute2 and
> can-j1939-linux-3.3.0-rc6 provided by Kurt.


Are you sure that at least your CAN interfaces are running properly?

> #./dmesg | grep can
> 
> OUTPUT:
> ===================
> [    1.289519] rtc_cmos 00:05: RTC can wake from S4
> [    1.455446] md: Scanned 0 and added 0 devices.
> [    4.561925] can: controller area network core (rev 20090105 abi 8)
> [    4.563889] can: raw protocol (rev 20090105)
> [    4.601750] sja1000_isa sja1000_isa.0: can0: bit-timing not yet defined
> [    4.606770] sja1000_isa sja1000_isa.1: can1: bit-timing not yet defined
> [  598.521246] can: SAE J1939
> ===================


The sja1000 interfaces usually tell you when the are set in dmesg.
This is definitely missing in this grep'ed output.

E.g.

# ip -details link show

Should give something like this:

8: can0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN qlen 10
    link/can
    can state STOPPED (berr-counter tx 0 rx 0) restart-ms 0
    bitrate 500000 sample-point 0.875
    tq 125 prop-seg 6 phase-seg1 7 phase-seg2 2 sjw 1
    sja1000: tseg1 1..16 tseg2 1..8 sjw 1..4 brp 1..64 brp-inc 1
    clock 8000000
9: can1: <NOARP,ECHO> mtu 16 qdisc noop state DOWN qlen 10
    link/can
    can state STOPPED (berr-counter tx 0 rx 0) restart-ms 0
    bitrate 500000 sample-point 0.812
    tq 125 prop-seg 6 phase-seg1 6 phase-seg2 3 sjw 1
    sja1000: tseg1 1..16 tseg2 1..8 sjw 1..4 brp 1..64 brp-inc 1
    clock 8000000

Regards,
Oliver

  parent reply	other threads:[~2012-05-19  9:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18 21:50 Strange error with jspy utility Abdul Khan
2012-05-19  5:15 ` Kurt Van Dijck
2012-05-24 19:52   ` Abdul Khan
2012-05-29  7:37   ` Strange error with jspy utility: solved? Kurt Van Dijck
2012-05-19  9:06 ` Oliver Hartkopp [this message]
2012-05-24 20:30   ` Strange error with jspy utility Abdul Khan
2012-05-25  2:16     ` Oliver Hartkopp
2012-05-25 22:46       ` Abdul Khan
2012-05-26  6:21         ` Oliver Hartkopp
2012-05-26  6:57           ` Oliver Hartkopp
2012-05-29  7:40             ` Strange error with jspy utility: Bus problems Kurt Van Dijck
2012-05-26 18:29         ` Strange error with jspy utility Kurt Van Dijck

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=4FB76279.6040201@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=akhan@symboticware.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