|
u-boot-fslc 2022.10 failed with exit code '137' (using too much memory)
#yocto
#kirkstone
#meta-freescale
#u-boot
Solution: https://github.com/Freescale/meta-freescale/issues/1318#issuecomment-1333725448
Solution: https://github.com/Freescale/meta-freescale/issues/1318#issuecomment-1333725448
|
By
Livius
· #24896
·
|
|
u-boot-fslc 2022.10 failed with exit code '137' (using too much memory)
#yocto
#kirkstone
#meta-freescale
#u-boot
You know you can reduce the memory consumption by: 1) Lowering the number of parallel makes (using PARALLEL_MAKE in local.conf or maybe in a .bbappend for the package) 2) Limit the number of bitbake t
You know you can reduce the memory consumption by: 1) Lowering the number of parallel makes (using PARALLEL_MAKE in local.conf or maybe in a .bbappend for the package) 2) Limit the number of bitbake t
|
By
Bas Mevissen
· #24895
·
|
|
u-boot-fslc 2022.10 failed with exit code '137' (using too much memory)
#yocto
#kirkstone
#meta-freescale
#u-boot
Yes, i reported it in GitHub also https://github.com/Freescale/meta-freescale/issues/1318 I have no any other Linux desktop machine to try it in a different host PC but i could see my eyes in htop GUI
Yes, i reported it in GitHub also https://github.com/Freescale/meta-freescale/issues/1318 I have no any other Linux desktop machine to try it in a different host PC but i could see my eyes in htop GUI
|
By
Livius
· #24894
·
|
|
u-boot-fslc 2022.10 failed with exit code '137' (using too much memory)
#yocto
#kirkstone
#meta-freescale
#u-boot
Em ter., 29 de nov. de 2022 às 06:33, Livius <egyszeregy@...> escreveu: You reported this on GH too so we'll keep it there and reply there.
Em ter., 29 de nov. de 2022 às 06:33, Livius <egyszeregy@...> escreveu: You reported this on GH too so we'll keep it there and reply there.
|
By
Otavio Salvador
· #24893
·
|
|
u-boot-fslc 2022.10 failed with exit code '137' (using too much memory)
#yocto
#kirkstone
#meta-freescale
#u-boot
New u-boot-fslc_2022.10.bb is failed always with exit code '137' which means the available memory has been exhausted, so 16 GB DDR4 RAM memory was not enough for this single recipe build on Ubuntu 20.
New u-boot-fslc_2022.10.bb is failed always with exit code '137' which means the available memory has been exhausted, so 16 GB DDR4 RAM memory was not enough for this single recipe build on Ubuntu 20.
|
By
Livius
· #24892
·
|
|
Yocto browser require low memory footprints
#yocto
#meta-freescale
I've used 'links' browser, which is very light-weight but also very minimal features. If your pre-rendered html is fairly simple, it might work out; probably worth taking a look at how some example pa
I've used 'links' browser, which is very light-weight but also very minimal features. If your pre-rendered html is fairly simple, it might work out; probably worth taking a look at how some example pa
|
By
S. Lockwood-Childs
· #24853
·
|
|
Yocto browser require low memory footprints
#yocto
#meta-freescale
You might try WPEWebKit. I've used it before and it's good for a very minimal display of web content while still being fairly full featured. > >
You might try WPEWebKit. I've used it before and it's good for a very minimal display of web content while still being fairly full featured. > >
|
By
Joshua Watt
· #24852
·
|
|
Yocto browser require low memory footprints
#yocto
#meta-freescale
Hi , We are using Yocto Linux 3.0 zeus branch on imx6 based SOC. we are looking for light weight web browser since our HW platform has only 1 GB of RAM supports. as of now we are using chromium versio
Hi , We are using Yocto Linux 3.0 zeus branch on imx6 based SOC. we are looking for light weight web browser since our HW platform has only 1 GB of RAM supports. as of now we are using chromium versio
|
By
yogeshbsa89@...
· #24851
·
|
|
Comunity vs i.MX
#yocto
Hello, Em qui., 23 de jun. de 2022 às 14:41, Константин Еременок <eremenok.k.by@...> escreveu: There was never a war. Both serves different goals. Lack of people to help maintaining the website.
Hello, Em qui., 23 de jun. de 2022 às 14:41, Константин Еременок <eremenok.k.by@...> escreveu: There was never a war. Both serves different goals. Lack of people to help maintaining the website.
|
By
Otavio Salvador
· #24850
·
|
|
Comunity vs i.MX
#yocto
Hello Konstantin, <eremenok.k.by@...> wrote: AFAIK, there was no war declared, not at least that I was aware of when I started using Yocto Project and `meta-freescale` layer. ;-) NXP is lacking
Hello Konstantin, <eremenok.k.by@...> wrote: AFAIK, there was no war declared, not at least that I was aware of when I started using Yocto Project and `meta-freescale` layer. ;-) NXP is lacking
|
By
Andrey Zhizhikin
· #24849
·
|
|
Comunity vs i.MX
#yocto
Hi there. I have not followed Yocto iMX for some time. Today I found in the document "i.MX Yocto Project User's Guide" from NXP such text: "i.MX joined the Yocto Project community providing a release
Hi there. I have not followed Yocto iMX for some time. Today I found in the document "i.MX Yocto Project User's Guide" from NXP such text: "i.MX joined the Yocto Project community providing a release
|
By
Константин Еременок
· #24848
·
|
|
GStreamer Cross compilation for iMX8M Mini Yocto
#compilation
#hardknott
#imx7ulpevk
#meta-freescale
#yocto
The default GStreamer provided in iMX8 yocto only supports the command line it does not support GStreamer C code hence I need to cross-compile the GStreamer library for iMX8M Mini Yocto. I tried addin
The default GStreamer provided in iMX8 yocto only supports the command line it does not support GStreamer C code hence I need to cross-compile the GStreamer library for iMX8M Mini Yocto. I tried addin
|
By
maneeshsingh1920@...
· #24821
·
|
|
How to Cross Compile GStreamer for NXP iMX8M Mini using Yocto
#meta-freescale
#imx7ulpevk
#yocto
#hardknott
Hi, Is there anyone on this forum who can help me ? Thanks, Maneesh
Hi, Is there anyone on this forum who can help me ? Thanks, Maneesh
|
By
maneeshsingh1920@...
· #24795
·
|
|
How to Cross Compile GStreamer for NXP iMX8M Mini using Yocto
#meta-freescale
#imx7ulpevk
#yocto
#hardknott
Hi Sir, I am using NXP iMX8M Mini EVK and Yocto imx-linux-hardknott imx-5.10.52 version. Default GStreamer provided in NXP iMX BSP does not support the GStreamer C application it only supports the com
Hi Sir, I am using NXP iMX8M Mini EVK and Yocto imx-linux-hardknott imx-5.10.52 version. Default GStreamer provided in NXP iMX BSP does not support the GStreamer C application it only supports the com
|
By
maneeshsingh1920@...
· #24794
·
|
|
Error when compiling an image based on imx8 when machine configuration file doesn't include "imx8" in the name
#dunfell
#compilation
#meta-freescale
#yocto
Hi, I'm getting an error when compiling an extended version of fsl-image-multimedia-full.bb for an i.mx8 based machine. However, I get this error only when the machine configuration file (which is exa
Hi, I'm getting an error when compiling an extended version of fsl-image-multimedia-full.bb for an i.mx8 based machine. However, I get this error only when the machine configuration file (which is exa
|
By
asconcepcion
· #24664
·
|
|
kernel-localversion, removing custom def configs, with linux-boundary
#meta-freescale
#compilation
#yocto
Thank you for your efforts, The latest commit has resolved the issue.
Thank you for your efforts, The latest commit has resolved the issue.
|
By
Daniel Cox
· #24663
·
|
|
#yocto #meta-freescale #qca9377 #imx7ulpevk #gatesgarth
#yocto
#meta-freescale
#qca9377
#imx7ulpevk
#gatesgarth
Hello, Em sex., 16 de abr. de 2021 às 09:55, <jovanalukovic0@...> escreveu: Please check if this happens on master; please report it here https://github.com/Freescale/meta-freescale/issues if it
Hello, Em sex., 16 de abr. de 2021 às 09:55, <jovanalukovic0@...> escreveu: Please check if this happens on master; please report it here https://github.com/Freescale/meta-freescale/issues if it
|
By
Otavio Salvador
· #24662
·
|
|
kernel-localversion, removing custom def configs, with linux-boundary
#meta-freescale
#compilation
#yocto
Hello, Em sex., 16 de abr. de 2021 às 09:55, <daniel.cox@...> escreveu: Reported here https://github.com/Freescale/meta-freescale/issues/733
Hello, Em sex., 16 de abr. de 2021 às 09:55, <daniel.cox@...> escreveu: Reported here https://github.com/Freescale/meta-freescale/issues/733
|
By
Otavio Salvador
· #24661
·
|
|
kernel-localversion, removing custom def configs, with linux-boundary
#meta-freescale
#compilation
#yocto
Hi, We have seen an issue in a recent update to the dunfell branch. Our image uses the linux-boundary, which requires the linux-imx.inc files. What we have found thought with the latest dunfull branch
Hi, We have seen an issue in a recent update to the dunfell branch. Our image uses the linux-boundary, which requires the linux-imx.inc files. What we have found thought with the latest dunfull branch
|
By
Daniel Cox
· #24658
·
|
|
#yocto #meta-freescale #qca9377 #imx7ulpevk #gatesgarth
#yocto
#meta-freescale
#qca9377
#imx7ulpevk
#gatesgarth
Hi, I am trying to include qca9377 module in my image (yocto-gatesgarth). I am using command bitbake imx-image-full, and i added two lines in my local.conf file: MACHINE_FEATURES += " qca9377" IMAGE_I
Hi, I am trying to include qca9377 module in my image (yocto-gatesgarth). I am using command bitbake imx-image-full, and i added two lines in my local.conf file: MACHINE_FEATURES += " qca9377" IMAGE_I
|
By
jovanalukovic0@...
· #24657
·
Edited
|