CAN j1939 library doubts

CAN j1939 library doubts

[Giox79]

Hello everybody.
I'm working on an embedded system, and I would like to dump data 
from CAN bus and parse j1939 data. 
I built canutils, last version, on ARM device, however, I'm a bit 
 about how to use the j1939 version of canutils.
Is there any tutorial about what should I do in order to use 
Utilities  like jspy?
If I'm right, I have to build both the kernel and the user app section.
I'm a Linux beginner, and I didn't find guides to these steps.
Any help, link to website or similar resources will be really appreciated.

Finally is there anyone that compiled the j1939 can libraries on 
ARM systems?

Re: CAN j1939 library doubts

[Jean-Claude Monnin]

Hi,
Yes, I have been using j1939 on an ARM system in the past (TI AM3505). Requires a patched kernel, "iproute2" and "can-j1939-utils". jspy worked fine on ARM.
I cross-compiled the software with ptxdist. I can't provide a tutorial for that, but I can share the rules to build it in case you are familiar with ptxdist.
I would like take the opportunity to say that I encourage the effort to bring upstream the j1939 stack and it's tools. Official tar.* source archives for "iproute2" with j1939 support and "can-j1939-utils" would be useful for the ptxdist rules.
Regards,
Jean-Claude

On Mar 12, 2013, at 22:52 , Giox79 <giovanniparodi79@gmail.com> wrote:

> Hello everybody.
> I'm working on an embedded system, and I would like to dump data 
> from CAN bus and parse j1939 data. 
> I built canutils, last version, on ARM device, however, I'm a bit 
> about how to use the j1939 version of canutils.
> Is there any tutorial about what should I do in order to use 
> Utilities  like jspy?
> If I'm right, I have to build both the kernel and the user app section.
> I'm a Linux beginner, and I didn't find guides to these steps.
> Any help, link to website or similar resources will be really appreciated.
> 
> Finally is there anyone that compiled the j1939 can libraries on 
> ARM systems?
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: CAN j1939 library doubts

[Kurt Van Dijck]

Hi,

iproute2, can-utils & kernel needs patches.

My 'latest' git archives http://gitorious.org/~kurt-vd/  will work,
but you probably want to merge the necessary patches into later versions.

I plan to do some effort to assemble an howto on elinux.org.

Kind regards,
Kurt

On Wed, Mar 13, 2013 at 09:29:01AM +0100, Jean-Claude Monnin wrote:
> Hi,
> Yes, I have been using j1939 on an ARM system in the past (TI AM3505). Requires a patched kernel, "iproute2" and "can-j1939-utils". jspy worked fine on ARM.
> I cross-compiled the software with ptxdist. I can't provide a tutorial for that, but I can share the rules to build it in case you are familiar with ptxdist.
> I would like take the opportunity to say that I encourage the effort to bring upstream the j1939 stack and it's tools. Official tar.* source archives for "iproute2" with j1939 support and "can-j1939-utils" would be useful for the ptxdist rules.
> Regards,
> Jean-Claude
> 
> On Mar 12, 2013, at 22:52 , Giox79 <giovanniparodi79@gmail.com> wrote:
> 
> > Hello everybody.
> > I'm working on an embedded system, and I would like to dump data 
> > from CAN bus and parse j1939 data. 
> > I built canutils, last version, on ARM device, however, I'm a bit 
> > about how to use the j1939 version of canutils.
> > Is there any tutorial about what should I do in order to use 
> > Utilities  like jspy?
> > If I'm right, I have to build both the kernel and the user app section.
> > I'm a Linux beginner, and I didn't find guides to these steps.
> > Any help, link to website or similar resources will be really appreciated.
> > 
> > Finally is there anyone that compiled the j1939 can libraries on 
> > ARM systems?
> > 
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-can" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Kurt Van Dijck
GRAMMER EiA ELECTRONICS
http://www.eia.be
kurt.van.dijck@eia.be
+32-38708534

