From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: yocto@yoctoproject.org
Subject: Re: can one lay hands on a galileo-based dev kit?
Date: Tue, 13 May 2014 15:33:33 +0100 [thread overview]
Message-ID: <53722D3D.4030902@dynamicdevices.co.uk> (raw)
In-Reply-To: <alpine.LFD.2.11.1405130954351.7299@localhost>
On 13/05/2014 14:56, Robert P. J. Day wrote:
> On Tue, 29 Apr 2014, Alex J Lennon wrote:
>
>> On 29/04/2014 17:34, Robert P. J. Day wrote:
>>> i've just been asked to design a linux device drivers course based
>>> on the arduino-compatible intel galileo processor, so my first TODO
>>> item is to lay hands on a galileo-based dev kit, for which this looks
>>> like the obvious choice:
>>>
>>> https://software.intel.com/en-us/iotdevkit
>>>
>>> but that page says "upcoming". does it exist? my normal go-to source
>>> up here, digikey.ca, shows zero in stock. where can i lay hands on
>>> one (if possible)? thanks.
>> If it helps I had a Galileo Dev Kit delivered from RS (UK) a couple of
>> days ago.
>>
>> http://uk.rs-online.com/web/p/processor-microcontroller-development-kits/7919611/
>>
>> (I'm actually a bit confused about how the Galileo IoT collection of
>> meta-foo layers relates to the primary meta-foo
>> sources, as I can't seem to find an independent meta-clanton ;ayer
>> which I guess I'd need. Early days yet, but am planning
>> on working through this as soon as I get some time as I want to test a
>> build with meta-moo support on Galileo)
> i finally have time to play with this, and am interested in using
> yocto to build a bootable system for the galileo. i see that there is
> a version "1.0.0" of the firmware for this board -- is there a
> convenient yocto recipe that involves just downloading the layer info
> and not what looks like the current entire tarball that's stuffed with
> all the sources?
>
> i suspect that, within a day or two, i'll figure that out once i
> start digging around. if it's already documented somewhere, that would
> be even better. :-)
Still a bit up in the air with this here Robert.
I've not been able to work out if there's a primary source for
meta-clanton independent
of the packaged iot layer, so I grabbed meta-intel-iot-devkit in its
entirety from
git://git.yoctoproject.org/meta-intel-iot-devkit
I built one of my own custom mono images based on core-image-sato
thinking I could
put that on a uSD and it would "just boot" (oh the optimism... :)
No joy there so I took a quick look through that Quark BSP guide and it
seemed to be
talking about booting some odd kind of image format from a file on uSD.
I stepped back and had it build the iot-devkit-image which seemed to
need be to make a
change to an image dependency on python to python-core.
That's where I had to leave it as I ran out of time. I was planning on
hooking up serial to the
Tx/Rx pins to see if anything is happening there, getting something
building, then replacing
the meta-intel-iot-devkit references in BBLAYERS (aside from
meta-clanton) with the daisy
layers I'm using on a day to day basis.
Will let you know once I get a bit of life out of it!
Cheers, Alex
> esent those of the company.
next prev parent reply other threads:[~2014-05-13 14:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 16:34 can one lay hands on a galileo-based dev kit? Robert P. J. Day
2014-04-29 16:43 ` Alex J Lennon
2014-04-29 16:50 ` Robert P. J. Day
2014-04-30 2:43 ` Trevor Woerner
2014-04-30 2:46 ` Trevor Woerner
2014-05-13 13:56 ` Robert P. J. Day
2014-05-13 14:16 ` Vaduva alexandru
2014-05-13 14:20 ` Robert P. J. Day
2014-05-13 14:33 ` Alex J Lennon [this message]
2014-05-16 10:11 ` Paul Eggleton
2014-05-16 10:29 ` Alex J Lennon
2014-05-16 10:47 ` Paul Eggleton
2014-05-16 11:17 ` Alex J Lennon
2014-05-16 11:32 ` Paul Eggleton
2014-05-16 12:15 ` Alex J Lennon
2014-05-16 11:37 ` Robert P. J. Day
2014-05-16 13:29 ` Paul Eggleton
2014-05-16 12:51 ` Robert P. J. Day
2014-05-16 13:10 ` Paul Eggleton
2014-05-16 13:58 ` Robert P. J. Day
2014-05-13 20:12 ` Alex J Lennon
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=53722D3D.4030902@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=rpjday@crashcourse.ca \
--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.