**** BEGIN LOGGING AT Thu Apr 03 02:59:59 2014 Apr 03 03:14:32 I've got a question for you guys that I've been googling to find the answer for the last day and a half and so far nothing that I've changed has fixed it. I'm new to building Angstrom (& IRC) so go easy on me it's probably just a simple configuration that's not set correct. When I run "MACHINE=am335x-evm bitbake systemd-gnome-image" I get this "u-boot-denx was skipped: incompatible with machine am335x-evm (not in COMPATIBLE_MACHINE)" but when Apr 03 03:14:32 I run "MACHINE=beagleboard bitbake systemd-gnome-image" I don't get this error . I know these boards are close to the same and I actually have both of them and I need to be able to build an image for the am335x-evm and I can't seem to figure it out. I checked out the "remotes/origin/angstrom-v2013.12-yocto1.5" branch after trying the master branch just in case it was a stability issue but still the same problem. Apr 03 04:01:17 Some more info that might be helpful but really makes me scratch my head is this. when I run "MACHINE=am335x-evm bitbake u-boot" I get these 3 specific errors "ERROR: Nothing PROVIDES 'u-boot' ", "ERROR: u-boot was skipped: incompatible with machine am335x-evm (not in COMPATIBLE_MACHINE)", "ERROR: u-boot-ti-staging PROVIDES u-boot but was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must be set in the am335x-evm machine configuration.". So I go Apr 03 04:01:17 a check "sources/meta-ti/conf/machine/am335x-evm.conf " which has no boot configuration but has "require conf/machine/include/ti33x.inc" then I check that to find this "PREFERRED_PROVIDER_u-boot = "u-boot-ti-staging" ", and this "UBOOT_MACHINE = "am335x_evm_config" ". Does this have anything to do with DeviceTree in the newer kernels and is just ignoring the configs? or am I just missing something Apr 03 22:09:11 I've got a question for you guys that I've been googling to find the answer for the last day and a half and so far nothing that I've changed has fixed it. I'm new to building Angstrom (& IRC)so go easy on me it's probably just a simple configuration that's not set correct. When I run "MACHINE=am335x-evm bitbake systemd-gnome-image" I get this "u-boot-denx was skipped: incompatible with machine am335x-evm (not in COMPATIBLE_MACHINE)" but when I r Apr 03 22:09:11 un "MACHINE=beagleboard bitbake systemd-gnome-image" I don't get the error. I know these boards are close to the same and I actually have both of them and I need to be able to build an image for the am335x-evm board and I can't seem to figure it out. I checked out the "remotes/origin/angstrom-v2013.12-yocto1.5" branch after trying the master branch just in case it was a stability issue but still the same problem. Some more info that might be hel Apr 03 22:09:12 pful but really makes me scratch my head is this. When I run "MACHINE=am335x-evm bitbake u-boot" I get these 3 specific errors; "ERROR: Nothing PROVIDES 'u-boot'", "ERROR: u-boot was skipped: incompatible with machine am335x-evm (not in COMPATIBLE_MACHINE)", and "ERROR: u-boot-ti-staging PROVIDES u-boot but was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must be set in the am335x-evm machine configuration." So I go and check "sources/meta-ti/c Apr 03 22:09:19 onf/machine/am335x-evm.conf" which has no boot configuration but has "require conf/machine/include/ti33x.inc" then I check that file to find this, "PREFERRED_PROVIDER_u-boot = "u-boot-ti-staging", "PREFERRED_PROVIDER_virtual/kernel = "linux-ti-staging"", "UBOOT_MACHINE = "am335x_evm_config"" Also when I check "sources/meta-ti/recipes-kernel/linux/linux-ti-staging_3.12.bb" I find this; "KERNEL_DEVICETREE_ti33x = "am335x-evm.dtb am335x-evmsk.dtb am3 Apr 03 22:09:24 35x-bone.dtb am335x-boneblack.dtb"", and "COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15" Does this have anything to do with Device Tree in the newer kernels and is just ignoring the configs? or am I just missing something? **** ENDING LOGGING AT Fri Apr 04 02:59:59 2014