Re: CAN j1939 library doubts

[Giox79]

Jean-Claude Monnin <jc_monnin <at> emailplus.org> writes:

> 
> Hi,
> Yes, I have been using j1939 on an ARM system in the past (TI AM3505). 
Requires a patched kernel, "iproute2"
> and "can-j1939-utils". jspy worked fine on ARM.
> I cross-compiled the software with ptxdist. I can't provide a tutorial for 
that, but I can share the rules to
> build it in case you are familiar with ptxdist.
> I would like take the opportunity to say that I encourage the effort to bring 
upstream the j1939 stack and
> it's tools. Official tar.* source archives for "iproute2" with j1939 support 
and "can-j1939-utils"
> would be useful for the ptxdist rules.
> Regards,
> Jean-Claude
> 
> On Mar 12, 2013, at 22:52 , Giox79 <giovanniparodi79 <at> gmail.com> wrote:
> 
> > Hello everybody.
> > I'm working on an embedded system, and I would like to dump data 
> > from CAN bus and parse j1939 data. 
> > I built canutils, last version, on ARM device, however, I'm a bit 
> > about how to use the j1939 version of canutils.
> > Is there any tutorial about what should I do in order to use 
> > Utilities  like jspy?
> > If I'm right, I have to build both the kernel and the user app section.
> > I'm a Linux beginner, and I didn't find guides to these steps.
> > Any help, link to website or similar resources will be really appreciated.
> > 
> > Finally is there anyone that compiled the j1939 can libraries on 
> > ARM systems?
> > 
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-can" in
> > the body of a message to majordomo <at> vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo <at> vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

Hi Jean-Claude,
first thanks for your reply. At present time I don't use the ptxdist system. 
However, as far as I understood, it is a specific kernel distribution configured 
for ARM devices. So if you can provide the rules to build j1939 using ptxdist, 
may be I will be able to use it in my SW setup.
Thanks a lot for you help..

Re: CAN j1939 library doubts

[Giox79]

Kurt Van Dijck <kurt.van.dijck <at> eia.be> writes:

> 
> Hi,
> 
> iproute2, can-utils & kernel needs patches.
> 
> My 'latest' git archives http://gitorious.org/~kurt-vd/  will work,
> but you probably want to merge the necessary patches into later versions.
> 
> I plan to do some effort to assemble an howto on elinux.org.
> 
> Kind regards,
> Kurt
> 
> On Wed, Mar 13, 2013 at 09:29:01AM +0100, Jean-Claude Monnin wrote:
> > Hi,
> > Yes, I have been using j1939 on an ARM system in the past (TI AM3505). 
Requires a patched kernel, "iproute2"
> and "can-j1939-utils". jspy worked fine on ARM.
> > I cross-compiled the software with ptxdist. I can't provide a tutorial for 
that, but I can share the rules
> to build it in case you are familiar with ptxdist.
> > I would like take the opportunity to say that I encourage the effort to 
bring upstream the j1939 stack and
> it's tools. Official tar.* source archives for "iproute2" with j1939 support 
and "can-j1939-utils"
> would be useful for the ptxdist rules.
> > Regards,
> > Jean-Claude
> > 
> > On Mar 12, 2013, at 22:52 , Giox79 <giovanniparodi79 <at> gmail.com> wrote:
> > 
> > > Hello everybody.
> > > I'm working on an embedded system, and I would like to dump data 
> > > from CAN bus and parse j1939 data. 
> > > I built canutils, last version, on ARM device, however, I'm a bit 
> > > about how to use the j1939 version of canutils.
> > > Is there any tutorial about what should I do in order to use 
> > > Utilities  like jspy?
> > > If I'm right, I have to build both the kernel and the user app section.
> > > I'm a Linux beginner, and I didn't find guides to these steps.
> > > Any help, link to website or similar resources will be really appreciated.
> > > 
> > > Finally is there anyone that compiled the j1939 can libraries on 
> > > ARM systems?
> > > 
> > > 
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe linux-can" in
> > > the body of a message to majordomo <at> vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-can" in
> > the body of a message to majordomo <at> vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

