From: Eric Nelson <eric.nelson@boundarydevices.com>
To: diego <diego.gonzalez@horus.es>, meta-freescale@yoctoproject.org
Subject: Re: FlexCAN not working
Date: Fri, 11 Oct 2013 08:16:12 -0700 [thread overview]
Message-ID: <5258163C.6050705@boundarydevices.com> (raw)
In-Reply-To: <5257E0EE.80802@horus.es>
Hi Diego,
On 10/11/2013 04:28 AM, diego wrote:
> Hello everybody,
>
> I'm trying to test FlexCAN on Sabrelite imx6 board without success.
> Those are the steps followed :
>
> 1) Comprobed that linux-imx has CAN drivers enable
> 2) Added on the image the packages:canutils,libsocketcan and iproute2
> 3) Tested the Flex can with canconfig and cantest.
>
> Everything seems ok, even I can see transmitted frames incremented.
> However there's not singnal on the oscilloscope.
>
> I don't now why is not working. Any ideas or suggestions?
>
Can you forward your kernel version (/proc/version) and output
of /proc/cpuinfo?
Some early versions of SABRE Lite used a discontinued Freescale
CAN PHY, and there's some code in board-mx6_nitrogen6x.c to
detect which is in use. If you're using the old board-mx6_sabrelite.c,
that detection code isn't present.
Checking dmesg will tell you:
dmesg | grep can
https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.0.35_4.1.0/arch/arm/mach-mx6/board-mx6_nitrogen6x.c#L1377
Regards,
Eric
next prev parent reply other threads:[~2013-10-11 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 11:28 FlexCAN not working diego
2013-10-11 15:16 ` Eric Nelson [this message]
2013-10-11 18:15 ` Jose Mª Ferreiro
2013-10-11 18:41 ` Eric Nelson
2013-10-11 18:55 ` Jose Mª Ferreiro
2013-10-11 20:56 ` Wayne T. Schellekens
2013-10-11 22:11 ` Eric Nelson
2013-10-14 9:40 ` Jose Mª Ferreiro
2013-10-15 0:30 ` HDMI on SABRE Lite (was FlexCAN not working) Eric Nelson
2013-10-18 11:33 ` FlexCAN not working diego
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=5258163C.6050705@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=diego.gonzalez@horus.es \
--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.