From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Jacob Kroon <jacob.kroon@gmail.com>,
linux-can@vger.kernel.org, wg@grandegger.com, mkl@pengutronix.de
Subject: Re: CM-ITC, pch_can/c_can_pci, sendto() returning ENOBUFS
Date: Tue, 30 Aug 2022 21:15:15 +0200 [thread overview]
Message-ID: <df1d220e-bf99-1051-ca90-5bd52e6c64e7@hartkopp.net> (raw)
In-Reply-To: <f8a95bfb-b1c2-cd41-1106-ca739c438fb9@gmail.com>
Hi Jacob,
On 30.08.22 14:59, Jacob Kroon wrote:
> On 8/29/22 15:53, Oliver Hartkopp wrote:
>> Regarding your problem:
>> "BUG! echo_skb 0 is occupied" should never show up but I wonder if you
>> probably have another CAN specific problem with your setup.
>>
>> Did you set up a CAN network with at least two CAN nodes, identical
>> bitrate settings and 2x120 Ohms (== 60 Ohms) termination between CAN_L
>> and CAN_H?
>>
>
> I have double checked that both endpoints of the network are terminated
> with 120Ohm resistors, and when I check CAN_H/CAN_L in an oscilloscope
> they look ok, and within the spec. voltage levels.
https://www.compulab.com/wp-content/uploads/2011/08/CM-iTC-Reference-Guide.pdf
"it is necessary to add transceiver
hardware (see the SB-iTC reference schematic)"
I assume you have a transceiver, right? ;-)
What is the other endpoint? The EG20T and another (automotive) ECU?
>> Do you have another CAN node which can be attached to the EG20T setup
>> (e.g. some ECU or an USB CAN adapter)?
>
> Yes I do have a CAN analyser from Microchip. I guess I can record all
> traffic with the analyzer, and compare it to what I see with "candump
> can0" on the host. Or do you have some other suggestion ?
Yes, please add the CAN analyzer from Microchip too!
The problem with only two nodes is that you have to be very precise with
bitrate settings and sampling points so that the receiving node needs to
properly set the ACK to acknowlege the CAN frame.
I had been working with a MSCAN system some time ago and that wasn't
able to talk to a commercial CAN tool until I added another node (from
another CAN tool provider).
Maybe you can make the other node talk to the Microchip CAN analyzer and
let the EG20T receive that traffic first.
Best,
Oliver
next prev parent reply other threads:[~2022-08-30 19:15 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 13:25 CM-ITC, pch_can/c_can_pci, sendto() returning ENOBUFS Jacob Kroon
2022-08-26 11:24 ` Jacob Kroon
2022-08-29 9:14 ` Jacob Kroon
2022-08-29 13:20 ` Jacob Kroon
2022-08-29 13:53 ` Oliver Hartkopp
2022-08-30 12:59 ` Jacob Kroon
2022-08-30 19:15 ` Oliver Hartkopp [this message]
2022-09-01 9:38 ` Jacob Kroon
2022-09-01 16:35 ` Oliver Hartkopp
2022-09-02 15:13 ` Jacob Kroon
2022-09-02 16:39 ` Jacob Kroon
2022-09-05 14:17 ` Marc Kleine-Budde
2022-09-05 15:54 ` Marc Kleine-Budde
2022-09-16 4:14 ` Jacob Kroon
2022-09-19 23:24 ` Jacob Kroon
2022-09-20 1:23 ` Vincent Mailhol
2022-09-20 5:08 ` Jacob Kroon
2022-09-21 7:25 ` dariobin
2022-09-21 7:47 ` Marc Kleine-Budde
2022-09-21 8:26 ` Jacob Kroon
2022-09-21 9:55 ` Oliver Hartkopp
2022-09-21 10:32 ` Marc Kleine-Budde
2022-09-21 10:39 ` Oliver Hartkopp
2022-09-21 10:53 ` Marc Kleine-Budde
2022-09-21 11:00 ` Oliver Hartkopp
2022-09-22 7:20 ` dariobin
2022-09-23 11:36 ` Marc Kleine-Budde
2022-09-23 17:55 ` dariobin
2022-09-23 19:03 ` Jacob Kroon
2022-09-23 19:21 ` Jacob Kroon
2022-09-23 19:45 ` dariobin
2022-09-23 20:27 ` Jacob Kroon
2022-09-24 5:17 ` Jacob Kroon
2022-09-28 8:25 ` Marc Kleine-Budde
2022-09-28 8:28 ` Jacob Kroon
2022-09-28 8:02 ` Marc Kleine-Budde
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=df1d220e-bf99-1051-ca90-5bd52e6c64e7@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=jacob.kroon@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=wg@grandegger.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