This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SK-AM62B-P1: [YOCTO] [SDK_9.02.01.09] Yocto build fail with out of memory

Part Number: SK-AM62B-P1

Dear Ti

we use yocto builds AM62x

When we build  bitbake  tisdk-default-image, it fail with out of memory.

I followed below command based on "software-dl.ti.com/.../Overview_Building_the_SDK.html

git clone git.ti.com/.../oe-layersetup.git tisdk


cd tisdk
./oe-layertool-setup.sh -f configs/processor-sdk/processor-sdk-kirkstone-chromium-09.02.01.09-config.txt

cd build
source conf/setenv

MACHINE=am62xx-evm bitbake -k tisdk-default-image

I have questions.

1. Running task number

In the build log, it shows below info. "running tasks 10917" is it normal number ?

"Currently 12 running tasks (4507 of 10917)  41% |################################################################  "

2. Hard disk usage

My HDD is 250G, it uses 200G even though the progress rate is 40%.

Is it normal ?

/dev/nvme0n1p2 244506940 207842848 24171036 90% /

BR

Jace

  • Hi Jace,

    Yocto builds can be very resource intensive, especially as you are building one of the full-featured image (tisdk-default-image).

    1. First, you really need a larger disk drive, Nowadays fast 2TB-sized NMVe drive is very reasonably priced and provide ample storage for Yocto builds and your other activities.

    2. Make sure you have enough RAM. 32GB, or better 64GB. (*)

    3. Make sure "swap" is enabled It's common to set this up to double the amount of memory available to the system (e.g., with 32GB DDR, setup swap size to 32GB, resulting in a total of 64GB of memory) (*)

    4. You can try to disable "Chromium" from the build, which is very heavy and resource-intensive to build, and may not be something you need, see here how to do that: https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/09_02_01_09/exports/docs/linux/Overview_Building_the_SDK.html#build-steps

    (*) As a workaround for not having enough RAM (points 3/4) you can also reduce the amount of parallelism in the the Yocto build, which often will get things going, by adding something like the below to your conf/local.conf file...

    Fullscreen
    1
    2
    BB_NUMBER_THREADS ?= "4"
    PARALLEL_MAKE ?= "-j 4"
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Regards, Andreas

    (ref: LCPD-38065)