I Kurt, 
thanks for your reply. I have a question related to J1939. My task is to extract 
from raw can packets info like oil, brake pressure and so on.
Can you tell me if it is right that after building the kernel for my board using 
your modified can driver, and using the jspy utils, I will have only to build 
the J1939 parser?
Is there any utility that will allow me parsing the standard (not vendor 
dependent)packets?
If I will be successfull building the J1939 in my SW environment, I will try to 
create a little howto.
If you think this can be useful, I will send it to you.
have a nice day

Re: CAN j1939 library doubts

[Kurt Van Dijck]

On Thu, Mar 14, 2013 at 11:17:51AM +0000, Giox79 wrote:
> Kurt Van Dijck <kurt.van.dijck <at> eia.be> writes:
> 
> > 
> 
> Hi Kurt, 
> thanks for your reply. I have a question related to J1939. My task is to extract 
> from raw can packets info like oil, brake pressure and so on.
> Can you tell me if it is right that after building the kernel for my board using 
> your modified can driver, and using the jspy utils, I will have only to build 
> the J1939 parser?

I think you could do that without jspy.
You could write a program that connect to a j1939 socket, similar to jspy,
and listen to any packet that if of your interest.
You would get the PGN's as binary streams (possible >8 bytes)

Your program will get quite straight-forward then.

I assume you won't need Address Claiming, since you're watching generic PGN's?

> Is there any utility that will allow me parsing the standard (not vendor 
> dependent)packets?
> If I will be successfull building the J1939 in my SW environment, I will try to 
> create a little howto.
> If you think this can be useful, I will send it to you.
> have a nice day

-- 
Kurt Van Dijck
GRAMMER EiA ELECTRONICS
http://www.eia.be
kurt.van.dijck@eia.be
+32-38708534

Re: CAN j1939 library doubts

[Giox79]

Kurt Van Dijck <kurt.van.dijck <at> eia.be> writes:

> 
> On Thu, Mar 14, 2013 at 11:17:51AM +0000, Giox79 wrote:
> > Kurt Van Dijck <kurt.van.dijck <at> eia.be> writes:
> > 
> > > 
> > 
> > Hi Kurt, 
> > thanks for your reply. I have a question related to J1939. My task is to 
extract 
> > from raw can packets info like oil, brake pressure and so on.
> > Can you tell me if it is right that after building the kernel for my board 
using 
> > your modified can driver, and using the jspy utils, I will have only to 
build 
> > the J1939 parser?
> 
> I think you could do that without jspy.
> You could write a program that connect to a j1939 socket, similar to jspy,
> and listen to any packet that if of your interest.
> You would get the PGN's as binary streams (possible >8 bytes)
> 
> Your program will get quite straight-forward then.
> 
> I assume you won't need Address Claiming, since you're watching generic PGN's?
> 
> > Is there any utility that will allow me parsing the standard (not vendor 
> > dependent)packets?
> > If I will be successfull building the J1939 in my SW environment, I will try 
to 
> > create a little howto.
> > If you think this can be useful, I will send it to you.
> > have a nice day
> 


Hi Kurt, thanks a lot for your help.
You are right as far as I know about can, I do not need address claiming, I have 
to implement a can2lan converter and to support translation of standard can 
messages to an more "clear" form (creating web pages or something like that).

In order to integrate your libs to my kernel, I was supposing to make a diff 
between source file, looking mainly at can and iproute2, merge the diffs and 
build the whole system.
Do you think this is the right approach?
Thanks a lot for your useful help

Re: CAN j1939 library doubts

[Kurt Van Dijck]

