I'll try to summarise as best the steps I've gone through and then the issue i'm having:
1) Intel provided SD card image working:
- got the latest SD Card image, installed on the sd card, booted no problem, loaded arduino script to enable networking (telnetd -l /bin/sh needs to be run - then I can ssh into the board through network port).
- Upgraded board firmware to 1.0.4 -- https://downloadcenter.intel.com/downloads/eula/24748/Intel-Galileo-Firmware-and-Drivers-1-0-4?httpDown=http%3A%2F%2Fdownloadmirror.intel.com%2F24748%2Feng%2FIntelGalileoFirmwareUpdater-1.0.4-Windows.zip
- to note this SD card image has 2 partitions - 53MB (1st partition, primary, FAT32, boot flag enabled) , 1.44 GB (2nd partition, primary, EXT3)
2) build my own system
- I'm using for reference: Intel ® Quark™ SoC X1000 Board Support Package (BSP) Build and Software User Guide; release 1.2.1; feb 2016
- Downloaded latest (1.2.1) BSP from here: https://downloadcenter.intel.com/download/23197/Intel-Quark-BSP
- set up a Debian 7.9 build machine and went through all steps in user's guide above, section 6 to create file system and kernel using Yocto project
- final steps here say to simply copy 5 files over the the SD card -- see 1st attachment
- no mention of 2 partitions on the SD card. only info I could find is that it just should be fat32 and copy over files.
Problems/other things i tried:
- the main problem i'm having is that if i copy this straight over it doesn't boot.
- looking at the console output when booting sees the build get stuck looking for something on "Waiting for root device /dev/mmcblk0p2". Extrapolating and many nights of investigating, I can see that in the Intel provided SD card image, we have a complete filesystem on the second partition, however in the user guide above there is NO MENTION of this at all.
- On the intel SD card image, there is also no ext3 image file in the first partition
- I tried some other things given the above, I figured that perhaps the ext3 file needed to be extracted out and then copied to the second SD card partition. I tried this, however it still got stuck at the point waiting for the /dev/mmcblk0p2 device. See attachment log of the boot for this version - compiled system, with files copied to 1st partition of SD card and image file extracted to the second partition. Note to do this (for others interested) i used the command (on my build system) to mount to a directory then copied over all files: mount -o loop image-full-quark.ext3 /directory/to/mount/
- 3rd attachment is the intel sd card boot up log. Note big differences between mine and theirs
- next thing I noticed was that in my build there WAS NO FILE in the /boot directory in my second partition (from my image-full-quark.ext3 filesystem image file). The file is called: vmlinux-3.8.7-yocto-standard
- My guess is that file is used to load up on boot, but as mentioned above there is NO reference to any of this in the docco about anything about a second partition on the SD card. I couldn't seem to find any file like this on my build - so any help on why I don't have this file in my build image greatly appreciated. -- NOTE i was building everything from defaults from the steps in the doc user guide above (ie: running the setup.sh scripts, environment vars setup etc then bitbake image-full)
Overall I was assuming that the latest downloads for the SD card image would be the same as the latest full SD card compile following the steps in the latest user guide above. It's VERY different and I would like to know why and how I can get my image compiling so the SD card boots up so I can start do other things i need to do like customizing some kernel options, etc -- i don't want to do that until the base install works!