Strange error with jspy utility

Strange error with jspy utility

[Abdul Khan]

Hi

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.

#./jspy -P -v

OUTPUT:
===================
 can0:20,0feda - !6 [1] 0a
 can1:20,0feda - !6 [1] 0a
 can0:40,0feda - !6 [1] 0a
 can1:40,0feda - !6 [1] 0a
 can0:40,0feda - !6 [1] 0a
 can1:40,0feda - !6 [1] 0a
===================

I did following steps before running the jsr utility.

#./ip link set can0 type can bitrate 125000 triple-sampling on
#./ip link set can1 type can bitrate 125000 triple-sampling on

#./ip link set can0 j1939 on
#./ip link set can1 j1939 on

#./ip addr add dev can0 j1939 0x20
#./ip addr add dev can1 j1939 0x40

#ifconfig can0 up
#ifconfig can1 up

#./jsr can0:20,feda | ./jsr can1:40,feda

Following configuration, I am using on Linux machine

#./uname -a

OUTPUT:
===================
Linux 3.3.0-rc6 #1 SMP Thu May 17 23:13:08 UTC 2012 i686 unknown
===================

#./lsmod

OUTPUT:
===================
Module                  Size  Used by    Not tainted
can_j1939              32312  0
sja1000_isa             3013  0
sja1000                 5344  1 sja1000_isa
can_dev                 5703  1 sja1000
can_raw                 4939  0
can                    20230  2 can_j1939,can_raw
===================

#./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
===================

#./ip addr show

OUTPUT:
===================
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN qlen 1000
    link/ether 00:01:05:0b:58:7e brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0
3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
    link/sit 0.0.0.0 brd 0.0.0.0
4: can0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN qlen 10
    link/can
    can-j1939 0x20 scope link
5: can1: <NOARP,ECHO> mtu 16 qdisc noop state DOWN qlen 10
    link/can
    can-j1939 0x40 scope link
===================

#./ifconfig

OUTPUT:
===================
can0      Link encap:UNSPEC  HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          UP RUNNING NOARP  MTU:16  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:10 Base address:0x600

can1      Link encap:UNSPEC  HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          UP RUNNING NOARP  MTU:16  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:10 Base address:0x680
===================


Thanks in advance.
Abdul.

Re: Strange error with jspy utility

[Kurt Van Dijck]

Hi Abdul,

Thanks for your intrest in can-j1939.
It appears you got quite far yet.

From your story, I assume you connected can0 & can1 together?

> I am facing strange error with jspy utility provided with j1939-utils
I cannot look on your CAN bus. I'd need a raw CAN dump too
if I want to really debug this remotely.

> #./jsr can0:20,feda | ./jsr can1:40,feda
Here, you connect 2 jsr instances together via a pipe also.
I think you created a loop here.

I'm not trying to find out how this would react.
'jsr' is meant as program to send stdin to j1939 &
receive j1939 to stdout. It's not well documented
since it's a kind of test program ... :-)

I think what you wanted to do is this:

$ ./jsr can0:20,feda &
$ echo "hello" | ./jsr can1:40,feda

Then, you will see the seond instance of jsr terminating
quite soon, after having sent 1 packet.
The first instance of jsr will receive that (via CAN) and print
on stdout.

$ jspy
should then show 1 packet.

Kind regards,
Kurt

> 
> Thanks in advance.
> Abdul.

Re: Strange error with jspy utility

[Oliver Hartkopp]

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

Re: Strange error with jspy utility

[Abdul Khan]

Hi Kurt

Thanks for your response, I was away for few days. Please see below my
findings in-line.

> From your story, I assume you connected can0 & can1 together?

Yes, can0 and can1 are connected together.
can0 hi   <--> can1 hi
can0 lo   <--> can1 lo
can0 grd <--> can1 grd

> I cannot look on your CAN bus. I'd need a raw CAN dump too
> if I want to really debug this remotely.

./cansend can0 123#1122334455667788

./candump can1

Output:
=====
can1 123 [8] 11 22 33 44 55 66 77 88

> $ ./jsr can0:20,feda &
> $ echo "hello" | ./jsr can1:40,feda

I did try with this.

> Then, you will see the seond instance of jsr terminating
> quite soon, after having sent 1 packet.

Yes, second instance of jsr terminating, after having sent 1 packet.

