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.

Usage of ti_config_fragments

Hi Experts,

I am facing difficulties in the configuration of Linux kernel 3.14 for the AM335x.

How to use the ti_config_fragments in configuring the Kernel ? Any user guide will be better.

  • Hi,

    See if the following guide helps: processors.wiki.ti.com/.../AM335x_PSP_User%27s_Guide

    Also can you provide some more details? Could you specify what do you mean by ti_config_fragments (?) is it some options in the tisdk_am335x-evm_defconfig file or how to use the defconfig file itself?

    Best Regards,
    Yordan
  • Hi Yordan,

    I have downloaded the Linux 3.14 kernel and I would like to test it for AM335x EVMSK.

    Now I tried compiling the kernel using make zImage command. But there is no .config file available.

    I found a folder named ti_config_fragments containing list of configuration files.

    Also i don't find a default configuration file name am335x_default_config in the arch/arm/configs/ folder.

    Now I want to compile the 3.14 kernel for the AM335x EVM configuration.
  • Hi,

    In arch/arm/configs folder you should look for a file called tisdk_am335x-evm_defconfig. If there is no such file, the omap2plus_defconfig also work for Sitara devices.

    So you should run

    $ make tisdk_am335x-evm_defconfig


    OR

    $ make omap2plus_defconfig


    Before using the make zImage command.

    Where did you downloaded the kernel from? So I can have a look at it and provide feedback.

    Best Regards,
    Yordan

  • Hi,
    The config fragments are a new way to add/modify/override the default config options in a defconfig file such as omap2plus_defconfig.

    Each config fragment contains some config options clubbed together as per feature/category/module with a value set against it.


    ex: ti_config_fragments/connectivity.cfg has required configs for connectivity related drivers/peripherals.


    This eliminates the need to have a different/duplicate defconfig file per usecase. The ti_config_fragments are specific to TI requirements/usecases.

    You need to merge the fragments with the base defconfig using following script, with the fragments as input.


    ./scripts/kconfig/merge_config.sh -m arch/arm/configs/omap2plus_defconfig ti_config_fragments/ipc.cfg ti_config_fragments/power.cfg ti_config_fragments/audio_display.cfg ti_config_fragments/system_test.cfg ti_config_fragments/baseport.cfg ti_config_fragments/wlan.cfg

    ti_config_fragments/connectivity.cfg ti_config_fragments/auto.cfg


    you'll see something like below

    #
    # merged configuration written to ./.config (needs make)


    make olddefconfig ARCH=arm

    ## configuration written to .config

    #
    After this a new .config file will be created with all the config options set to the requested value or default value from Kconfig


    Now you build zImage/dtb/modules as you do always.


    make -j4 zImage; make am335x-evm.dtb;make modules

     

    Regards,

    RK

  • The kernel is downloaded from the link

    git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git, tag ti2014.10.01.
  • Hi,

    RK gave very detailed explanation of the ti_config_fragments in his post above. Please refer to that reply.

    Best Regards,
    Yordan