While I've read enough to think I understand git, I get confused when it's applied to real situations like Yocto. If I look at the Yocto Development Manual, Appendix A, A.5.2.4 Changing Recipes-kernel

I have the meta-cedartrail image running on hardware (Marshalltown board). To make the serial console work, I have in the machine/cedartrail.conf file: SERIAL_CONSOLE = "115200 ttyS0" this works fine,

I created a "How DO I" for adding recipes, and added it to the wiki. Please review for correctness if you like. Jim A

Based on what I've discovered about the use of IMAGE_INSTALL in local.conf, I'll opt for POKY_EXTRA_INSTALL += "hello" That option worked. So now I can better understand this. Thanks all. Would the ma

okay, I got a clean build, but hello was not in the final image even though I had: EXTRA_IMAGE_FEATURES += "hello" in the local.conf. I ran hob against this and could see that hello was an option, but

Thanks for a clear explanation. This is an area I'm sure my customers will struggle with. I think another problem I was having was the recipe was called helloworld, but the application seems to be jus

Now I have gotten by the fetching but the license file information in the .bb file from the example is incorrect. I can't see from the Reference manual License section enough information for me to cre

Duh! Now that makes sense. Sorry for being so dense. That's what happens when your been programing since Fortran was at the 1.0 level. Brain goes soft. Jim A

I got the layer created like you said, but the test had a fetch problem and it just locked up there. Had to control-C out of it. Console below: jim@ubuntu-x64:/build/mycdv-minimal$ bitbake helloworld

I got the layer created like you said, but the test had a fetch problem and it just locked up there. Had to control-C out of it. Console below: jim@ubuntu-x64:/build/mycdv-minimal$ bitbake helloworld

I'm trying to understand the concept of creating a recipe and having it included in the build I do. For example, suppose I want to create the meta-intel/meta-cedartrail BSP with the core-image-minimal

Thanks for these suggestions. I'll look them over and figure out what I want to do. Jim A

I've noticed that the meta-intel BSP come up with the default terminal, serial console user, etc. as root. What would it take to make my own BSP that was exactly the same, but the default was a not ad

I'm going to retest all this and try some of these tricks when I have some time. If I get any more errors with the local repository, I'll post them. Thanks, Jim A

I'm not sure it does. I don't want poky to do more work. I have my download directory, $DL_DIR, outside my build directory so I can keep it run to run, as mentioned in the comments in local.conf. I wa

I have used both git and the tarball methods of bitbaking projects, all of them derivatives of the examples in the Yocto documentation. I was having issues using the local clone of the Yocto kernel gi

Jim Abernathy Looks good to me.

This worked fine for me. one typo in step (5) ext3 and not text3, but these are good instructions. How do we get them put into the README.hardware instead of the directdisk section that doesn't work a

The README.hardware file in the poky directory talks about creating images on 2 types of disk for the Atom based PCs like the n450. The one I've successfully tested is the core-image-sato on a USB key

I'll test this out and see. I'm plan on keeping this system on a UPS anyway. Jim S