> The first instance of jsr will receive that (via CAN) and print
> on stdout.
>
> $ jspy
> should then show 1 packet.
>

./jspy -P -v

Output:
=====
can0:40, 0feda - !6 [6] 68656c6c 6f0a
                      - !6 [6] 68656c6c 6f0a

Thanks
Abdul.

Re: Strange error with jspy utility

[Abdul Khan]

Hi Oliver,

Please see my findings in-line.

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

I can able to send packet from can0 to can1 and vice versa.

#./cansend can0 123#1122334455667788

#./candump can1

Output:
=====
can1 123 [8] 11 22 33 44 55 66 77 88

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

I am getting following dmesg.
[    4.629951] can: controller area network core (rev 20090105 abi 8)
[    4.630072] NET: Registered protocol family 29
[    4.631864] can: raw protocol (rev 20090105)
[    4.642162] CAN device driver interface
[    4.644036] sja1000 CAN netdevice driver
[    4.646370] sja1000_isa: platform device 0: port=0x600, mem=0x0, irq=10
[    4.647973] sja1000_isa: platform device 1: port=0x680, mem=0x0, irq=10
[    4.648073] sja1000_isa sja1000_isa.0: probing idx=0: port=0x600,
mem=0x0, irq=10
[    4.651991] sja1000_isa sja1000_isa.0: sja1000_isa device
registered (reg_base=0x00000600, irq=10)
[    4.652063] sja1000_isa sja1000_isa.1: probing idx=1: port=0x680,
mem=0x0, irq=10
[    4.662256] sja1000_isa sja1000_isa.1: sja1000_isa device
registered (reg_base=0x00000680, irq=10)
[    4.665633] Legacy sja1000_isa driver for max. 8 devices registered
[    4.672009] sja1000_isa sja1000_isa.0: can0: bit-timing not yet defined
[    4.673968] sja1000_isa sja1000_isa.1: can1: bit-timing not yet defined

on loading can-j1939.ko module
# modprobe can-j1939

dmesg output:
==========
[   76.791667] can: SAE J1939

on setting bit-rate using below command.
#./ip link set can0 type can bitrate 125000
#./ip link set can1 type can bitrate 125000

dmesg output:
==========
[  168.014338] sja1000_isa sja1000_isa.0: can0: setting BTR0=0x03 BTR1=0x1c
[  173.198542] sja1000_isa sja1000_isa.1: can1: setting BTR0=0x03 BTR1=0x1c


on setting link using below command
#./ip link set can0 j1939 on
#./ip link set can1 j1939 on

dmesg output:
==========
[  187.406173] j1939-4: register
[  190.325970] j1939-5: register

> E.g
>
> # ip -details link show
>

# ip -details link show ( Before: ifconfig can0/1 up )

Output:
======================
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN qlen 1000
    link/ether 00:01:05:0b:58:7e brd ff:ff:ff:ff:ff:ff
3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
    link/sit 0.0.0.0 brd 0.0.0.0
4: can0: <NOARP,ECHO> mtu 16 qdisc pfifo_fast state DOWN qlen 10
    link/can
    can state STOPPED (berr-counter tx 0 rx 0) restart-ms 0
    bitrate 125000 sample-point 0.875
    tq 500 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
    j1939 on
5: can1: <NOARP,ECHO> mtu 16 qdisc pfifo_fast state DOWN qlen 10
    link/can
    can state STOPPED (berr-counter tx 0 rx 0) restart-ms 0
    bitrate 125000 sample-point 0.875
    tq 500 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
    j1939 on
======================


# ip -details link show  ( After: ifconfig can0/1 up )

Output:
======================
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN qlen 1000
    link/ether 00:01:05:0b:58:7e brd ff:ff:ff:ff:ff:ff
3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
    link/sit 0.0.0.0 brd 0.0.0.0
4: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN qlen 10
    link/can
    can state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0
    bitrate 125000 sample-point 0.875
    tq 500 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
    j1939 on
5: can1: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN qlen 10
    link/can
    can state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0
    bitrate 125000 sample-point 0.875
    tq 500 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
    j1939 on
======================


#./ifconfig

Output:
======================
can0      Link encap:UNSPEC  HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          UP RUNNING NOARP  MTU:16  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10
          RX bytes:8 (8.0 B)  TX bytes:8 (8.0 B)
          Interrupt:10 Base address:0x600

