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.

RTOS/PROCESSOR-SDK-AM65X: processor_sdk_rtos_am65xx_5_02_00_10 build time far longer than processor_sdk_rtos_am65xx_5_01_00_11

Part Number: PROCESSOR-SDK-AM65X

Tool/software: TI-RTOS

Hi,

do you have any feedback why building 5.2 version takes much longer than 5.1? This is for build all.

Do you experience the same?

  • Thorsten,

    Can you please indicate your host build environment.  Are you building in Windows or Linux.  Our observation from nightly builds using Yocto infrastructure shows all components in PRSDK 5.01 and PRSDK 5.02 took comparable amount of time with slightly higher time for the latest SDK.

    Having said that, as an application developer, users should not have to gmake clean and build the entire SDK.  There are several libraries like CSL, driver libraries, OSAL that most customers would not need to rebuild unless there is a bug/patch they want to apply to those components.

    Additionally, there are some flags that will help reduce build times significantly. 

    Here are my notes from Processor SDK RTOS build and testing that might be useful to you to build some of the components and reduce build times:

    PDK_build_notes.docx

    The key is to do targeted builds for the platform you are working on, for the core you are working on. Hope this helps,

    Regards,

    Rahul

    PS: Also, there is an effort to enable parallel make in the  that you can track using bug ID PRSDK-4574 and PRSDK-5247. This should help reduce the build times.

  • I am reposting the notes in the document so it is searchable for other community users. These notes will be added to Software developers guide soon. 

    PRSDK PDK build notes:

    The following steps can be used in a command shell to generate the CCS projects for PDK low level drivers. Users are expected to complete component discovery in CCS before using these steps.

    Setup environment from root directory:

    <SDK_INSTALL_PATH>\processor_sdk_rtos_am65xx_x_xx_xx_xx

    setupenv.bat

     

    Optional step: SDK contains prebuilt binaries for driver and CSL libraries so there is no need to rebuild the libraries but if you need to rebuild the libraries, you can do it using gmake utility using the following options.

    gmake <target>_clean

    gmake <target>

     

    <target>: Refer to makefile in the pdk_am65xx_x_x_x\packages

     

    all csl board emac fvid2 gpio i2c mcasp mmcsd nimu pm profiling pruss sciclient spi uart udma usb sbl sa osal can be used as <target>

     

    This can take a while to build. To limit the build to A53 core, use the additional arguments as

    gmake <target> LIMIT_BOARDS=am65xx_evm LIMIT_CORES=mpu1_0 <ARGUMENTS>

     

    ARGUMENTS

    Options

    Description

    LIMIT_BOARDS

    am65xx_evm, am65xx_idk

    Supported evaluation platform

    LIMIT_SOC

    am65xx

    Supported SOC options

    LIMIT_CORES

    mcu1_0, mpu1_0

    Support for different cores

    DISABLE_RECURSE_DEPS

    yes, no

    Disable for building dependencies

    BUILD_PROFILE

    release, debug

    Build profile

     

    Caution: With DISABLE_RECURSE_DEPS=yes, you will run into link time errors if dependent component libraries are not built.

     

    To apply the options globally, set the environment variables and then invoke the build

    set LIMIT_BOARDS=am65xx_evm

    set LIMIT_SOC=am65xx

    set DISABLE_RECURSE_DEPS=yes     (Use only if dependent components are already built)

    set BUILD_PROFILE=release    (Default setting is release)

     

    Regards,

    Rahul

  • Hi,
    this is a WIN10 build. Good to know all libraries are pre-built. After first complete build we made use of the options as you stated. If you further step down to single peripheral build level you can reach 2 minutes for build time. However, not from SDK side. This works for PDK build only. For SDK build there is no option to split down to "PDK single/multiple driver level however.

    Best options for SDK level build for DRA804M EVM / DEBUG / NO LIBs would be great. I will work through your word doc. Very helpful.

    Many thanks
    Thorsten
  • By the way, for AM65xx the PDK build notes shows guide lines to build via command line. But not to create project for CCS right?
  • Thorsten,

    That is correct. Currently majority of the components are designed to build using command line make file. There are a couple of examples that you can use if you want to checkout of the CCS build setup. We provide an example RTOS template project in the top level processor SDK RTOS folder A53 developers:
    software-dl.ti.com/.../index_examples_demos.html

    That can simply be imported into CCS after eclipse content of components from the SDK are discovered.

    The other example is the USB driver projects for R5F and A53. We provide a script called pdkProjectCreate to generate the projects in your environment. you can check my guidance on creating them here:
    e2e.ti.com/.../762996 (Step 2)


    Instructions to generate example projects for R5F and A53 for the USB driver.
    setupenv.bat
    cd ..\pdk_am65xx_1_0_3\packages
    pdkProjectCreate.bat am65xx am65xx_evm little usb all mcu (Create project for R5F)
    pdkProjectCreate.bat am65xx am65xx_evm little usb all mpu (Create project for A53)

    Regards,
    Rahul
  • Many thanks for the great hints. Let me study and try those.