![]() If you need a version of this manual for a different You can see all Yocto Project major releases by Older than the Yocto Project version with which you the search might have returned a manual much Version of the manual might not be the one you want If you located this manual through a web search, the Manuals from the site are more up-to-date than manualsĭerived from the Yocto Project released TAR files. To be sure you have the latest version of the manual patch file to m圆sabre_common.patch, it did not help.Yocto Project Board Support Package (BSP) Developer's Guide The patch was not applied.īut the file git/include/configs/m圆sabre_common.h was untouched by the patch. > the old string ("DO I SEE THIS?") was still there. regenerate the whole image (I tested that the patch was applied by modifying the copied. patch file(s) to sources/meta-fsl-arm/recipes-bsp/u-boot/u-boot-imx/. create a patch with the new work, with "git format-patch -1" (or whichever number of commits) when it works, commit with "git commit -a -sign-off" and a meaningful message test with recompiling the module (-c compile -f) and regenerating the image make changes in build/tmp/work/im圆qsabresd-poky-linux-gnueabi/u-boot-fslc/v2014.01-r0/git/ Is the following workflow acceptable, or should it be different: What is the best practice to create a patch for this file, and make sure the patch is applied at the next build? I understand from the doc ( Yocto Project Development Manual) that I have to make a patch, but I do not find the information there precise enough for me. This is great, but the manual changes will disappear the next time I sync the repo, or at the next clean. After a:Īnd a new upload, the command was updated! What was wrong is that I only rebuilt u-boot, and didn't regenerate the image. sdcard file to my SD card, stopped the boot at the u-boot prompt, and "print" gave: NOTE: Tasks Summary: Attempted 214 tasks of which 213 didn't need to be rerun and all succeeded. NOTE: Tainting hash to force rebuild of task /home/gauthier/numpy-fsl-community-bsp/sources/meta-fsl-arm/recipes-bsp/u-boot/u-boot-fslc_2014.01.bb, do_compile + "netboot=echo Booting from net DO I SEE THIS?. "build/tmp/work/im圆qsabresd-poky-linux-gnueabi/u-boot-fslc/v2014.01-r0/git/inlude/configs/m圆sabre_common.h", to add a string to CONFIG_EXTRA_ENV_SETTINGS, netboot: I *think* that working with patches is the correct workflow, is that correct? How would you do it? ![]() I have attempted patches but I can't seem to make it work. Modifying the source file in tmp/work/./git worked, but I want to make the change stay. Short version of what I still have troubles with: It feels like I am making wrong assumptions, if anyone could shed a light. Is the patch even being applied, how can I check this? And where is it applied, in that case? I have no such file, not that I could find at least. ![]() ![]() I noticed several patch files there: sources/meta-fls-arm/recipes-bsp/u-boot/u-boot-imx/, but first I am not sure how bitbake sorts out which one to apply, second the u-boot parameters I end up with are not the ones in the relevant patch (m圆q_sabresd-*.patch).įurthermore, the patch is on the file include/configs/m圆q_sabresd.h. INIT: Id "mxc6" respawning too fast: disabled for 5 minutes The kernel command line did not change, and it did break the startup. I also tested to modify sources/meta-fls-arm/conf/machine/include/im圆sabresd-common.inc (changing ttymxc0 only to see if that would get through to the final image) but it had no positive effect. I went to the machine config (as per the doc above) there: sources/meta-fls-arm/conf/machine/include, but I did not find where in there I should put the APPEND. Where are my current u-boot parameters defined? What is the best way to make changes to them? For example, you can add some helpful debug information doing the following:ĪPPEND += "printk.time=y initcall_debug debug""īut this is not very helpful. The Linux kernel command line is typically specified in the machine config using the APPEND variable. " How do I change the Linux kernel command line? Now that this is working, I would like to change my yocto build itself so that the kernel command line gets its correct parameters without me doing it manually. To achieve that I manually changed the u-boot variables with setenv and saveenv. The im圆q_sabresd booted fine so I went on and made it take its rootfs from NFS. I baked a core-image-x11 image and put it on my SD card with dd. I am trying to modify the kernel command line of a yocto image I built. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |