Re: R-Car E2 Can interface receive issue

2016-09-02 Thread Roopesh K P
Dear Geert Uytterhoeven, Thank you very much for your support. I thought R-CAR M2 SoC have 2 CAN channels and doesn't require a hardware port in board to test it with can-utils. So you means that I can only use virtual CAN interface (vcan) in Koelsch or ALT board. Anyway thanks for the

Re: R-Car E2 Can interface receive issue

2016-09-02 Thread Geert Uytterhoeven
Hi RKP, On Fri, Sep 2, 2016 at 9:19 AM, Roopesh K P wrote: > I assume Koelsch and Porter boards have not much difference in their make > (both are using R-CAR M2 as SoC) and I can boot a Koelsch board with uImage > and dtb(r8a7791-porter.dtb) made for porter board . I

Re: R-Car E2 Can interface receive issue

2016-09-01 Thread Geert Uytterhoeven
On Thu, Sep 1, 2016 at 2:24 PM, Roopesh K P wrote: > Today I tested the CAN with R-CAR M2 (Koelsch board) because r8a7791 is > listed in CAN driver compatibility list . > > ' dmesg | grep -i can ' shows > > vcan: Virtual CAN interface driver > slcan: serial line CAN

Re: R-Car E2 Can interface receive issue

2016-09-01 Thread Roopesh K P
Dear Geert Uytterhoeven, Thank you very much for your support. Today I tested the CAN with R-CAR M2 (Koelsch board) because r8a7791 is listed in CAN driver compatibility list . ' dmesg | grep -i can ' shows vcan: Virtual CAN interface driver slcan: serial line CAN interface driver slcan: 10

R-Car E2 Can interface receive issue

2016-08-30 Thread Roopesh K P
I'm trying to use native (real hardware) interfaces like can0 in R-CAR E2 based board (RTP0RC7794SEB00011S - ALT board). I am able to configure the CAN interfaces (can0 and can1). While testing, CAN driver seems to be able to send the CAN packets but not able to receive CAN packets from bus.