Well it turns out that following the Perf recipe was not only a good idea, but absolutely necessary. The perf recipe copies the code out of the work-shared kernel directory into the perf build directo

Bruce, I am running a 8 month old version of poky Dunfell, commit e32d854e. I can see the code in perf.bb where it copies over the kernel code to its directory, so I think that I have the patch you me

Hi all, I am trying to model a new recipe off of perf.bb to compile the usbip helper kernel code. I have been having issues with the work-shared/../kernel-source directory being empty, so I went back

I have successfully gotten yocto to build the USBIP-tools directory by adding a bb recipe for it, see below. However, I am sure that I have violated ever good and reasonable best practice! Therefore I

Thanks for the quick reply. I looked at the perf recipe, and its quite involved. Is there a simpler recipie to use as a template? Perhaps one of these? meta-openembedded/meta-oe/recipes-kernel/bpftool

Hi all, I've googled most of the day, but to no avail. How does one compile and add to the image the daemon usbipd? Is there a bitbake file already for this? The code is part of the kernel found in th

OK, Making some progress. I added a package_tar to my conf file and now I get a nice little tar file with my app and its helpers in it! I might also play with the do_deploy command and see if I can ju

Thanks Khem and Chuck! Yes, the application is built in its own bitbake recipe. I do see that there are rpm files built for the application, and that may be a way to upgrade the application in the fut

Hi all, As part of our image we build our company's application. This application becomes part of the image and is executed when the image boots. My question is how to have the binary image also be av

Thank you all. That is good information to know! However, I already had a custom machine config that I was able to drop the overlay into. Once I had the correct overlay enabling the sdio, the SD card

Raj, Thanks for taking the time to respond. I thought of that too. My custom Yocto build has the line to turn on the sdio in it: I have attached the entire file: config.txt.yocto However, the Rasbian

Making some progress here! I added a compiled version of the attached device tree and now the mmc1 shows up in my yocto image! Yes! Now I need to find out the secret magic in that tree that I need to

Raj, I found out how to debug the boot process of the PI from: https://github.com/raspberrypi/documentation/blob/master/hardware/raspberrypi/bootmodes/README.md by turning on the boot code debug. sed

Raj, Thanks for taking the time to respond. I thought of that too. My custom Yocto build has the line to turn on the sdio in it: I have attached the entire file: config.txt.yocto However, the Rasbian

Making some progress here! I added a compiled version of the attached device tree and now the mmc1 shows up in my yocto image! Yes! Now I need to find out the secret magic in that tree that I need to

Raj, I found out how to debug the boot process of the PI from: https://github.com/raspberrypi/documentation/blob/master/hardware/raspberrypi/bootmodes/README.md by turning on the boot code debug. sed

Raj, Thanks for taking the time to respond. I thought of that too. My custom Yocto build has the line to turn on the sdio in it: I have attached the entire file: config.txt.yocto However, the Rasbian

Raj, Thanks for taking the time to respond. I thought of that too. My custom Yocto build has the line to turn on the sdio in it: I have attached the entire file: config.txt.yocto However, the Rasbian

Hi all, I have been spinning my wheels for two days trying to discover how to enable MMC1 on a CM3. This is the one on GPIO22-27. I can boot Rasbian on the CM3 and it inits the MMC1 and its pins just