• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 100 subscribers
  • Views 359 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

PROCESSOR-SDK-AM62X: Recommended HDD size

Ryuuichi machida
Guru 13170 points

Part Number: PROCESSOR-SDK-AM62X

Hello,

I would like to try full sdk build based on bitbake.
At first, I tried to set HDD size definition is 256GB.
However, I got error for size when I performed full SDK build.

It is not for AM62, but I found following information on other device SDK.

https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-j7200/08_06_00_11/exports/docs/j7200/linux/Overview_Building_the_SDK.html
The build will ~250GB of hard disk space for building the tisdk-default-image. 

From above, I assume that I need more HDD size than 256GB for full SDK build, however if you have recommended HDD size information for following usecase which is described in SDK web documentation each other ?

tisdk-core-bundle : For full SDK
tisdk-default-image : For target filesystem
tisdk-base-image : For minimal target filesystem
meta-toolchain-arago-tisdk : Devkit

BR,

  • +1
    TI__Guru 70472 points
    Ryuuichi machida said:
    tisdk-core-bundle : For full SDK

    First, you don't need to build tisdk-core-bundle (formerly known as arago-core-tisdk-bundle) at all, it is only used for creating a huge executable installer for the entire SDK like you can download from the ti.com SDK download folders. This build target is provided for completeness/reference sake (and since it's co-located with all the other open source Yocto stuff it's organically provided, if you will), and not really needed by anybody outside TI. This build target also has by far the largest needs in terms of space for the build to succeed, easily requiring 100's of GBs as you found out.

    A user of our SDK usually only builds two different types of artifact with our Yocto sources:

    1. Different target images (tisdk-default-image, tisdk-base-image, etc.), and
    2. The cross-toolchain installer ("devkit") associated with / customized for a certain image (called meta-toolchain-arago-tisdk in our Yocto Dunfell v8.x-based SDKs)

    For building (1) and (2) about 200GB or so should be plenty if building the largest one of the images that we provide which is tisdk-default-image. Note that you can reduce space requirements when you use a shared state cache (see SSTATE_DIR variable) between different builds and even SDK versions and machines. To do that this folder should be located OUTSIDE your temporary build folder. You can update that variable in your local.conf file. This will also allow you to delete all the build's temp folders after a complete build, and any re-build of any component that hasn't been changed will just pull the binary artifacts stored during previous builds from SSTATE_DIR into the image, greatly eliminating the need for any "space-expensive" rebuilds of the individual artifacts that go into a final image. Here's some more background on this concept:

    https://docs.yoctoproject.org/singleindex.html#shared-state-cache 

    https://www.thegoodpenguin.co.uk/blog/improving-yocto-build-time/ (scroll down to "Shared State Cache")

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Guru 13170 points

    Hellp Andreas,

    Thank you for your reply.
    Understood.

    BR,