|
MACHINE and inc files
You do not need to include anything. Maybe I did not understand you. Can you provide a file structure/use case? Gabriele NOTE: I won't be able to reply till Tuesday 23rd
You do not need to include anything. Maybe I did not understand you. Can you provide a file structure/use case? Gabriele NOTE: I won't be able to reply till Tuesday 23rd
|
By
Gabriele
· #49698
·
|
|
MACHINE and inc files
Hi Tomek, you can specify machine-specific variables/function with the following syntax: <PROPERTY_NAME>_[MACHINE_NAME] = "value" ex: MAGIC_NUMBER_velismate-x21 = "12345" inside your temp.bb Regards,
Hi Tomek, you can specify machine-specific variables/function with the following syntax: <PROPERTY_NAME>_[MACHINE_NAME] = "value" ex: MAGIC_NUMBER_velismate-x21 = "12345" inside your temp.bb Regards,
|
By
Gabriele
· #49693
·
|
|
SDKPATH: how to change?
Ciao Mauro, you can change the directory during installation ./poky-glibc-x86_64-your-image-armv7at2hf-neon-toolchain-2.6.2.sh -d /install/path More info with ./poky-glibc-x86_64-your-image-armv7at2hf
Ciao Mauro, you can change the directory during installation ./poky-glibc-x86_64-your-image-armv7at2hf-neon-toolchain-2.6.2.sh -d /install/path More info with ./poky-glibc-x86_64-your-image-armv7at2hf
|
By
Gabriele
· #48748
·
|
|
Support UBI u-boot
Hi, I compile uboot using the Yocto generated SDK. Simply source /opt/poky/.../env-script make -j4 If you just want to run the menuconfig run make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfi
Hi, I compile uboot using the Yocto generated SDK. Simply source /opt/poky/.../env-script make -j4 If you just want to run the menuconfig run make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfi
|
By
Gabriele
· #48299
·
|
|
Support UBI u-boot
Hi, Sorry, I never tried that approach. As far as I know uboot (usually virtual/bootloader) does not have a task to run menuconfig directly from bitbake. I usually have a local clone of uboot and I si
Hi, Sorry, I never tried that approach. As far as I know uboot (usually virtual/bootloader) does not have a task to run menuconfig directly from bitbake. I usually have a local clone of uboot and I si
|
By
Gabriele
· #48288
·
|
|
Support UBI u-boot
Hi JH, have you tried what we suggested you in your last thread? More specifically adding your defconfig and tweaking it through menuconfig. and then specify the UBOOT_MACHINE. However you should be a
Hi JH, have you tried what we suggested you in your last thread? More specifically adding your defconfig and tweaking it through menuconfig. and then specify the UBOOT_MACHINE. However you should be a
|
By
Gabriele
· #48285
·
|
|
How to make a local patch without a commit number, or will not be possible?
Hi JH, since uboot migrated to kconfig for a while, I'd suggest you to patch the Freescale's one with your custom machine defconfig and then specify the UBOOT_MACHINE = "my_machine_defconfig" in your
Hi JH, since uboot migrated to kconfig for a while, I'd suggest you to patch the Freescale's one with your custom machine defconfig and then specify the UBOOT_MACHINE = "my_machine_defconfig" in your
|
By
Gabriele
· #48246
·
|
|
permanently supercede kernel config with one of my own creation
Add this line to your machine config: >>>>>>>>> # Install the module in /lib/modules/${uname -r}/ MACHINE_EXTRA_RRECOMMENDS = " kernel-modules" <<<<<<<<< Gabriele
Add this line to your machine config: >>>>>>>>> # Install the module in /lib/modules/${uname -r}/ MACHINE_EXTRA_RRECOMMENDS = " kernel-modules" <<<<<<<<< Gabriele
|
By
Gabriele
· #48209
·
|
|
permanently supercede kernel config with one of my own creation
Hi Kent, There must be a recipe for your "vendor supplied" kernel, why not extending it with an append, so you will be able to ship your own defconfig? Assuming your vendor kernel recipe is called lin
Hi Kent, There must be a recipe for your "vendor supplied" kernel, why not extending it with an append, so you will be able to ship your own defconfig? Assuming your vendor kernel recipe is called lin
|
By
Gabriele
· #48199
·
|
|
lost busybox mysteriously
Ok this sounds good. Actually the kernel needs a series of module (both built in or loadable) when mounting the partitions (read from fstab for example), so, in case of ubifs: - Mtd partitions are rec
Ok this sounds good. Actually the kernel needs a series of module (both built in or loadable) when mounting the partitions (read from fstab for example), so, in case of ubifs: - Mtd partitions are rec
|
By
Gabriele
· #48175
·
|
|
lost busybox mysteriously
HI JH, - Can you stop on uboot and try "nand bad"? This will list the bad blocks on your device. - How do you flash your ubi partition(s)? - During boot, does ubifs layer complain about the partition
HI JH, - Can you stop on uboot and try "nand bad"? This will list the bad blocks on your device. - How do you flash your ubi partition(s)? - During boot, does ubifs layer complain about the partition
|
By
Gabriele
· #48172
·
|
|
Getting linux kernel version
Hi all, is there a standard way to get the Linux kernel version (output of `uname -r`)? I'm using a custom kernel recipe that inherit from kernel class. I need to get that version in a task executed a
Hi all, is there a standard way to get the Linux kernel version (output of `uname -r`)? I'm using a custom kernel recipe that inherit from kernel class. I need to get that version in a task executed a
|
By
Gabriele
· #47523
·
|
|
Adding libstdc++-dev path?
Forget about the DEPENDS, I used that in another scenario. I tried the following recipe: FILESEXTRAPATHS_prepend := "${THISDIR}/files:" SRC_URI = "file://main.cpp" do_compile() { # For example purpose
Forget about the DEPENDS, I used that in another scenario. I tried the following recipe: FILESEXTRAPATHS_prepend := "${THISDIR}/files:" SRC_URI = "file://main.cpp" do_compile() { # For example purpose
|
By
Gabriele
· #47520
·
|
|
Adding libstdc++-dev path?
Hi, have you tried adding libstdc++-dev to the recipe dependencies? DEPENDS += " libstdc++-dev" This will bring libstdc++ package into recipe sysroot and no extra actions will be needed on compilation
Hi, have you tried adding libstdc++-dev to the recipe dependencies? DEPENDS += " libstdc++-dev" This will bring libstdc++ package into recipe sysroot and no extra actions will be needed on compilation
|
By
Gabriele
· #47517
·
|
|
Yocto build to add root password
Hi JH, Take a look at this manual section, last example: https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#ref-classes-extrausers Regards, Gabriele
Hi JH, Take a look at this manual section, last example: https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#ref-classes-extrausers Regards, Gabriele
|
By
Gabriele
· #47405
·
|
|
Installing a Kernel module.
Hi Shravan, as pointed out in the documentation [1], you need to specify module_conf_* and KERNEL_MODULE_PROBECONF. Here is an example coming from one of my machine: # g_multi: serial, RNDIS and sotra
Hi Shravan, as pointed out in the documentation [1], you need to specify module_conf_* and KERNEL_MODULE_PROBECONF. Here is an example coming from one of my machine: # g_multi: serial, RNDIS and sotra
|
By
Gabriele
· #47403
·
|
|
Final DISTRO_FEATURES value
Ciao, you can inspect the testdata file located next to the generated image, under deploy floder. Best regards, Gabriele
Ciao, you can inspect the testdata file located next to the generated image, under deploy floder. Best regards, Gabriele
|
By
Gabriele
· #46346
·
|
|
Opencv headers
Hi, you need to add DEPENDS = "opencv" to your recipe. This will import the needed header in your recipe sysroot. Best regards, Gabriele
Hi, you need to add DEPENDS = "opencv" to your recipe. This will import the needed header in your recipe sysroot. Best regards, Gabriele
|
By
Gabriele
· #46324
·
|
|
How to specify a different kernel for an image
Hi Patrick, thank you for the clarification. I have no idea on how to encapsulate the output of bitbake into another image in a nice and clean way. I'm pretty sure that you must run two separate bitba
Hi Patrick, thank you for the clarification. I have no idea on how to encapsulate the output of bitbake into another image in a nice and clean way. I'm pretty sure that you must run two separate bitba
|
By
Gabriele
· #46019
·
|
|
How to specify a different kernel for an image
Hi Patrick, I would approach in this way: in my meta-something/conf/machine: - machine_base.inc where I put all the standard machine configuration for production - mymachine.conf require conf/machine/
Hi Patrick, I would approach in this way: in my meta-something/conf/machine: - machine_base.inc where I put all the standard machine configuration for production - mymachine.conf require conf/machine/
|
By
Gabriele
· #46010
·
|