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. $ cp u-boot-variscite.bbappend u-boot-fw-utils.I am trying to modify the kernel command line of a yocto image I built. SRCREV = " The commit id you'd like to use" UBOOT_SRC = "git:/// your_account/uboot-imx.git protocol=git" ![]() Update the recipes to use your remote repository instead of the default one: Using this method Yocto will take the source code from your own remote repository on github:Ĭreate your own github account and upload your proprietary U-Boot to a new repository:įor example, you can fork our repository to your own account by visiting the following link and clicking on "Fork" at the top right of the screen.Īlternatively, you can clone our repository to your local machine, and push it later to your own account. (If you do so, make sure to run " bitbake -c cleansstate virtual/bootloader" before rebuilding U-Boot) 3 Use your own remote repository on github UBOOT_SRC = "git://$" during development to get the latest commit of the branch Update the recipes to use the local repository instead of the default one:Īnd append the following lines to it (see the previous section for listing the commits or getting the latest commit id): $ git commit -a -m "my_m圆var_som_changes" Make your changes in the source code and commit them:Īfter making changes in the source code you need to commit them. Using this method Yocto will take the U-Boot source from a local repository instead of our remote ones on github: $ cp u-boot-variscite.bbappend u-boot-fw-utils.bbappend SRC_URI += "file://my_m圆var_som_changes.diff" $ cp ~/var-fslc-yocto/local_repos/uboot-imx/my_m圆var_som_changes.diff files/ $ cd ~/var-fslc-yocto/sources/meta-variscite-fslc/recipes-bsp/u-boot/ ![]() $ gedit board/variscite/m圆var_som/m圆var_som.c $ cd ~/var-fslc-yocto/local_repos/uboot-imx You can use either diff or patch file types. Make your changes in the source code and create a patch: $ cp -a tmp/work/var_som_m圆-fslc-linux-gnueabi/u-boot-variscite/1.0-r0/git/./local_repos/uboot-imx Follow the first part of step 4 of the same page, to source the setup-environment script (stop after that - don't build any image).Follow steps 1-3 of the Build Yocto from source code page.Using this method Yocto will take the source code from our default remote repository, and apply your patches to it before building it: fsl-image-gui) and the updated U-Boot will be used, or you can bitbake U-Boot alone by running " bitbake virtual/bootloader" (see the Build Yocto from source code page for the initial setup and for more info on using bitbake).ġ Add your own patches on top of our source code 3 Use your own remote repository on githubĬhoose one of the following three methods to customize U-Boot.Īfter following one of the below methods you can either bitbake your complete image (e.g.1 Add your own patches on top of our source code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |