linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: laurent vaudoit <laurent.vaudoit@gmail.com>
To: linux-can@vger.kernel.org
Subject: linux-can ISOTP module
Date: Wed, 4 Jun 2014 12:55:56 +0000 (UTC)	[thread overview]
Message-ID: <loom.20140604T144601-350@post.gmane.org> (raw)

Hi all, 
i'm using isotp module for some work purpose,
on a imx25 board, with kernel 3.10.

I have integrated the module isotp and the correct header file in my
kernel.

I'm able to use isotpsend adn isotprecv functions but i have some questions:

Comming from automotiv diagnostic, we are used to configure a lots of 
parameters in our baremetal Iso15765 protocol firmware (stmin, 
bs,n_cs,n_bs...)
I have not seen anything to parameter timings such as n_cs, n_bs.
Is their something i missed?

For extended adressing method, it seems that both rx and tx frame must have 
the same first byte in can frame (the one set by ext_address field of the 
structure). This is correct for mixed addressing method (see Iso15765-2), 
but for extended adressing method, we should be able to specify different 
Target and source adress. I have not seen anything like this.

Last point, if i want to send a 255 bytes frame, with bs=0 and stmin=0 
(requested by the receiver), transfer start well SN 0x01 to SN 0x0B) but 
after i have a frame with SN 0x03 instead of SN = 0x0C and everything stop.

Does anyone encountered this kind of problem?

I will search for this problem as it is a big problem if we want to make 
some download through isotp.

Thanks in advance for your answer

Best regards

Laurent




             reply	other threads:[~2014-06-04 13:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 12:55 laurent vaudoit [this message]
2014-06-04 18:40 ` linux-can ISOTP module 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
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=loom.20140604T144601-350@post.gmane.org \
    --to=laurent.vaudoit@gmail.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;
as well as URLs for NNTP newsgroup(s).