On Thu, Mar 14, 2013 at 04:20:08PM +0000, Giox79 wrote:
> Kurt Van Dijck <kurt.van.dijck <at> eia.be> writes:
> 
> In order to integrate your libs to my kernel, I was supposing to make a diff 
> between source file, looking mainly at can and iproute2, merge the diffs and 
> build the whole system.
> Do you think this is the right approach?
no. I (just) prepared the repositories to allow easy merges.

follow these steps (@Marc, can you just verify the 'git' calls):

git clone your kernel, or get a stable one
	$ git clone http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
... this takes time
	$ cd linux-stable
	$ git tag
choose a version, like v3.3, or v3.8, ...
	$ git checkout <chosen-version>
	$ git checkout -b <new-branch-name>
This last command creates a new branch, so you can play freely.
Now choose your branch on http://gitorious.org/~kurt-vd/linux-can/linux-can-j1939
, like j1939-v3.3
	$ git pull git://gitorious.org/~kurt-vd/linux-can/linux-can-j1939.git <gitorious-branch-name>

If this all went ok, then you're ready now.

The same applies for can-utils & iproute2.
You could also clone my j1939 versions directly if you do not care about
the precise versions, like:
	$ git clone -b <gitorious-branch-name> git://gitorious.org/~kurt-vd/linux-can/iproute2-j1939
with <gitorious-branch-name> something like 'j1939-v3.6'.
In contrast to the kernel, I never modify iproute2 besides j1939 stuff,
so this would work very fine.
Even an .tgz export could work then.

Kind regards,
Kurt

Re: CAN j1939 library doubts

[Giox79]

Kurt Van Dijck <kurt.van.dijck <at> eia.be> writes:

> 
> On Thu, Mar 14, 2013 at 04:20:08PM +0000, Giox79 wrote:
> > Kurt Van Dijck <kurt.van.dijck <at> eia.be> writes:
> > 
> > In order to integrate your libs to my kernel, I was supposing to make a diff 
> > between source file, looking mainly at can and iproute2, merge the diffs and 
> > build the whole system.
> > Do you think this is the right approach?
> no. I (just) prepared the repositories to allow easy merges.
> 
> follow these steps (@Marc, can you just verify the 'git' calls):
> 
> git clone your kernel, or get a stable one
> 	$ git clone http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git
> ... this takes time
> 	$ cd linux-stable
> 	$ git tag
> choose a version, like v3.3, or v3.8, ...
> 	$ git checkout <chosen-version>
> 	$ git checkout -b <new-branch-name>
> This last command creates a new branch, so you can play freely.
> Now choose your branch on http://gitorious.org/~kurt-vd/linux-can/linux-can-
j1939
> , like j1939-v3.3
> 	$ git pull git://gitorious.org/~kurt-vd/linux-can/linux-can-j1939.git 
<gitorious-branch-name>
> 
> If this all went ok, then you're ready now.
> 
> The same applies for can-utils & iproute2.
> You could also clone my j1939 versions directly if you do not care about
> the precise versions, like:
> 	$ git clone -b <gitorious-branch-name> git://gitorious.org/~kurt-
vd/linux-can/iproute2-j1939
> with <gitorious-branch-name> something like 'j1939-v3.6'.
> In contrast to the kernel, I never modify iproute2 besides j1939 stuff,
> so this would work very fine.
> Even an .tgz export could work then.
> 
> Kind regards,
> Kurt
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo <at> vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 


Kurt, thanks a lot for your great help.
I will give it a try during the weekend, I have to use a customized linux kernel 
based on 3.6, so I will apply the suggested steps skipping the git to download 
official linux kernel.
I will let you know my tests results. At present time, thanks again and 
congratulation for your work.

Re: CAN j1939 library doubts

[Marc Kleine-Budde]

