• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 200 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.

AM625: About build image

hao teng
Intellectual 450 points

Part Number: AM625

hi

I referred to SDK 11.009 and used the command make ARCH=arm64 CROSS_COMPILE=aarch64-none-linux-gnu- defconfig ti_arm64_prune.config ti_rt.configto build the kernel from my SDK 8.6. The resulting build still contains many modules.
Is there a more minimal defconfig in the newer SDK — similar to a 'tiny Linux' config — that has no modules and keeps only the essential AM62 A53 and M-core settings? I'd like to port it to SDK 8.6 and gradually add modules back. (My current SDK cannot be upgraded.
 
thanks
  • 0
    TI__Expert 7040 points

    Hi Hao,

    TI doesn't publish a "tiny_defconfig" for K3/AM62 the way upstream Linux has make tinyconfig.

    The only officially maintained trimming fragments are ti_arm64_prune.config (drops non-AM62/non-target K3 SoC bits) and ti_early_display.config/ti_rt.config (boot-time and RT tweaks).

    None of them aim for "zero modules, A53+M4 only." ti_arm64_prune.config already trims a lot, but it's nowhere close to a minimal config; it still leaves most driver subsystems (USB, sound, various SoC IP not on your board, etc.) enabled as modules.

    Regards,
    Vinu

  • 0 in reply to Vinuchandran A V
    Intellectual 450 points

    Hi Vinu

    "I am currently trimming down the kernel for the AM625. As I go deeper into menuconfig, the options become very granular — disabled modules are small and scattered across many menus, making it hard to prune systematically.
    My original plan was to start from a minimal 'tiny Linux' defconfig and incrementally add only what I need. Since any real product using the AM6x family will eventually run Linux on custom hardware, the K3 SoC defconfigs and base configs are mainly for validation — I believe TI understands the AM62's multi-core heterogeneous architecture far better than a new user ever could, so a well-crafted minimal defconfig from TI would be very valuable.
    In my case, my hardware does not need GPU support at all. After disabling DRM in the kernel config, pvrsrvkm.ko(PowerVR driver) is still generated​ — I found it is built as an out-of-tree module from the SDK itself, not from the kernel tree.
    Would it be possible for TI to provide a user-friendly minimal/tiny defconfig (no modules, core AM62 A53 + M-core only) in future SDK releases, similar to what exists in newer SDK versions, to make this workflow easier?"
    thanks
  • 0 in reply to hao teng
    TI__Expert 7040 points

    Hi Hao,

    For SDK 8.x, this probably isn't feasible - since it is a very old version, which is not actively maintained, so a new minimal defconfig target is unlikely to be added there.

    For the latest SDK, I'll ask the dev team about the feasibility of considering this as part of any of the future releases.

    Regards,
    Vinu

  • 0 in reply to Vinuchandran A V
    Intellectual 450 points
    Vinuchandran A V said:
    For SDK 8.x, this probably isn't feasible - since it is a very old version, which is not actively maintained, so a new minimal defconfig target is unlikely to be added there.
    "When I started using the AM62, SDK 9 had not yet been released. Additionally, the cross compiler was changed starting from SDK 9, which adds risk to any upgrade.
    It would be very helpful if newer SDK versions provided a minimal/'tiny' defconfig for the AM62 that boots a bare-minimum system — I could then reference it and port the relevant config to my SDK 8.6 environment."
    thanks
  • 0 in reply to hao teng
    TI__Expert 7040 points

    Hi Hao,

    I've created a requirement ticket. 

    https://jira.itg.ti.com/browse/SITREQ-6943

    The ticket is yet not published externally. This is only for internal tracking.

    I'll share the external link, once it's available.

    Regards,
    Vinu

  • 0 in reply to hao teng
    TI__Guru**** 182156 points

    Hi Hao,

    hao teng said:
    Would it be possible for TI to provide a user-friendly minimal/tiny defconfig (no modules, core AM62 A53 + M-core only) in future SDK releases, similar to what exists in newer SDK versions, to make this workflow easier?"

    As you have already observed that trimming kernel config is not trivial, expanding a barebone/tiny kernel config to enable a certain application is not trivial either. Therefor, it doesn't make sense to provide a "tiny" kernel config in the SDK.

    If you really want a "tiny" kernel config, please check kernel make targets of allnoconfig and/or tinyconfig.

    kernel doc:

    Documentation/admin-guide/README.rst