can1      Link encap:UNSPEC  HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          UP RUNNING NOARP  MTU:16  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10
          RX bytes:8 (8.0 B)  TX bytes:8 (8.0 B)
          Interrupt:10 Base address:0x680
======================


# ./ip address show

Output:
======================
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN qlen 1000
    link/ether 00:01:05:0b:58:7e brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0
3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
    link/sit 0.0.0.0 brd 0.0.0.0
4: can0: <NOARP,ECHO> mtu 16 qdisc pfifo_fast state DOWN qlen 10
    link/can
    can-j1939 0x20 scope link
5: can1: <NOARP,ECHO> mtu 16 qdisc pfifo_fast state DOWN qlen 10
    link/can
    can-j1939 0x40 scope link
======================

Observation:
=========
After ifconfig up command, it's state changes from "STOPPED" to "ERROR-ACTIVE"

can state STOPPED ----> can state ERROR-ACTIVE

I am not sure, its a normal behaviour or there is some kind of error.

Thanks
Abdul.

Re: Strange error with jspy utility

[Oliver Hartkopp]

Hi Abdul,

i've already seen from your answer to Kurt that you have also tested the CAN
connection with 'cansend' and 'candump' - which was a really good idea :-)

The CAN state going from "can state STOPPED ----> can state ERROR-ACTIVE" is a
correct behaviour.

In your shown examples you only send ONE single frame.

It can be that ONLY ONE single frame can pass the bus and then e.g. the
interrupt line is not processed correctly which does not re-arm the interrupt.

Can you please confirm that you can send MORE that ONE CAN frame from can0 to
can1 and that you also can send more than one frame from can1 to can0?

Regards,
Oliver


On 24.05.2012 22:30, Abdul Khan wrote:

