But if I do, should I stick with the 3.8 kernel? Or 3.12 or 3.13?
If you want ‘full’ cape support stick with 3.8… If you are just using
usb/ethernet with simple capes* (usart/i2c/spi) use 3.13 (i’m working
on adding most capes to 3.13 at the moment…) ignore 3.12…
Sounds good, I only have one of the breadboard capes which I have enabled two USARTS on. so 3.13
sounds like where I should start playing.
My assumption is the build scripts assume I am running linux. Can dual boot
to this on my main dev machine to Linux Mint, or could use my NUC which I
think right now I have running Ubuntu 13.04.
The scripts assume linux, mostly tested on debian jessie, but works in ubuntu…
Note the “image-builder” works best native on arm hardware… (qemu is
too bit rotten for 100% reliably between distro versions)
So to build for my one BBBk, I would be better off doing the build on another ARM based machine running Debian. Probably my best option would be to use my Odroid U2? It has a 16gb emmc on it and i can plug in a microsd… I am currently running Ubuntu on it, but can install Debian.
A few more things to investigate:
If I build an image and write it to an SD card, can I try it out (boot
off of it) without it overwriting the EMMC?
There will be a traditional “flasher” which will overwrite the eMMC
and a secondary “4gb img” which you can dump to your microSD and it’ll
run on that.
So if I am reading this correct, Each time will overwrite the eMMC… I was hoping to be able to maybe have the ability to choose either boot emmc or boot SD. I am probably missing something.
> But if I do, should I stick with the 3.8 kernel? Or 3.12 or 3.13?
If you want 'full' cape support stick with 3.8.. If you are just using
usb/ethernet with simple capes* (usart/i2c/spi) use 3.13 (i'm working
on adding most capes to 3.13 at the moment..) ignore 3.12..
Sounds good, I only have one of the breadboard capes which I have enabled
two USARTS on. so 3.13
sounds like where I should start playing.
> My assumption is the build scripts assume I am running linux. Can dual
> boot
> to this on my main dev machine to Linux Mint, or could use my NUC which
> I
> think right now I have running Ubuntu 13.04.
The scripts assume linux, mostly tested on debian jessie, but works in
ubuntu..
Note the "image-builder" works best native on arm hardware.. (qemu is
too bit rotten for 100% reliably between distro versions)
So to build for my one BBBk, I would be better off doing the build on
another ARM based machine running Debian. Probably my best option would be
to use my Odroid U2? It has a 16gb emmc on it and i can plug in a
microsd... I am currently running Ubuntu on it, but can install Debian.
Ubuntu is fine.. Remember this is just the "image-builder" it uses
debootstrap in a chroot to create a new fresh/clean image..
The kernel on the other hand.. you can build anywhere, native, cross, etc..
> A few more things to investigate:
> 1) If I build an image and write it to an SD card, can I try it out
> (boot
> off of it) without it overwriting the EMMC?
There will be a traditional "flasher" which will overwrite the eMMC
and a secondary "4gb img" which you can dump to your microSD and it'll
run on that.
So if I am reading this correct, Each time will overwrite the eMMC... I was
hoping to be able to maybe have the ability to choose either boot emmc or
boot SD. I am probably missing something.
Well technically it's only one file different in the first boot partition:
So if it finds "flash-eMMC.txt" in the first partition it'll flash the
eMMC... It's easier to just push out two images with different
functions then explainnig.. "mount ; rm flash-eMMC.txt ; "
