From: swapnil <patilswa@gmail.com>
To: linux-can@vger.kernel.org
Subject: Re: AW: Need support J1939 protocol support to my kernel (v3.8 on BeagleBone Black)
Date: Thu, 28 Nov 2013 04:49:38 +0000 (UTC) [thread overview]
Message-ID: <loom.20131128T053030-487@post.gmane.org> (raw)
In-Reply-To: 20131112100222.GA3748@vandijck-laurijssen.be
Kurt Van Dijck <kurt.van.dijck <at> eia.be> writes:
>
> Hey all,
>
> Maybe Michael was a bit too fast.
> I suspect you tried to merge the j1939 linux kernel into can-utils ?
>
> On Tue, Nov 12, 2013 at 01:10:04AM +0000, swapnil wrote:
> > Michael Luxen <mluxen <at> gmx.net> writes:
> >
> > >
> > > Hello Swapnil,
> > >
> > > I've success with building the J1939 stack on my BBB based on Debian
using
> > these steps:
> > >
> > > git clone git://gitorious.org/linux-can/can-utils.git
> > > cd can-utils
> > > --- get J1939 stuff ---
>
> So you're in the can-utils directory now. Merge can-utils-j1939
>
> $ git remote add j1939 git://gitorious.org/~kurt-vd/linux-can/can-j1939-
utils.git
> $ git remote update j1939
> $ git merge j1939/master
>
> build can-utils now.
> And then:
>
> $ cd ..
> $ git clone <your kernel>
> $ cd linux (or your linux kernel directory)
>
> and then these steps apply.
>
> > > git remote add j1939 git://gitorious.org/~kurt-vd/linux-can/linux-can-
j1939.git
> > > git remote update j1939
> > > --- depending on kernel ---
> > > git merge j1939/v3.6
> > > ...or…
> > > git merge j1939/v3.8
>
> Maybe this will work better.
>
> 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
>
>
Hi Kurt ,
Thanks for adding the information on elinux.org/J1939
I am able to build the kernal for begabone black using j1939
but when i tried to build iproute2-j1939
root@arm:/home/ubuntu/OBDscan/iproute2-j1939# make
make[1]: Entering directory `/home/ubuntu/OBDscan/iproute2-j1939/misc'
gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -I../include -
DRESOLVE_HOSTNAMES -DLIBDIR=\"/usr/lib/\" -I/usr//usr/include -o arpd
arpd.c ../lib/libnetlink.a ../lib/libutil.a -ldb -lpthread
arpd.c:19:20: fatal error: db_185.h: No such file or directory
#include <db_185.h>
^
compilation terminated.
make[1]: *** [arpd] Error 1
make[1]: Leaving directory `/home/ubuntu/OBDscan/iproute2-j1939/misc'
make: *** [all] Error 2
i am getting above error.
i tried to install sudo apt-get install db4.7-util
but did not worked
if y
>ip link set can0 j1939 on
Error: either "dev" is duplicate, or "j1939" is a garbage.
can you please help me.
I am really trying hard to build it on begalbone black
Thank You
Swapnil
next prev parent reply other threads:[~2013-11-28 4:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 16:14 AW: Need support J1939 protocol support to my kernel (v3.8 on BeagleBone Black) Michael Luxen
2013-11-12 1:10 ` swapnil
2013-11-12 10:02 ` Kurt Van Dijck
2013-11-28 4:49 ` swapnil [this message]
2013-11-28 8:52 ` Kurt Van Dijck
2013-12-04 22:10 ` swapnil
2013-12-05 19:59 ` Kurt Van Dijck
-- strict thread matches above, loose matches on Subject: below --
2014-01-15 16:14 swapnil
2014-01-16 21:43 ` Kurt Van Dijck
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.20131128T053030-487@post.gmane.org \
--to=patilswa@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