• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 828 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.

DRA712: Necessary modules to include on Android zImage

Raul Matos
Expert 5125 points
Part Number: DRA712


Team, please answer my customer's question below regarding TI's Android BSP available for J6 Entry EVM.

We are working on kernel customization for our board. We have experience in a such job, but we are trying to understand your kernel config system (./ti_config_fragments/defconfig_builder.sh) .

Example file ti_sdk_dra7x_android_release_defconfig, shows that several SOCs (CONFIG_SOC_IMXxx=y) MACHine, and modules are being selected, but these are not required or used in EVM.

We are required to include used modules only, to avoid a larger zImage and to improve boot time.

  • Could you share any documentation about your configuration system or explain why SOC like iMX is required.
  • Future AOSP release (Android O), will be based on kernel 4.4 or newer. In a such a case, config and build system tool will be the same?
  • 0
    TI__Mastermind 42515 points
    Hi Raul,

    I have forwarded your question to Android expert for comment.

    Regards,
    Yordan
  • 0
    TI__Mastermind 33420 points
    Hi Raul,

    I don't see those configs enabled in final ".config" that gets generated after building the defconfig.
    Let me get back to you on why those configs are enabled in intermediate step.

    Android Automotive O SDK from TI will be based on Kernel 4.4

    Regards,
    Vishal
  • 0 in reply to Vishal Mahaveer
    TI__Mastermind 33420 points
    The reason it is showing up in defconfig is because we include "arch/arm/configs/multi_v7_defconfig" in our scripts.
    The SOC configs you mentioned gets disabled in final .config.
  • 0 in reply to Vishal Mahaveer
    Expert 1285 points
    We understand that defconfig_builder.sh, use ti_sdk_dra7x_android_release_defconfig, with several cfg files.
    SDK_Release_Defconfigs type:
    defconfig: multi_v7_defconfig
    config_file:
    None extra_configs:
    multi_v7_prune.cfg
    baseport.cfg ipc.cfg
    connectivity.cfg
    audio_display.cfg
    wlan.cfg omap_soc.cfg
    lpae.cfg
    dra7_only.cfg
    systemd.cfg
    ../android/configs/android-base.cfg
    ../android/configs/android-recommended.cfg
    auto.cfg
    android_omap.cfg

    But we don't see where unnecesary configs are being prunned.
    We want to create our board config file from scratch, based on EVM, using TI tools, if it is possible, or menuconfig (several configs are not showed) .
    Could you share any documentation about your configuration tool, for DRA7x. We need to understand which file select/unselect each module to avoid unnecesary zImage size.

    Thanks
  • 0 in reply to Christian N
    TI__Mastermind 33420 points
    Hi Christian,

    You can use the finally generated ".config" to create your board defconfig, instead of using the ti_sdk_dra7x_android_release_defconfig.

    Regards,
    Vishal