Hi,
I am using FSL Linux 3.10.17 with iMX6Q device and can successfully build the SD image and boot the device.
Then I tried to reconfigure Linux kernel.
I did the following steps:
However, nothing seems happened.
Can someone help to share what are the steps needed for re-configure and re-build the kernel binaries?
Regards,
yf
Solved! Go to Solution.
Alejandro,
Thank you for the pointer, I checked the URL and tried to identify the proper "defconfig" under "sources/meta-fsl-arm" folder and got:
meta-fsl-arm/recipes-kernel/linux/linux-timesys-3.0.15/defconfig
meta-fsl-arm/recipes-kernel/linux/linux-imx-3.10.9/mx6/defconfig
meta-fsl-arm/recipes-kernel/linux/linux-imx-2.6.35.3/imx28evk/defconfig
meta-fsl-arm/recipes-kernel/linux/linux-imx-2.6.35.3/mx5/defconfig
meta-fsl-arm/recipes-kernel/linux/linux-imx-2.6.35.3/imx23evk/defconfig
meta-fsl-arm/recipes-kernel/linux/linux-imx-3.0.35/mx6q/defconfig
meta-fsl-arm/recipes-kernel/linux/linux-imx-3.0.35/mx6dl/defconfig
meta-fsl-arm/recipes-kernel/linux/linux-imx-3.0.35/mx6sl/defconfig
meta-fsl-arm/recipes-kernel/linux/linux-imx-3.0.35/mx6s/defconfig
meta-fsl-arm/recipes-kernel/linux/linux-fslc/mxs/defconfig
meta-fsl-arm/recipes-kernel/linux/linux-fslc/defconfig
I am not sure which is the one for 3.10.17 version kernel on imx6q device? None of these defconfig files look like the one in build folder
520fc9c85e261a9959853268ecbe3d28 linux-imx/3.10.17-r0/defconfig
520fc9c85e261a9959853268ecbe3d28 linux-imx/3.10.17-r0/git/arch/arm/configs/imx_v7_defconfig
Does this mean that 3.10.17 version is not using any "defconfig" under "sources" folder?
Regards,
yanfeng
Hello,
Kernel 3.10.17 uses ‘device tree' and imx_v7_defconfig.
Luis
Luis,
So this means for 3.10.17, we can simply do:
1) bitbake -c cleansstate linux_imx
2) bitbake -c menuconfig linux_imx to config the kernel and save result upon exit
3) bitbake -c deploy linux_imx to build kernel w/ new config updated in step #2
Is this what you mean?
There is no "defconfig" thing to touch in "sources/" folder, right?
Regards,
yanfeng
Hello,
No, you only have to follow the Task 5 document. You can use menuconfig to modify configuration.
If wanted to build manually the kernel, for development for example in a separated folder, starting from default config, you could do:
export PATH=$PATH:/home/yocto/fsl-yocto-bsp/imx6q_image_test/tmp/sysroots/i686-linux/usr/bin/cortexa9hf-vfp-neon-poky-linux-gnueabi
make -j4 ARCH=arm CROSS_COMPILE=arm-poky-linux-gnueabi- imx_v7_defconfig
(If you need change something) make -j 4 ARCH=arm CROSS_COMPILE=arm-poky-linux-gnueabi- menuconfig
(If need clean) make -j4 ARCH=arm CROSS_COMPILE=arm-poky-linux-gnueabi- mrproper
make -j4 ARCH=arm CROSS_COMPILE=arm-poky-linux-gnueabi- LOADADDR=10008000 uImage
make -j4 ARCH=arm CROSS_COMPILE=arm-poky-linux-gnueabi- modules
make -j4 ARCH=arm CROSS_COMPILE=arm-poky-linux-gnueabi- INSTALL_MOD_PATH=<PATH to rootfs> modules_install
Regards,
Luis