> Hi Oliver,
> 
> Please see my findings in-line.
> 
>> Are you sure that at least your CAN interfaces are running properly?
> 
> I can able to send packet from can0 to can1 and vice versa.
> 
> #./cansend can0 123#1122334455667788
> 
> #./candump can1
> 
> Output:
> =====
> can1 123 [8] 11 22 33 44 55 66 77 88
> 
>> The sja1000 interfaces usually tell you when the are set in dmesg.
>> This is definitely missing in this grep'ed output.
> 
> I am getting following dmesg.
> [    4.629951] can: controller area network core (rev 20090105 abi 8)
> [    4.630072] NET: Registered protocol family 29
> [    4.631864] can: raw protocol (rev 20090105)
> [    4.642162] CAN device driver interface
> [    4.644036] sja1000 CAN netdevice driver
> [    4.646370] sja1000_isa: platform device 0: port=0x600, mem=0x0, irq=10
> [    4.647973] sja1000_isa: platform device 1: port=0x680, mem=0x0, irq=10
> [    4.648073] sja1000_isa sja1000_isa.0: probing idx=0: port=0x600,
> mem=0x0, irq=10
> [    4.651991] sja1000_isa sja1000_isa.0: sja1000_isa device
> registered (reg_base=0x00000600, irq=10)
> [    4.652063] sja1000_isa sja1000_isa.1: probing idx=1: port=0x680,
> mem=0x0, irq=10
> [    4.662256] sja1000_isa sja1000_isa.1: sja1000_isa device
> registered (reg_base=0x00000680, irq=10)
> [    4.665633] Legacy sja1000_isa driver for max. 8 devices registered
> [    4.672009] sja1000_isa sja1000_isa.0: can0: bit-timing not yet defined
> [    4.673968] sja1000_isa sja1000_isa.1: can1: bit-timing not yet defined
> 
> on loading can-j1939.ko module
> # modprobe can-j1939
> 
> dmesg output:
> ==========
> [   76.791667] can: SAE J1939
> 
> on setting bit-rate using below command.
> #./ip link set can0 type can bitrate 125000
> #./ip link set can1 type can bitrate 125000
> 
> dmesg output:
> ==========
> [  168.014338] sja1000_isa sja1000_isa.0: can0: setting BTR0=0x03 BTR1=0x1c
> [  173.198542] sja1000_isa sja1000_isa.1: can1: setting BTR0=0x03 BTR1=0x1c
> 
> 
> on setting link using below command
> #./ip link set can0 j1939 on
> #./ip link set can1 j1939 on
> 
> dmesg output:
> ==========
> [  187.406173] j1939-4: register
> [  190.325970] j1939-5: register
> 
>> E.g
>>
>> # ip -details link show
>>
> 
> # ip -details link show ( Before: ifconfig can0/1 up )
> 
> Output:
> ======================
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> state DOWN qlen 1000
>     link/ether 00:01:05:0b:58:7e brd ff:ff:ff:ff:ff:ff
> 3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
>     link/sit 0.0.0.0 brd 0.0.0.0
> 4: can0: <NOARP,ECHO> mtu 16 qdisc pfifo_fast state DOWN qlen 10
>     link/can
>     can state STOPPED (berr-counter tx 0 rx 0) restart-ms 0
>     bitrate 125000 sample-point 0.875
>     tq 500 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
>     j1939 on
> 5: can1: <NOARP,ECHO> mtu 16 qdisc pfifo_fast state DOWN qlen 10
>     link/can
>     can state STOPPED (berr-counter tx 0 rx 0) restart-ms 0
>     bitrate 125000 sample-point 0.875
>     tq 500 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
>     j1939 on
> ======================
> 
> 
> # ip -details link show  ( After: ifconfig can0/1 up )
> 
> Output:
> ======================
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> state DOWN qlen 1000
>     link/ether 00:01:05:0b:58:7e brd ff:ff:ff:ff:ff:ff
> 3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
>     link/sit 0.0.0.0 brd 0.0.0.0
> 4: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN qlen 10
>     link/can
>     can state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0
>     bitrate 125000 sample-point 0.875
>     tq 500 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
>     j1939 on
> 5: can1: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN qlen 10
>     link/can
>     can state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0
>     bitrate 125000 sample-point 0.875
>     tq 500 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
>     j1939 on
> ======================
> 
> 
> #./ifconfig
> 
> Output:
> ======================
> can0      Link encap:UNSPEC  HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>           UP RUNNING NOARP  MTU:16  Metric:1
>           RX packets:1 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:10
>           RX bytes:8 (8.0 B)  TX bytes:8 (8.0 B)
>           Interrupt:10 Base address:0x600
> 
> can1      Link encap:UNSPEC  HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>           UP RUNNING NOARP  MTU:16  Metric:1
>           RX packets:1 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:10
>           RX bytes:8 (8.0 B)  TX bytes:8 (8.0 B)
>           Interrupt:10 Base address:0x680
> ======================
> 
> 
> # ./ip address show
> 
> Output:
> ======================
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
>     inet6 ::1/128 scope host
>        valid_lft forever preferred_lft forever
> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> state DOWN qlen 1000
>     link/ether 00:01:05:0b:58:7e brd ff:ff:ff:ff:ff:ff
>     inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0
> 3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
>     link/sit 0.0.0.0 brd 0.0.0.0
> 4: can0: <NOARP,ECHO> mtu 16 qdisc pfifo_fast state DOWN qlen 10
>     link/can
>     can-j1939 0x20 scope link
> 5: can1: <NOARP,ECHO> mtu 16 qdisc pfifo_fast state DOWN qlen 10
>     link/can
>     can-j1939 0x40 scope link
> ======================
> 
> Observation:
> =========
> After ifconfig up command, it's state changes from "STOPPED" to "ERROR-ACTIVE"
> 
> can state STOPPED ----> can state ERROR-ACTIVE
> 
> I am not sure, its a normal behaviour or there is some kind of error.
> 
> Thanks
> Abdul.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Strange error with jspy utility

[Abdul Khan]

Hi Oliver,

Please see my findings in-line with your questions.

On Thu, May 24, 2012 at 10:16 PM, Oliver Hartkopp
<socketcan@hartkopp.net> wrote:
> Hi Abdul,
>
> i've already seen from your answer to Kurt that you have also tested the CAN
> connection with 'cansend' and 'candump' - which was a really good idea :-)
>
> The CAN state going from "can state STOPPED ----> can state ERROR-ACTIVE" is a
> correct behaviour.
>

thanks for the info.

> In your shown examples you only send ONE single frame.
>

I sent multiple frames and there were three cases.

> It can be that ONLY ONE single frame can pass the bus and then e.g. the
> interrupt line is not processed correctly which does not re-arm the interrupt.
>


CASE-1  ( Loop back: can0-can1 and vice versa )
====================================

#./cansend can0 123#1122334455667788 (multiple time in a loop using script)

#./candump -e any,0:0,#FFFFFFFF

Output:
=====
can0 123 [8] 11 22 33 44 55 66 77 88
can1 123 [8] 11 22 33 44 55 66 77 88
can0 123 [8] 11 22 33 44 55 66 77 88
can1 123 [8] 11 22 33 44 55 66 77 88
.....................................................
.....................................................
.
Similarly for can1, there was no problem.

Result:
=====
All CAN frames passed through the bus and there was no problem with
interrupt line.


CASE-2  ( Loop back: can0-can1 and vice versa )
====================================

#./jsr can0:20,feda | ./jsr can1:40,feda

#./candump -e any,0:0,#FFFFFFFF

Output:
=====
can0 18FEDA40 [1] 0A
can1 18FEDA40 [1] 0A
.................................
................................

#./jspy -P -v

Output:
=====
can0:40,0feda - !6 [1] 0a
can1:40,0feda - !6 [1] 0a
.................................
................................

#./ip -d -s link show

Output:
=====
4: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN qlen 10
    link/can
    can <TRIPLE-SAMPLING> state ERROR-PASSIVE (berr-counter tx 0 rx
128) restart-ms 0
    bitrate 125000 sample-point 0.875
    tq 500 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
    re-started bus-errors arbit-lost error-warn error-pass bus-off
    0          0          0          0          0          0
    RX: bytes  packets  errors  dropped overrun mcast
    55731          55731        0       0       0       0
    TX: bytes  packets  errors  dropped carrier collsns
    1      1        0       0       0       0
    j1939 on

5: can1: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN qlen 10
    link/can
    can <TRIPLE-SAMPLING> state ERROR-PASSIVE (berr-counter tx 0 rx
128) restart-ms 0
    bitrate 125000 sample-point 0.875
    tq 500 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
    re-started bus-errors arbit-lost error-warn error-pass bus-off
    0          0          0          0          0          0
    RX: bytes  packets  errors  dropped overrun mcast
    1      1        0       0       0       0
    TX: bytes  packets  errors  dropped carrier collsns
    55731          55731        0       0       0       0
    j1939 on


Result:
=====
Only one j1939 frame passed through the bus and there was no problem
with interrupt line.



CASE-3  ( Connected j1939 simulator to can1 )
==================================
Start j1939 simulator connected with can1

#./candump -e any,0:0,#FFFFFFFF

Output:
=====
 can1  20000004  [8] 00 04 00 00 00 00 00 60   ERRORFRAME
	controller-problem{rx-error-warning}
	error-counter-tx-rx{{0}{96}}
 can1  20000004  [8] 00 10 00 00 00 00 00 80   ERRORFRAME
	controller-problem{rx-error-passive}
	error-counter-tx-rx{{0}{128}}


#./ip -d -s link show

Output:
=====
5: can1: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN qlen 10
    link/can
    can <TRIPLE-SAMPLING> state ERROR-PASSIVE (berr-counter tx 0 rx
128) restart-ms 0
    bitrate 125000 sample-point 0.875
    tq 500 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
    re-started bus-errors arbit-lost error-warn error-pass bus-off
    0          0          0          1          1          0
    RX: bytes  packets  errors  dropped overrun mcast
    16         2        0       0       0       0
    TX: bytes  packets  errors  dropped carrier collsns
    0          0        0       0       0       0
    j1939 on


# dmesg

Output:
=====
[    4.616007] can: controller area network core (rev 20090105 abi 8)
[    4.616121] NET: Registered protocol family 29
[    4.618211] can: raw protocol (rev 20090105)
[    4.628480] CAN device driver interface
[    4.630351] sja1000 CAN netdevice driver
[    4.633162] sja1000_isa: platform device 0: port=0x600, mem=0x0, irq=10
[    4.634698] sja1000_isa: platform device 1: port=0x680, mem=0x0, irq=10
[    4.634744] sja1000_isa sja1000_isa.0: probing idx=0: port=0x600,
mem=0x0, irq=10
[    4.638424] sja1000_isa sja1000_isa.0: sja1000_isa device
registered (reg_base=0x00000600, irq=10)
[    4.638458] sja1000_isa sja1000_isa.1: probing idx=1: port=0x680,
mem=0x0, irq=10
[    4.648482] sja1000_isa sja1000_isa.1: sja1000_isa device
registered (reg_base=0x00000680, irq=10)
[    4.651477] Legacy sja1000_isa driver for max. 8 devices registered
[    4.665513] can: SAE J1939
[   96.910811] sja1000_isa sja1000_isa.0: can0: setting BTR0=0x03 BTR1=0x9c
[  102.318645] sja1000_isa sja1000_isa.1: can1: setting BTR0=0x03 BTR1=0x9c
[  117.660969] j1939-4: register
[  120.117923] j1939-5: register


I was getting this error, once I tried to send j1939 frame from j1939
simulator to can1

[  254.018168] sja1000_isa sja1000_isa.1: can1: error warning interrupt
[  254.021242] sja1000_isa sja1000_isa.1: can1: error passive interrupt


Result:
=====
No j1939 frame passed through the bus and there was problem with interrupt line.


> Can you please confirm that you can send MORE that ONE CAN frame from can0 to
> can1 and that you also can send more than one frame from can1 to can0?
>

Yes for CAN frames. However, No for j1939 frames

I am using the same sja1000_isa driver provided in the source code
provided by Kurt.

# modprobe sja1000_isa port=0x600,0x680 irq=10,10

I don't know, Why sja1000_isa driver is giving "error warning
interrupt" and "error passive interrupt" messages. As simulator
supposed to be sent properly formatted j1939 frame to can1.

What could be possible cause for this type of behaviour ?

> Regards,
> Oliver

Thanks
Abdul.

Re: Strange error with jspy utility

[Oliver Hartkopp]

Hm - thanks for the good testing but looks like you still have some kind of
CAN problem, e.g.

- slightly different bitrate
- wrong/missing termination

Please try without triple-sampling and check the two points above.

Regards,
Oliver

ps. you might also use 'cangen' to generate CAN traffic

On 26.05.2012 00:46, Abdul Khan wrote:

> Hi Oliver,
> 
> Please see my findings in-line with your questions.
> 
> On Thu, May 24, 2012 at 10:16 PM, Oliver Hartkopp
> <socketcan@hartkopp.net> wrote:
>> Hi Abdul,
>>
>> i've already seen from your answer to Kurt that you have also tested the CAN
>> connection with 'cansend' and 'candump' - which was a really good idea :-)
>>
>> The CAN state going from "can state STOPPED ----> can state ERROR-ACTIVE" is a
>> correct behaviour.
>>
> 
> thanks for the info.
> 
>> In your shown examples you only send ONE single frame.
>>
> 
> I sent multiple frames and there were three cases.
> 
>> It can be that ONLY ONE single frame can pass the bus and then e.g. the
>> interrupt line is not processed correctly which does not re-arm the interrupt.
>>
> 
> 
> CASE-1  ( Loop back: can0-can1 and vice versa )
> ====================================
> 
> #./cansend can0 123#1122334455667788 (multiple time in a loop using script)
> 
> #./candump -e any,0:0,#FFFFFFFF
> 
> Output:
> =====
> can0 123 [8] 11 22 33 44 55 66 77 88
> can1 123 [8] 11 22 33 44 55 66 77 88
> can0 123 [8] 11 22 33 44 55 66 77 88
> can1 123 [8] 11 22 33 44 55 66 77 88
> .....................................................
> .....................................................
> .
> Similarly for can1, there was no problem.
> 
> Result:
> =====
> All CAN frames passed through the bus and there was no problem with
> interrupt line.
> 
> 
> CASE-2  ( Loop back: can0-can1 and vice versa )
> ====================================
> 
> #./jsr can0:20,feda | ./jsr can1:40,feda
> 
> #./candump -e any,0:0,#FFFFFFFF
> 
> Output:
> =====
> can0 18FEDA40 [1] 0A
> can1 18FEDA40 [1] 0A
> .................................
> ................................
> 
> #./jspy -P -v
> 
> Output:
> =====
> can0:40,0feda - !6 [1] 0a
> can1:40,0feda - !6 [1] 0a
> .................................
> ................................
> 
> #./ip -d -s link show
> 
> Output:
> =====
> 4: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN qlen 10
>     link/can
>     can <TRIPLE-SAMPLING> state ERROR-PASSIVE (berr-counter tx 0 rx
> 128) restart-ms 0
>     bitrate 125000 sample-point 0.875
>     tq 500 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
>     re-started bus-errors arbit-lost error-warn error-pass bus-off
>     0          0          0          0          0          0
>     RX: bytes  packets  errors  dropped overrun mcast
>     55731          55731        0       0       0       0
>     TX: bytes  packets  errors  dropped carrier collsns
>     1      1        0       0       0       0
>     j1939 on
> 
> 5: can1: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN qlen 10
>     link/can
>     can <TRIPLE-SAMPLING> state ERROR-PASSIVE (berr-counter tx 0 rx
> 128) restart-ms 0
>     bitrate 125000 sample-point 0.875
>     tq 500 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
>     re-started bus-errors arbit-lost error-warn error-pass bus-off
>     0          0          0          0          0          0
>     RX: bytes  packets  errors  dropped overrun mcast
>     1      1        0       0       0       0
>     TX: bytes  packets  errors  dropped carrier collsns
>     55731          55731        0       0       0       0
>     j1939 on
> 
> 
> Result:
> =====
> Only one j1939 frame passed through the bus and there was no problem
> with interrupt line.
> 
> 
> 
> CASE-3  ( Connected j1939 simulator to can1 )
> ==================================
> Start j1939 simulator connected with can1
> 
> #./candump -e any,0:0,#FFFFFFFF
> 
> Output:
> =====
>  can1  20000004  [8] 00 04 00 00 00 00 00 60   ERRORFRAME
> 	controller-problem{rx-error-warning}
> 	error-counter-tx-rx{{0}{96}}
>  can1  20000004  [8] 00 10 00 00 00 00 00 80   ERRORFRAME
> 	controller-problem{rx-error-passive}
> 	error-counter-tx-rx{{0}{128}}
> 
> 
> #./ip -d -s link show
> 
> Output:
> =====
> 5: can1: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN qlen 10
>     link/can
>     can <TRIPLE-SAMPLING> state ERROR-PASSIVE (berr-counter tx 0 rx
> 128) restart-ms 0
>     bitrate 125000 sample-point 0.875
>     tq 500 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
>     re-started bus-errors arbit-lost error-warn error-pass bus-off
>     0          0          0          1          1          0
>     RX: bytes  packets  errors  dropped overrun mcast
>     16         2        0       0       0       0
>     TX: bytes  packets  errors  dropped carrier collsns
>     0          0        0       0       0       0
>     j1939 on
> 
> 
> # dmesg
> 
> Output:
> =====
> [    4.616007] can: controller area network core (rev 20090105 abi 8)
> [    4.616121] NET: Registered protocol family 29
> [    4.618211] can: raw protocol (rev 20090105)
> [    4.628480] CAN device driver interface
> [    4.630351] sja1000 CAN netdevice driver
> [    4.633162] sja1000_isa: platform device 0: port=0x600, mem=0x0, irq=10
> [    4.634698] sja1000_isa: platform device 1: port=0x680, mem=0x0, irq=10
> [    4.634744] sja1000_isa sja1000_isa.0: probing idx=0: port=0x600,
> mem=0x0, irq=10
> [    4.638424] sja1000_isa sja1000_isa.0: sja1000_isa device
> registered (reg_base=0x00000600, irq=10)
> [    4.638458] sja1000_isa sja1000_isa.1: probing idx=1: port=0x680,
> mem=0x0, irq=10
> [    4.648482] sja1000_isa sja1000_isa.1: sja1000_isa device
> registered (reg_base=0x00000680, irq=10)
> [    4.651477] Legacy sja1000_isa driver for max. 8 devices registered
> [    4.665513] can: SAE J1939
> [   96.910811] sja1000_isa sja1000_isa.0: can0: setting BTR0=0x03 BTR1=0x9c
> [  102.318645] sja1000_isa sja1000_isa.1: can1: setting BTR0=0x03 BTR1=0x9c
> [  117.660969] j1939-4: register
> [  120.117923] j1939-5: register
> 
> 
> I was getting this error, once I tried to send j1939 frame from j1939
> simulator to can1
> 
> [  254.018168] sja1000_isa sja1000_isa.1: can1: error warning interrupt
> [  254.021242] sja1000_isa sja1000_isa.1: can1: error passive interrupt
> 
> 
> Result:
> =====
> No j1939 frame passed through the bus and there was problem with interrupt line.
> 
> 
>> Can you please confirm that you can send MORE that ONE CAN frame from can0 to
>> can1 and that you also can send more than one frame from can1 to can0?
>>
> 
> Yes for CAN frames. However, No for j1939 frames
> 
> I am using the same sja1000_isa driver provided in the source code
> provided by Kurt.
> 
> # modprobe sja1000_isa port=0x600,0x680 irq=10,10
> 
> I don't know, Why sja1000_isa driver is giving "error warning
> interrupt" and "error passive interrupt" messages. As simulator
> supposed to be sent properly formatted j1939 frame to can1.
> 
> What could be possible cause for this type of behaviour ?
> 
>> Regards,
>> Oliver
> 
> Thanks
> Abdul.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Strange error with jspy utility

[Oliver Hartkopp]

>>
>> I don't know, Why sja1000_isa driver is giving "error warning
>> interrupt" and "error passive interrupt" messages. As simulator
>> supposed to be sent properly formatted j1939 frame to can1.
>>
>> What could be possible cause for this type of behaviour ?
>>


Is it possible, that when your j1939 simulator tries to answer, the problems
begin?

Regards,
Oliver

Re: Strange error with jspy utility

[Kurt Van Dijck]

Oliver & Abdul,

> > i've already seen from your answer to Kurt that you have also tested the CAN
> > connection with 'cansend' and 'candump' - which was a really good idea :-)
I was closely looking this thread, but yet I conclude I must have missed some emails.
Probably our mail server is misbehaving.

I will check on some cache for your answers and reply then.

Kind regards,
Kurt

Re: Strange error with jspy utility: solved?

[Kurt Van Dijck]

> Hi Kurt
> 
> Thanks for your response, I was away for few days. Please see below my
> findings in-line.
> 
> > From your story, I assume you connected can0 & can1 together?
> 
> Yes, can0 and can1 are connected together.
> can0 hi   <--> can1 hi
> can0 lo   <--> can1 lo
> can0 grd <--> can1 grd

Very well.
> 
> > I cannot look on your CAN bus. I'd need a raw CAN dump too
> > if I want to really debug this remotely.
> 
> ./cansend can0 123#1122334455667788
> 
> ./candump can1
> 
> Output:
> =====
> can1 123 [8] 11 22 33 44 55 66 77 88

You proved the CAN bus is working with 11bit identifiers.
I meant to do candump in parallel with the j1939 tests.

> 
> > $ ./jsr can0:20,feda &
> > $ echo "hello" | ./jsr can1:40,feda
> 
> I did try with this.
> 
> > Then, you will see the seond instance of jsr terminating
> > quite soon, after having sent 1 packet.
> 
> Yes, second instance of jsr terminating, after having sent 1 packet.
> 
> > The first instance of jsr will receive that (via CAN) and print
> > on stdout.
> >
> > $ jspy
> > should then show 1 packet.
> >
> 
> ./jspy -P -v
> 
> Output:
> =====
> can0:40, 0feda - !6 [6] 68656c6c 6f0a
>                       - !6 [6] 68656c6c 6f0a
I believe the output of
	$ candump can0
would have been:
can0 18feda40 [6] 68 65 6c 6c 6f 0a

I think your system is working fine.
The problem you faced is that 'jsr's use is not very wel documented :-)

Regards,
Kurt
> 
> Thanks
> Abdul.

Re: Strange error with jspy utility: Bus problems

[Kurt Van Dijck]

On Sat, May 26, 2012 at 08:57:07AM +0200, Oliver Hartkopp wrote:
> 
> >>
> >> I don't know, Why sja1000_isa driver is giving "error warning
> >> interrupt" and "error passive interrupt" messages. As simulator
> >> supposed to be sent properly formatted j1939 frame to can1.
> >>
> >> What could be possible cause for this type of behaviour ?
> >>

I didn't focused on this at start, and lost the issue a bit.
J1939 is supposed (by norm) to run 250kbit. You're operating j1939
on 125kbit, which is (logically) possible, but beware interfacing
with others!
Are you sure your simulator is operating 125kbit?

Regards,
Kurt