All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Boris Baskevitch <boris.baskevitch@annecy-elec.fr>
Cc: linux-can@vger.kernel.org
Subject: Re: CAN-BCM periodic send signaling
Date: Mon, 06 Jan 2014 19:08:43 +0100	[thread overview]
Message-ID: <52CAF12B.1000006@hartkopp.net> (raw)
In-Reply-To: <003601cf0b02$53c58f10$fb50ad30$@annecy-elec.fr>

Hey Boris,

On 06.01.2014 18:11, Boris Baskevitch wrote:

> I'm using the CAN-BCM to send periodic CAN messages on the bus.
> In one of those messages, I need to send a counter value which is incremented each time the message is sent.
> How can I do that ?

E.g. if you have a 4 bit counter, you just send 16 "struct can_frames" at
TX_SETUP time - also set nframes to 16 then.

When nframes > 1 a sequence of CAN frames is sent automatically.
You may alter these CAN frames at runtime.
If you do so, the tx index may be set to "0" (start) with TX_RESET_MULTI_IDX.

See tst-bcm-cycle.c from the git://gitorious.org/linux-can/can-tests.git

Here's the patch to demonstrate it based on can-tests repository with nframes=4:

diff --git a/tst-bcm-cycle.c b/tst-bcm-cycle.c
index b85ceed..adb2fd6 100644
--- a/tst-bcm-cycle.c
+++ b/tst-bcm-cycle.c
@@ -89,16 +89,29 @@ int main(int argc, char **argv)

 	msg.msg_head.opcode  = TX_SETUP;
 	msg.msg_head.can_id  = 0x42;
-	msg.msg_head.flags   = SETTIMER|STARTTIMER;
-	msg.msg_head.nframes = 1;
-	msg.msg_head.count = 10;
-	msg.msg_head.ival1.tv_sec = 1;
+	msg.msg_head.flags   = SETTIMER|STARTTIMER|TX_CP_CAN_ID;
+	msg.msg_head.nframes = 4;
+	msg.msg_head.count = 0;
+	msg.msg_head.ival1.tv_sec = 0;
 	msg.msg_head.ival1.tv_usec = 0;
 	msg.msg_head.ival2.tv_sec = 0;
-	msg.msg_head.ival2.tv_usec = 0;
-	msg.frame[0].can_id    = 0x42;
+	msg.msg_head.ival2.tv_usec = 200000;
+
+	//msg.frame[0].can_id    = 0x42; /* obsolete due to TX_CP_CAN_ID */
 	msg.frame[0].can_dlc   = 8;
-	U64_DATA(&msg.frame[0]) = (__u64) 0xdeadbeefdeadbeefULL;
+	U64_DATA(&msg.frame[0]) = (__u64) 0x01000000deadbeefULL;
+
+	//msg.frame[1].can_id    = 0x42; /* obsolete due to TX_CP_CAN_ID */
+	msg.frame[1].can_dlc   = 8;
+	U64_DATA(&msg.frame[1]) = (__u64) 0x02000000deadbeefULL;
+
+	//msg.frame[2].can_id    = 0x42; /* obsolete due to TX_CP_CAN_ID */
+	msg.frame[2].can_dlc   = 8;
+	U64_DATA(&msg.frame[2]) = (__u64) 0x03000000deadbeefULL;
+
+	//msg.frame[3].can_id    = 0x42; /* obsolete due to TX_CP_CAN_ID */
+	msg.frame[3].can_dlc   = 8;
+	U64_DATA(&msg.frame[3]) = (__u64) 0x04000000deadbeefULL;

 	if (write(s, &msg, sizeof(msg)) < 0)
 		perror("write");

Does this fit your needs?

Regards,
Oliver


  reply	other threads:[~2014-01-06 18:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 17:11 CAN-BCM periodic send signaling Boris Baskevitch
2014-01-06 18:08 ` Oliver Hartkopp [this message]
2014-01-07  8:29   ` Boris Baskevitch
2014-01-07  9:47     ` Oliver Hartkopp
2014-01-07 12:19       ` Oliver Hartkopp
2014-01-07 12:52         ` Boris Baskevitch
2014-01-07 13:36           ` Oliver Hartkopp
2014-01-07 13:40             ` Boris Baskevitch

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=52CAF12B.1000006@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=boris.baskevitch@annecy-elec.fr \
    --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 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.