From: Andrew Lentvorski <bsder@allcaps.org>
To: vklein <vk4514@arcor.de>, linux-can@vger.kernel.org
Subject: Re: newbi Question: NMEA2000 and BeagleBone
Date: Thu, 26 Mar 2015 16:29:18 -0700 [thread overview]
Message-ID: <5514964E.8050401@allcaps.org> (raw)
In-Reply-To: <55140B67.9060207@arcor.de>
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
Well, I have the TowerTech TT-3201 on a BeagleBone black. It sorta
works. I can generally get 2 of the 3 interfaces to work. However, I
can't really recommend it as working out how to do this in straight
Debian instead of Angstrom has been a slog.
If I had to do it again, I'd probably try these guys.
http://www.logicsupply.com/components/beaglebone/capes/cbb-serial/
They update their user manual for it regularly, and they talk about
doing this with the latest Debian image (which you need for the latest
SocketCAN stuff).
-a
On 3/26/15, 6:36 AM, vklein wrote:
> Hi all,
>
> I searched the list about using NMEA2000 ( a subclass of J1939) and a
> BeageBone-black.
>
> Are there some newer infos how to install J1939 support on the BBB?
>
> Are there preferred transceiver boards? I Think I need only one interface.
>
> At the moment I use a Actisense NTG-1 USB and a Raspberry pi with the
> canboat software.
>
> http://wiki.openseamap.org/wiki/OpenSeaMap-dev:HW-logger/raspberry
>
> Regards
>
> Victor
> --
> 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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-03-26 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 13:36 newbi Question: NMEA2000 and BeagleBone vklein
[not found] ` <3468382.ObYm91FbAa@heinz>
[not found] ` <551432DB.8010406@arcor.de>
2015-03-26 16:35 ` Heinz-Jürgen Oertel
2015-03-26 23:29 ` Andrew Lentvorski [this message]
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=5514964E.8050401@allcaps.org \
--to=bsder@allcaps.org \
--cc=linux-can@vger.kernel.org \
--cc=vk4514@arcor.de \
/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