[-- Attachment #1: Type: text/plain, Size: 1697 bytes --]

On 03/14/2013 10:07 PM, Kurt Van Dijck wrote:
> On Thu, Mar 14, 2013 at 04:20:08PM +0000, Giox79 wrote:
>> Kurt Van Dijck <kurt.van.dijck <at> eia.be> writes:
>>
>> In order to integrate your libs to my kernel, I was supposing to make a diff 
>> between source file, looking mainly at can and iproute2, merge the diffs and 
>> build the whole system.
>> Do you think this is the right approach?
> no. I (just) prepared the repositories to allow easy merges.
> 
> follow these steps (@Marc, can you just verify the 'git' calls):

:) Looks good.

> git clone your kernel, or get a stable one
> 	$ git clone http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> ... this takes time
> 	$ cd linux-stable
> 	$ git tag
> choose a version, like v3.3, or v3.8, ...
> 	$ git checkout <chosen-version>
> 	$ git checkout -b <new-branch-name>
> This last command creates a new branch, so you can play freely.
> Now choose your branch on http://gitorious.org/~kurt-vd/linux-can/linux-can-j1939
> , like j1939-v3.3
> 	$ git pull git://gitorious.org/~kurt-vd/linux-can/linux-can-j1939.git <gitorious-branch-name>

I would add Kurt's tree as a remote, instead of pull do:

    git remote add -f kurt git://gitorious.org/~kurt-vd/linux-can/linux-can-j1939.git
    git merge kurt/<gitorious-branch-name>

If you already have a git tree, you can start with the "git remote add".

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

Re: CAN j1939 library doubts

[Giox79]

Kurt Van Dijck <kurt.van.dijck <at> eia.be> writes:

> 
> On Thu, Mar 14, 2013 at 04:20:08PM +0000, Giox79 wrote:
> > Kurt Van Dijck <kurt.van.dijck <at> eia.be> writes:
> > 
> > In order to integrate your libs to my kernel, I was supposing to make a diff 
> > between source file, looking mainly at can and iproute2, merge the diffs and 
> > build the whole system.
> > Do you think this is the right approach?
> no. I (just) prepared the repositories to allow easy merges.
> 
> follow these steps (@Marc, can you just verify the 'git' calls):
> 
> git clone your kernel, or get a stable one
> 	$ git clone http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git
> ... this takes time
> 	$ cd linux-stable
> 	$ git tag
> choose a version, like v3.3, or v3.8, ...
> 	$ git checkout <chosen-version>
> 	$ git checkout -b <new-branch-name>
> This last command creates a new branch, so you can play freely.
> Now choose your branch on http://gitorious.org/~kurt-vd/linux-can/linux-can-
j1939
> , like j1939-v3.3
> 	$ git pull git://gitorious.org/~kurt-vd/linux-can/linux-can-j1939.git 
<gitorious-branch-name>
> 
> If this all went ok, then you're ready now.
> 
> The same applies for can-utils & iproute2.
> You could also clone my j1939 versions directly if you do not care about
> the precise versions, like:
> 	$ git clone -b <gitorious-branch-name> git://gitorious.org/~kurt-
vd/linux-can/iproute2-j1939
> with <gitorious-branch-name> something like 'j1939-v3.6'.
> In contrast to the kernel, I never modify iproute2 besides j1939 stuff,
> so this would work very fine.
> Even an .tgz export could work then.
> 
> Kind regards,
> Kurt
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo <at> vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 


Kurt, thanks again for your help.
Today I received the board on which I have to develop the SW system, and the 
Kernel ported to this specific EVM is a 2.6.35.3, so I won't be able to use on 
the original patched source code the approach that you suggested, since I'm not 
using a kernel 3 release.

I think that at present time I have to change my approach. I will try to follow 
the idea that you suggested me, starting from official kernel releases, and I 
will ask EVM SW producers to help me figure out what kind of patches I will have 
to apply in order to support their HW.
Thanks again for your help, you have been really kind.
May be in the next week I will have some news.
Giovanni