From: Patrick Menschel <menschel.p@posteo.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
"Misra Pankaj Kumar (RBEI/EEA2)" <Pankaj.Kumar@in.bosch.com>
Cc: linux-can <linux-can@vger.kernel.org>
Subject: Re: bcmserver.c usage and preconditions
Date: Wed, 30 Mar 2016 15:49:43 +0200 [thread overview]
Message-ID: <56FBD977.5040100@posteo.de> (raw)
In-Reply-To: <56FBBFA3.8000907@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
Thanks Oliver,
based on the usage examples in the file header I thought it reads from
stdin ;-P
I have it working now on both BananaPi and BeagleBoneBlack.
Regards,
Patrick
Am 30.03.2016 um 13:59 schrieb Oliver Hartkopp:
> Hi Patrick,
>
> On 03/30/2016 10:32 AM, Patrick Menschel wrote:
>> Hi Pankaj,
>>
>> CAN Bus is functional in both directions, rx and tx .
>>
>> 1. cansend works properly
>> 2. candump also works properly
>>
>> I'm just trying to verify if it's just me or the bcm.
>
> It's you :-)
>
>>>
>>> 2. then start bcmserver
>>>
>>> ~$ bcmserver
>>>
>>> 3. and input the line
>>>
>>> ~$ can0 A 1 0 123 8 11 22 33 44 55 66 77 88
>>>
>>> but unfortunately I don't get any output at all.
>
> The bcmserver creates an IP server listening on port 28600 on localhost.
>
> So you would need to connect this server e.g. with netcat first and then
> type the according command (with '<' and '>' tags!!) into the netcat shell.
>
> Regards,
> Oliver
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3709 bytes --]
prev parent reply other threads:[~2016-03-30 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 6:01 bcmserver.c usage and preconditions Patrick Menschel
2016-03-30 7:57 ` Misra Pankaj Kumar (RBEI/EEA2)
2016-03-30 8:32 ` Patrick Menschel
2016-03-30 11:59 ` Oliver Hartkopp
2016-03-30 13:49 ` Patrick Menschel [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=56FBD977.5040100@posteo.de \
--to=menschel.p@posteo.de \
--cc=Pankaj.Kumar@in.bosch.com \
--cc=linux-can@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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.