From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: "Daniel C. A (NESTIT)" <daniel.ca@nestgroup.net>, yocto@yoctoproject.org
Subject: Re: CAN Support
Date: Wed, 08 Oct 2014 09:54:31 +0200 [thread overview]
Message-ID: <5434EDB7.8060600@dynamicdevices.co.uk> (raw)
In-Reply-To: <DFA4DD36883F5641AD609D011918C1B309CB8ABA@new-ex1.nestgroup.net>
[-- Attachment #1: Type: text/plain, Size: 2315 bytes --]
Hi Daniel,
On 07/10/2014 15:05, Daniel C. A (NESTIT) wrote:
>
> Hi,
>
> Presently im working on i.mx6 EVK for Automotive
> application. I have used 'fsl-image-gui' which was Bitbaked using
> Yocto-dora release. Since I'm worked on CAN interfaces, I got the
> following queries.
>
> 1. How to make CAN interfaces up on EVK?
>
> 2. Is there anything that I have to consider when I Bitbake
> fsl-image-gui?
>
> 3. Has fsl-image-gui got support for basic drivers like
> CAN,I2c,gpio driver., etc?
>
> 4. My intention is to test CAN Tx/rx using CAN Analyzer and EVK,
> what all are the steps for the same?Is there any document that I can
> follow?
>
>
>
> Regards,
>
> Daniel C A
>
>
>
>
Have you asked over at the meta-freescale list? As you know, driver
support is likely to be closely linked to the Linux kernel
provided for the i.MX6, and they are in the best position over on that
list to answer your question.
Whilst I don't have a definitive answer for you if you look at the
Freescale Embedded Linux bundle for the i.MX6 processor
(e.g. L3.10.17_1.0.0_LINUX_DOCS
<https://www.freescale.com/webapp/Download?colCode=L3.10.17_1.0.0_LINUX_DOCS&appType=license&location=null&fasp=1&WT_TYPE=Supporting%20Information&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=gz&WT_ASSET=Documentation&fileExt=.gz> )
you will see sections on GPIO, I2C, and FlexCAN. There are also details
in those sections on
the specific kernel configuration options that need to be turned on if
they are not already turned on by default in the
meta-freescale kernel configuration.
If the drivers you need are not built into the standard kernel by
default then you will need to make some configuration changes.
To do so you might wish to start by looking at the Yocto kernel
development manual here
http://www.yoctoproject.org/docs/1.6.1/kernel-dev/kernel-dev.html
Incidentally. I haven't yet had a chance to pick up a copy of Otavio
Salvador's book "Embedded Linux Development with Yocto Project"
but he's active with all of this over on the meta-freescale list so you
could probably do worse than take a look at his book.
e.g.
http://www.amazon.co.uk/Embedded-Linux-Development-Yocto-Project/dp/1783282339
Regards,
Alex
[-- Attachment #2.1: Type: text/html, Size: 9254 bytes --]
[-- Attachment #2.2: SECURITYINFOIMAGE.gif --]
[-- Type: image/gif, Size: 98 bytes --]
prev parent reply other threads:[~2014-10-08 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 13:05 CAN Support Daniel C. A (NESTIT)
2014-10-08 7:54 ` Alex J Lennon [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=5434EDB7.8060600@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=daniel.ca@nestgroup.net \
--cc=yocto@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.