All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: laurent vaudoit <laurent.vaudoit@gmail.com>
Cc: maxime@artisandeveloppeur.fr, linux-can@vger.kernel.org
Subject: Re: linux-can ISOTP module
Date: Fri, 20 Jun 2014 21:08:09 +0200	[thread overview]
Message-ID: <53A48699.6030605@hartkopp.net> (raw)
In-Reply-To: <CAA7hF3xomuS-mDRQWmkC=D9YfbDPt+TwXKc7+ZFtUNwkg5cMdQ@mail.gmail.com>

Hello Laurent,

On 06.06.2014 08:42, laurent vaudoit wrote:

>>>> With this method, how can i have a segmented transfer like this:
>>>> 0x6a7  0x55 0x10 0x08 ........
>>>> 0x687  0xAA 0x30 0x00 0x00
>>>> 0x6a7  0x55 0x21 .....
>>>>
>>>> The connection i need is between two ECU, using IDs 0x6a7/687 and one has
>>>> adress extension 0x55, the other 0xAA (this adressing method is used on some
>>>> FIAT ECUs for example), but i don't see how it can work using two socket.
>>> I confirm.
>>> This is a problem that we also encountered on a BMW ECU with the current
>>> implementation of ISOTP.
>>> The use-case is real and not currently supported.

I added the funtionality of a different rx_ext_addr to a specific branch of
can-utils and can-modules:

https://gitorious.org/linux-can/can-utils/commits/rx_ext_addr
https://gitorious.org/linux-can/can-modules/commits/rx_ext_addr

Please check them out for a test. As all the isotp tools (in the branch)
support the new feature too, it should be easy to do.

> In my opinion, it would be better to have all normalization parameters
> in the structure:
> __u8 Adressing_method
> __u8 TA
> __u8 SA
> __u8 AE
> 
> Because depending on the Adressing method used, you have to use TA
> (target adress) and SA (Source Adress) for first byte of the frame (TA
> in emission, SA in reception) or AE (adress extension) for both
> emission and reception (case of mixed adressing, see ISO15765-2
> normalization)
> But i don't know if it is available, due to compatibility.

I wonder whether this should be part of a syscall interface API.
The ISO15765-2 protocol is a CAN transport protocol which creates a virtual
point-to-point data connection with help of two CAN identifiers.
There are many use-cases for transport protocols besides diagnosis.

The fact that the ISO15765-2 appendix defines an assignment of logical
addresses to CAN identifiers does not mean that a socket API needs to provide
this assignment pattern. This can be done by some library too.

Regards,
Oliver


  reply	other threads:[~2014-06-20 19:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 12:55 linux-can ISOTP module laurent vaudoit
2014-06-04 18:40 ` Oliver Hartkopp
2014-06-05  7:16   ` laurent vaudoit
2014-06-05 10:18     ` Maxime Jayat
2014-06-05 18:22       ` Oliver Hartkopp
2014-06-06  6:42         ` laurent vaudoit
2014-06-20 19:08           ` Oliver Hartkopp [this message]
2014-06-23 18:01             ` laurent vaudoit
2014-11-13 17:47               ` Oliver Hartkopp
     [not found]                 ` <CAA7hF3ypuVbfxbskM+2bn_58a-k0EtCePxQ_1i6j24G5H=zFSQ@mail.gmail.com>
2015-01-16 17:31                   ` Oliver Hartkopp
2014-06-21 11:18     ` N_Cs timing - was " Oliver Hartkopp
2014-06-23 18:13       ` laurent vaudoit

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=53A48699.6030605@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=laurent.vaudoit@gmail.com \
    --cc=linux-can@vger.kernel.org \
    --cc=maxime@artisandeveloppeur.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.