can one lay hands on a galileo-based dev kit?
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.
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================Quoted 10 lines · Robert P. J. Day
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)
Cheers, Alex
Quoted 2 lines
rday
Quoted 9 lines · Alex J Lennon
Quoted 7 lines · Robert P. J. Day
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:
Quoted 8 lines
Quoted 3 lines
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/
ok, so that tells me it's at least available, so i should be able to
track it down online around here somewhere. good to know. now if anyone in canada wants to weigh in and point me at the best source for one of these things, that would be great.
BTW, i notice that's the basic board, while this:
https://software.intel.com/en-us/iotdevkit
seems a bit more bundled. does anyone know if there is any significant difference?
as i mentioned earlier, a client wants a drivers course based on
this processor, so i'd also want the ability to possibly order a bunch of them for the students as class time approaches (whenever that is).
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================Quoted 3 lines · Robert P. J. Day
now if
anyone in canada wants to weigh in and point me at the best source for one of these things, that would be great.
Hi Robert,
I found this company in B.C. via amazon.ca which appears to have some in stock:
http://www.canakit.com/arduino-intel-galileo.html
Hope this helps.
PS. adafruit's website says they currently have them in stock:
http://www.adafruit.com/products/1637
Quoted 16 lines · Alex J Lennon
Quoted 10 lines · Robert P. J. Day
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.
Quoted 8 lines
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. :-)
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================Is this information helpful for you:
http://www.malinov.com/Home/sergey-s-blog/intelgalileo-buildinglinuximage
http://www.mouser.com/pdfdocs/Quark_BSPBuildGuide_329687_001.PDF
Alex
Is this in
On Tuesday, May 13, 2014 5:01 PM, Robert P. J. Day <[email protected]> wrote:
Quoted 16 lines · Alex J Lennon
Quoted 10 lines · Robert P. J. Day
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.
Quoted 8 lines
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. :-)
rday
Signature · 13 lines
======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== -- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
Quoted 3 lines · Vaduva alexandru
Is this information helpful for you:
http://www.malinov.com/Home/sergey-s-blog/intelgalileo-buildinglinuximage
http://www.mouser.com/pdfdocs/Quark_BSPBuildGuide_329687_001.PDF
i've seen those, both are based on using the 0.7.5 version of the
sources which i've been warned have "issues". i've already found the newer 1.0.0 version:
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23197
so in the next day or so, i'll see if that's straightforward to build and boot. just curious if anyone has already done that and can confirm, "yup, it works."
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================Quoted 31 lines · Robert P. J. Day
Quoted 14 lines · Alex J Lennon
Quoted 10 lines · Robert P. J. Day
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.
Quoted 8 lines
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?
Quoted 3 lines
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
Quoted 1 line
esent those of the company.
Quoted 8 lines · Robert P. J. Day
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. :-) rday
I've made some progress with this Robert, although I confess it was more challenging than I had expected.
I suspect I am using components that are out of sync, maybe the installed grub loader vs the images I'm trying to build and boot, or perhaps because I'm trying to target a poky distribution instead of the iot one. Maybe I'm just missing something blindingly obvious and making a rod for my back.
The Galileo didn't seem to want to play nicely from the start. I wasn't able to do the simple Arduino IDE firmware update the docs suggest - no response to query - and couldn't get any life out of UART0 on the TTL pins. The USB client was enumerating as a serial gadget once I copied across the 'magic' usbser.sys driver file on my Windows host though, so there was some proof of life at least.
(I was a bit concerned for a while I might have bricked the thing when I spotted the caveats about not powering USB without +V from the PSU. Seems a bit like an accident waiting to happen, particularly if this is being marketed as an Arduino replacement. Big red sticker on the box needed for us software engineers at the very least).
I finally realised that I needed to wire up a 3.5mm jack cable to see the Linux console (at RS232-C line levels no less....) A shame that wasn't included in the box, but I guess if you just want an Arduino-a-like (and the USB comms. actually works...) then maybe you don't need to see what's really going on.
I worked through the Quark_BSPBuildGuide as it says that "you must update the firmware the first time you use the board", which has been superceded, so I wondered if maybe I was running some old code in the supplied board that needed updating.
The capsule files from the LITTLE_LINUX_IMAGE_FirmwareUpdate_Intel_Galileo download installed OK and that got me to a shell with Poky 1.4
"Poky 9.0.2 (Yocto Project 1.4 Reference Distro) 1.4.2 clanton /dev/ttyS1"
It was picking up an IP address, I could SSH in and all was good.
...
So then I had a look at what was involved in booting from the uSD instead of the image that I presume the capsule installed to the SPI flash.
As I mentioned earlier I had grabbed meta-intel-iot-devkit. Perhaps that was my mistake. I had built up an image with the packaged layers to start, and I then tried to copy across my new build so I could boot it.
I was hoping for something a little like what is offered out of the meta-fsl-arm builds, i.e. a FAT boot partition and then an ext3 rootfs partition, but this layer seems to be using a single FAT partition with an initrd and an ext3 file mounted as root.
First I tried dd'ing the .hddimg file I had generated but that seemed to result in an EFI boot configuration that the Galileo bootloader wasn't picking up.
So I reverted to copying across my new bzImage and iot-devkit-image-clanton.ext3 as per the BSP Build docs and that at least did boot the kernel.
It then failed to mount the rootfs as it couldn't find /media/realroot in the .ext3 file. Maybe this is because I'm targeting poky not the iot distro?
With that added to my image I was able to boot to a Poky 1.5.1 shell, and I had mono 3.4.0 up and running on poky which was what I wanted to achieve.
That said I seem to have lost the ethernet interface along the way so will need to see where that has gone.
...
Lastly I've tried to eliminate use of the bblayers from meta-intel-iot-devkit in favour of my day to day Poky 1.6 daisy layers.
I needed to copy across ./meta-intel-iot-devkit/meta/conf/machine/include/ia32-base.inc to poky/meta, remove dependencies on meta-iot-devkit and meta-hob from bblayers, and remove a couple of orphaned .bbappends in meta-galileo (iot-devkit-spi-image.bbappend, iot-devkit-image.bbappend) but it seems to be building now at least.
I'm waiting to see how far that gets.
...
Apologies for the length of this, but perhaps some of it is useful. If there's an easier way to build a poky daisy distro for Galileo I'd love to hear it :)
Cheers, Alex
Quoted 65 lines · On Tuesday 13 May 2014 15:33:33 Alex J Lennon wrote:
Quoted 39 lines · Robert P. J. Day
Quoted 22 lines · Alex J Lennon
Quoted 11 lines · Robert P. J. Day
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
Quoted 8 lines
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?
Quoted 4 lines
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-devkitI 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.
Quoted 7 lines
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.
So apologies for not replying earlier - I've not been directly involved in the BSP for Galileo, but I have been providing support for the team doing the IoT DevKit work. You should be able to build images for Galileo using what's in meta-intel-iot-devkit directly; you could also use the layers within it separately using your own separate OE-Core / Poky tree, but it's not really designed to be used in that way. If you really want to do it separately you should take care to use all three layers (meta-clanton-bsp, meta-galileo, and meta-iot-devkit) and set your DISTRO = "iot-devkit".
FYI as of yesterday there is also now a "devkit-daisy" branch which is updated on top of the daisy branch, but it is a work-in-progress at the moment so don't be too surprised if something breaks (although it did work well for me here).
To create a partitioned image file suitable for dd'ing to an SD card, the easiest way is to use the wic tool - for example, to build a final image from an image called "iot-devkit-image" that you just built using the build system:
wic create iot-devkit -e iot-devkit-image
("iot-devkit" here points to scripts/lib/image/canned-wks/iot-devkit.wks which tells wic how to format the image).
I'd recommend you then use the ddimage helper script that we have since it provides a measure of assurance that you've got the right device before overwriting its contents, for example:
sudo ../scripts/contrib/ddimage /var/tmp/wic/build/iot-devkit-NNNNN-mmcblkp0.direct /dev/mmcblk0
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 95 lines · Paul Eggleton
Quoted 63 lines · On Tuesday 13 May 2014 15:33:33 Alex J Lennon wrote:
Quoted 38 lines · Robert P. J. Day
Quoted 21 lines · Alex J Lennon
Quoted 11 lines · Robert P. J. Day
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
Quoted 8 lines
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?
Quoted 4 lines
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-devkitI 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.Quoted 7 lines
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.So apologies for not replying earlier - I've not been directly involved in the BSP for Galileo, but I have been providing support for the team doing the IoT DevKit work. You should be able to build images for Galileo using what's in meta-intel-iot-devkit directly; you could also use the layers within it separately using your own separate OE-Core / Poky tree, but it's not really designed to be used in that way. If you really want to do it separately you should take care to use all three layers (meta-clanton-bsp, meta-galileo, and meta-iot-devkit) and set your DISTRO = "iot-devkit".
FYI as of yesterday there is also now a "devkit-daisy" branch which is updated on top of the daisy branch, but it is a work-in-progress at the moment so don't be too surprised if something breaks (although it did work well for me here).
To create a partitioned image file suitable for dd'ing to an SD card, the easiest way is to use the wic tool - for example, to build a final image from an image called "iot-devkit-image" that you just built using the build system:
wic create iot-devkit -e iot-devkit-image
("iot-devkit" here points to
scripts/lib/image/canned-wks/iot-devkit.wkswhich tells wic how to format the image).
Quoted 9 lines
I'd recommend you then use the ddimage helper script that we have since it provides a measure of assurance that you've got the right device before overwriting its contents, for example:
sudo ../scripts/contrib/ddimage
/var/tmp/wic/build/iot-devkit-NNNNN-mmcblkp0.direct/dev/mmcblk0Cheers,
Paul
Thanks Paul. Very useful, particularly the image creation incantations. I'll give this a go as soon as I can make some time.
I really want to be building the same distro for multiple targets here (i.MX6, RPi, Galileo, qemu), but Poky is breaking for me.
I'm using my day to day daisy layers with the meta-intel-iot-devkit ones I believe I need as follows: http://pastebin.com/7rFQpdiX
The latest build failure was a missing grub which I suppose is to be expected as I'm not using the correct/recommended distro (?)
Can you comment on what the main difference is in intention/what's supplied between the poky reference distro and the iot-devkit distro?
Cheers, Alex
Quoted 112 lines · On Friday 16 May 2014 11:29:34 Alex J Lennon wrote:
Quoted 102 lines · Paul Eggleton
Quoted 67 lines · On Tuesday 13 May 2014 15:33:33 Alex J Lennon wrote:
Quoted 40 lines · Robert P. J. Day
Quoted 23 lines · Alex J Lennon
Quoted 11 lines · Robert P. J. Day
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-kit
s/
7919611/(I'm actually a bit confused about how the Galileo IoT collection of meta-foo layers relates to the primary meta-foo
Quoted 8 lines
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?
Quoted 4 lines
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-devkitI 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.Quoted 7 lines
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.So apologies for not replying earlier - I've not been directly involved in the BSP for Galileo, but I have been providing support for the team doing the IoT DevKit work. You should be able to build images for Galileo using what's in meta-intel-iot-devkit directly; you could also use the layers within it separately using your own separate OE-Core / Poky tree, but it's not really designed to be used in that way. If you really want to do it separately you should take care to use all three layers (meta-clanton-bsp, meta-galileo, and meta-iot-devkit) and set your DISTRO = "iot-devkit".
FYI as of yesterday there is also now a "devkit-daisy" branch which is updated on top of the daisy branch, but it is a work-in-progress at the moment so don't be too surprised if something breaks (although it did work well for me here).
To create a partitioned image file suitable for dd'ing to an SD card, the easiest way is to use the wic tool - for example, to build a final image from an image called "iot-devkit-image" that you just built using the build
system:
wic create iot-devkit -e iot-devkit-image("iot-devkit" here points to
scripts/lib/image/canned-wks/iot-devkit.wkswhich tells wic how to format the image).Quoted 8 lines
I'd recommend you then use the ddimage helper script that we have since it provides a measure of assurance that you've got the right device before
overwriting its contents, for example:
sudo ../scripts/contrib/ddimage/var/tmp/wic/build/iot-devkit-NNNNN-mmcblkp0.direct/dev/mmcblk0>
Cheers,
Paul
Quoted 8 lines
Thanks Paul. Very useful, particularly the image creation incantations. I'll give this a go as soon as I can make some time.
I really want to be building the same distro for multiple targets here (i.MX6, RPi, Galileo, qemu), but Poky is breaking for me.
I'm using my day to day daisy layers with the meta-intel-iot-devkit ones I believe I need as follows: http://pastebin.com/7rFQpdiX
I think you should probably have meta-iot-devkit as well even if you don't use DISTRO = "iot-devkit".
Quoted 2 lines
The latest build failure was a missing grub which I suppose is to be expected as I'm not using the correct/recommended distro (?)
When you say "missing grub" can you be more specific about the error?
Quoted 2 lines
Can you comment on what the main difference is in intention/what's supplied between the poky reference distro and the iot-devkit distro?
Well, looking at the distro config itself there's actually not that much in it of real substance, but there are some bbappends in the meta-iot-devkit layer, hence why I'd suggest including it.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 3 lines
I think you should probably have meta-iot-devkit as well even if you don't use DISTRO = "iot-devkit".
I added meta-iot-devkit in to bblayers and when I bitbake iot-devkit-image (MACHINE=clanton, DISTRO=iot-devkit) I get orphaned bbappends.
ERROR: No recipes available for:
/data_drive/imx6/rootfs_builder/sources/meta-intel-iot-devkit/meta-iot-devkit/recipes-extended/ethtool/ethtool_3.10.bbappend
/data_drive/imx6/rootfs_builder/sources/meta-intel-iot-devkit/meta-iot-devkit/recipes-core/busybox/busybox_1.21.1.bbappend
ERROR: Command execution failed: Exited with 1
Quoted 3 lines
Quoted 2 lines
The latest build failure was a missing grub which I suppose is to be expected as I'm not using the correct/recommended distro (?)
When you say "missing grub" can you be more specific about the error?
When I take out meta-iot-devkit and build core-image-minimal for MACHINE=clanton, DISTRO=iot-devkit I get
ERROR: Unable to install packages. Command '/data_drive/imx6/rootfs_builder/buildgalileoiot2/tmp/sysroots/i686-linux/usr/bin/smart --data-dir=/data_drive/imx6/rootfs_builder/buildgalileoiot2/tmp/work/clanton-poky-linux/core-image-minimal-initramfs/1.0-r0/rootfs/var/lib/smart install -y busybox@i586 initramfs-live-install-efi@i586
run-postinsts@all initramfs-live-install@i586 udev@i586
initramfs-live-boot@clanton base-passwd@i586' returned 1:
Loading cache...
Updating cache... ########################################
[100%]
Computing transaction...error: Can't install initramfs-live-install-1.0-r9@i586: no package provides grub
There seem to be some grub recipes in meta-clanton-bsp though so... (?) Maybe if I put meta-intel-iot-devkit back in and sort out the bbappends... (?)
Cheers,
Alex
Quoted 7 lines · On Friday 16 May 2014 12:17:33 Alex J Lennon wrote:
Quoted 2 lines
I think you should probably have meta-iot-devkit as well even if you don't use DISTRO = "iot-devkit".
I added meta-iot-devkit in to bblayers and when I bitbake iot-devkit-image (MACHINE=clanton, DISTRO=iot-devkit) I get orphaned bbappends.
Quoted 8 lines
ERROR: No recipes available for:
/data_drive/imx6/rootfs_builder/sources/meta-intel-iot-devkit/meta-iot-devki t/recipes-extended/ethtool/ethtool_3.10.bbappend
/data_drive/imx6/rootfs_builder/sources/meta-intel-iot-devkit/meta-iot-devki t/recipes-core/busybox/busybox_1.21.1.bbappend ERROR: Command execution
failed: Exited with 1
Are you trying to use these layers with 1.6 / master? Until the devkit-daisy branch was pushed, the devkit was based on 1.5 (dora).
Quoted 20 lines
Quoted 4 lines
Quoted 2 lines
The latest build failure was a missing grub which I suppose is to be expected as I'm not using the correct/recommended distro (?)
When you say "missing grub" can you be more specific about the error?
When I take out meta-iot-devkit and build core-image-minimal for MACHINE=clanton, DISTRO=iot-devkit I get
ERROR: Unable to install packages. Command '/data_drive/imx6/rootfs_builder/buildgalileoiot2/tmp/sysroots/i686-linux/us r/bin/smart --data-dir=/data_drive/imx6/rootfs_builder/buildgalileoiot2/tmp/work/clanto n-poky-linux/core-image-minimal-initramfs/1.0-r0/rootfs/var/lib/smart install -y busybox@i586 initramfs-live-install-efi@i586 run-postinsts@all initramfs-live-install@i586 udev@i586 initramfs-live-boot@clanton base-passwd@i586' returned 1:
Loading cache...
Updating cache... ########################################
[100%]
Quoted 6 lines
Computing transaction...error: Can't install initramfs-live-install-1.0-r9@i586: no package provides grub
There seem to be some grub recipes in meta-clanton-bsp though so... (?) Maybe if I put meta-intel-iot-devkit back in and sort out the bbappends... (?)
If you get this error, it means there is a grub recipe but no package called "grub" was produced. I don't recieve this error here, but FWIW I don't have a grub ipk package in tmp/deploy/ipk either, so this is expected and it shouldn't be looking for the package.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
On Fri, 16 May 2014, Paul Eggleton wrote:
... snip ...
Quoted 8 lines
So apologies for not replying earlier - I've not been directly involved in the BSP for Galileo, but I have been providing support for the team doing the IoT DevKit work. You should be able to build images for Galileo using what's in meta-intel-iot-devkit directly; you could also use the layers within it separately using your own separate OE-Core / Poky tree, but it's not really designed to be used in that way. If you really want to do it separately you should take care to use all three layers (meta-clanton-bsp, meta-galileo, and meta-iot-devkit) and set your DISTRO = "iot-devkit".
should any of these layers be added to:
http://layers.openembedded.org/layerindex/branch/master/layers/
for findability?
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================Quoted 9 lines · Paul Eggleton
Quoted 8 lines · On Friday 16 May 2014 12:17:33 Alex J Lennon wrote:
Quoted 2 lines
I think you should probably have meta-iot-devkit as well even if you don't use DISTRO = "iot-devkit".
I added meta-iot-devkit in to bblayers and when I bitbake iot-devkit-image (MACHINE=clanton, DISTRO=iot-devkit) I get orphaned bbappends.
ERROR: No recipes available for:
Quoted 8 lines
Quoted 6 lines
/data_drive/imx6/rootfs_builder/sources/meta-intel-iot-devkit/meta-iot-devki t/recipes-extended/ethtool/ethtool_3.10.bbappend
/data_drive/imx6/rootfs_builder/sources/meta-intel-iot-devkit/meta-iot-devki t/recipes-core/busybox/busybox_1.21.1.bbappend ERROR: Command execution
failed: Exited with 1Are you trying to use these layers with 1.6 / master? Until the devkit-daisy branch was pushed, the devkit was based on 1.5 (dora).
Yes I'm on daisy nowadays - http://pastebin.com/4C8DWHJw
Quoted 21 lines
Quoted 21 lines
Quoted 3 lines
Quoted 2 lines
The latest build failure was a missing grub which I suppose is to be expected as I'm not using the correct/recommended distro (?)
When you say "missing grub" can you be more specific about the error?
When I take out meta-iot-devkit and build core-image-minimal for MACHINE=clanton, DISTRO=iot-devkit I get
ERROR: Unable to install packages. Command '/data_drive/imx6/rootfs_builder/buildgalileoiot2/tmp/sysroots/i686-linux/us r/bin/smart --data-dir=/data_drive/imx6/rootfs_builder/buildgalileoiot2/tmp/work/clanto n-poky-linux/core-image-minimal-initramfs/1.0-r0/rootfs/var/lib/smart install -y busybox@i586 initramfs-live-install-efi@i586 run-postinsts@all initramfs-live-install@i586 udev@i586 initramfs-live-boot@clanton base-passwd@i586' returned 1:
Loading cache...
Updating cache... ########################################
[100%]Computing transaction...error: Can't install initramfs-live-install-1.0-r9@i586: no package provides grub
Quoted 7 lines
Quoted 3 lines
There seem to be some grub recipes in meta-clanton-bsp though so... (?) Maybe if I put meta-intel-iot-devkit back in and sort out the bbappends... (?)
If you get this error, it means there is a grub recipe but no package called "grub" was produced. I don't recieve this error here, but FWIW I don't have a grub ipk package in tmp/deploy/ipk either, so this is expected and it shouldn't be looking for the package.
I've just checked out the new devkit-daisy branch and that's built me core-image-minimal successfully with MACHINE=clanton, DISTRO=iot-devkit
Many thanks!
I'll kick off another build of my mono image for poky and see what happens...
Cheers,
Alex
Quoted 9 lines · Paul Eggleton
So apologies for not replying earlier - I've not been directly involved in the BSP for Galileo, but I have been providing support for the team doing the IoT DevKit work. You should be able to build images for Galileo using what's in meta-intel-iot-devkit directly; you could also use the layers within it separately using your own separate OE-Core / Poky tree, but it's not really designed to be used in that way. If you really want to do it separately you should take care to use all three layers (meta-clanton-bsp, meta-galileo, and meta-iot-devkit) and set your DISTRO = "iot-devkit".
possibly a silly question, but what are the dependencies between
those three layers? i'm used to seeing layer dependencies listed in a layer's "layer.conf" file. if i look at the meta-iot-devkit layer, its layer.conf file says nothing about dependencies, but one of its kernel recipes, "linux-yocto-clanton_3.8.bbappend", is clearly a reference to a kernel recipe in the meta-clanton-bsp layer.
i would thus have expected to see that dependency listed in the
layer.conf file. has something about listing layer dependencies changed while i wasn't looking?
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================Quoted 18 lines · On Friday 16 May 2014 08:51:35 Robert P. J. Day wrote:
Quoted 9 lines · Paul Eggleton
So apologies for not replying earlier - I've not been directly involved in the BSP for Galileo, but I have been providing support for the team doing the IoT DevKit work. You should be able to build images for Galileo using what's in meta-intel-iot-devkit directly; you could also use the layers within it separately using your own separate OE-Core / Poky tree, but it's not really designed to be used in that way. If you really want to do it separately you should take care to use all three layers (meta-clanton-bsp, meta-galileo, and meta-iot-devkit) and set your DISTRO = "iot-devkit".
possibly a silly question, but what are the dependencies between
those three layers? i'm used to seeing layer dependencies listed in a layer's "layer.conf" file. if i look at the meta-iot-devkit layer, its layer.conf file says nothing about dependencies, but one of its kernel recipes, "linux-yocto-clanton_3.8.bbappend", is clearly a reference to a kernel recipe in the meta-clanton-bsp layer.
Quoted 3 lines
i would thus have expected to see that dependency listed in the
layer.conf file. has something about listing layer dependencies changed while i wasn't looking?
No, nothing has changed. The separation here is probably not as clearly defined as it ought to be. I guess what I'd say is, you shouldn't look at this as a fully worked example of how to structure things; it was put together out of various pieces and intended to be used as a whole rather than separate components.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 14 lines · On Friday 16 May 2014 07:37:01 Robert P. J. Day wrote:
On Fri, 16 May 2014, Paul Eggleton wrote:
... snip ...
Quoted 9 lines
So apologies for not replying earlier - I've not been directly involved in the BSP for Galileo, but I have been providing support for the team doing the IoT DevKit work. You should be able to build images for Galileo using what's in meta-intel-iot-devkit directly; you could also use the layers within it separately using your own separate OE-Core / Poky tree, but it's not really designed to be used in that way. If you really want to do it separately you should take care to use all three layers (meta-clanton-bsp, meta-galileo, and meta-iot-devkit) and set your DISTRO = "iot-devkit".
Quoted 5 lines
should any of these layers be added to:
http://layers.openembedded.org/layerindex/branch/master/layers/
for findability?
Whilst I would usually say yes, in this case I'm not sure that would be ideal. The layer index is designed to index individual layers, but the layers within this repository aren't meant to be used separately; people who do try to do that will have to know what they are doing. This isn't the canonical source of the BSP either - the official BSP is what gets published as a tarball and its usage is documented in the Quark BSP build guide.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 23 lines · Paul Eggleton
Quoted 18 lines · On Friday 16 May 2014 08:51:35 Robert P. J. Day wrote:
Quoted 9 lines · Paul Eggleton
So apologies for not replying earlier - I've not been directly involved in the BSP for Galileo, but I have been providing support for the team doing the IoT DevKit work. You should be able to build images for Galileo using what's in meta-intel-iot-devkit directly; you could also use the layers within it separately using your own separate OE-Core / Poky tree, but it's not really designed to be used in that way. If you really want to do it separately you should take care to use all three layers (meta-clanton-bsp, meta-galileo, and meta-iot-devkit) and set your DISTRO = "iot-devkit".
possibly a silly question, but what are the dependencies between
those three layers? i'm used to seeing layer dependencies listed in a layer's "layer.conf" file. if i look at the meta-iot-devkit layer, its layer.conf file says nothing about dependencies, but one of its kernel recipes, "linux-yocto-clanton_3.8.bbappend", is clearly a reference to a kernel recipe in the meta-clanton-bsp layer.Quoted 3 lines
i would thus have expected to see that dependency listed in the
layer.conf file. has something about listing layer dependencies changed while i wasn't looking?
Quoted 5 lines
No, nothing has changed. The separation here is probably not as clearly defined as it ought to be. I guess what I'd say is, you shouldn't look at this as a fully worked example of how to structure things; it was put together out of various pieces and intended to be used as a whole rather than separate components.
fair enough ... i should be able to test this by end of day.
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================