From: Daiane Angolini <daiane.angolini@freescale.com>
To: Simone <cjb.sw.nospam@gmail.com>
Cc: "<meta-freescale@yoctoproject.org>" <meta-freescale@yoctoproject.org>
Subject: Re: canbus interface issue on imx536
Date: Mon, 2 Sep 2013 09:30:11 -0300 [thread overview]
Message-ID: <522484D3.6040100@freescale.com> (raw)
In-Reply-To: <C776209B-80B7-402B-8217-D7395E87D0E9@gmail.com>
On 09/02/2013 07:26 AM, Simone wrote:
> Dear All,
>
> I’m trying to build an image with CAN support for imx536 processor.
>
> I’ve added canutils and libsocketcan to my “.bb” image file and re built
> the image successfully.
>
> Now, I’m trying to test the interface, but I’m encountering some problems.
>
> Here below the results of the setup functions:
>
> *CMD: ip link set can0 type can bitrate 500000**
> *RESULT: ip: either "dev" is duplicate, or "bitrate" is garbage
>
> **
>
> *CMD: ifconfig can0 up**
> *RESULT: ifconfig: SIOCGIFFLAGS: No such device
>
> I saw that “*ip” *command is under */bin*instead of */sbin* where is
> actually located busybox. Is this correct?
I *almost* remember something regarding the package iproute2 and can. Do
you have this package into your image? Could you, please take a look on
this?
Do you know if you need to re-configure buxybox to include some can support?
>
> I’ve already copied the symlink to *ip* in */sbin*but with no difference.__
>
> Anyone have experience with canbus on imx53?
I'm sorry, I don't have any experience with can.... all my mental links
are from what I heard from imx-community threads.
>
> Thanks
>
> Regards
>
>
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
--
Daiane
next prev parent reply other threads:[~2013-09-02 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <018e01cea7c2$7cd87e60$76897b20$@cjb.it>
2013-09-02 10:26 ` canbus interface issue on imx536 Simone
2013-09-02 12:30 ` Daiane Angolini [this message]
2013-09-02 17:14 ` Simone
2013-09-03 14:05 ` Marco
2013-09-04 6:49 ` Simone
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=522484D3.6040100@freescale.com \
--to=daiane.angolini@freescale.com \
--cc=cjb.sw.nospam@gmail.com \
--cc=meta-freescale@yoctoproject.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.