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.

Defconfig file not found in 8.2.0.24

Hi,

I observed that earlier SDK(4.2.0.09) with kernel version 4.9.59 there is defconfig with respect to am335x in the directory structure (sources/meta-ti/recipes-kernel/linux/linux-am335x/defconfig)

Now we have moved to latest SDK(8.2.0.24) with kernel version 5.10.100 in this we are not able to observe the defconfig in (sources/meta-ti/recipes-kernel/linux/linux-am335x/defconfig) for am335x..

May i know which path defconfig is there to get affect to linux kernel(5010.100) in latest SDK(8.2.0.24)?

  • Hi, I'm currently in the middle of some project work and won't be able to look into this right away, so please allow a few days for a response. Thanks.

  • yes please. i tried to copy .config (4.9.59) to .config (5.10.100) and did bitbake -c virtual/kernel menuconfig.. it is overwriting the copied .config(4.9.59) how to over come this? 

    One more observations,

    if we replace .config(4.9.59) with the .config(5.10.100) with the path where .config is residing(SEM_3T/build/arago-tmp-external-arm-glibc/work-shared/am335x-evm/kernel-build-artifacts$)
       observation if we build on top of that "bitbake virtual/kernel" it is overwriting .config(4.9.59) to .config(5.10.100)
       Although i used the same .config(4.9.59) into "arch/arm/configs/tisdk_am335x-evm_defconfig"(by renaming) and if we recompile build once again its overwriting tisdk_am335x-evm_defconfig

    Basically i am tried to port the kernel from 4.9.59(with our custom changes) to 5.10.100 

    please help when u find the time. 

    Thanks,

  • Hi Manu,

    yes please. i tried to copy .config (4.9.59) to .config (5.10.100) and did bitbake -c virtual/kernel menuconfig.. it is overwriting the copied .config(4.9.59) how to over come this? 

    If you want to migrate your Kernel config within Yocto I'd recommend dropping into 'bitbake -c devshell' for full control over the migration process and the generation of a new buildable defconfig rather than using 'bitbake -c menuconfig. Please check below some steps I used before for the am62xx-evm platform, they should apply to am335x-evm as well. But before the step of running 'make menuconfig' (note we don't need to explicitly supply cross-compile arguments while inside the devshell!) copy in your old .config file, and run 'make oldconfig'. Also check here for more background: https://stackoverflow.com/questions/4178526/what-does-make-oldconfig-do-exactly-in-the-linux-kernel-makefile

    # Clean TI Kernel build target
    MACHINE=am62xx-evm bitbake -c clean linux-ti-staging
    
    # Perform the bitbake 'configure' step on the TI Kernel build target to establish a baseline
    # Kernel configuration that can then be used for further customization. Note that this triggers
    # the default defconfig_builder.sh (a TI tool) based process to generate a Kernel config.
    MACHINE=am62xx-evm bitbake -c configure linux-ti-staging
    
    # Now enter the bitbake devshell so we can explore and work on the TI Kernel
    MACHINE=am62xx-evm bitbake -c devshell linux-ti-staging
    
    # Open the Kernel menuconfig tool. There, look for the CONFIG_LOCALVERSION setting and populate
    # it with a custom test string of "defconfig-test". Then, exit the tool.
    make menuconfig
    
    # Verify the changes to the Kernel config that were made
    diff $KBUILD_OUTPUT/.config.old $KBUILD_OUTPUT/.config
    24c24
    < CONFIG_LOCALVERSION=""
    ---
    > CONFIG_LOCALVERSION="defconfig-test"
    
    # Create a new 'defconfig' file based off the current Kernel config
    make savedefconfig
    
    # Verify that a new 'defconfig' file was created in the Kernel build output directory
    ll $KBUILD_OUTPUT
    
    # Copy newly created 'defconfig' into the TI Kernel recipe folder that is part of the meta-ti layer,
    # overwriting the existing 'defconfig' file which is nornally used to trigger defconfig_builder.sh mechanism.
    cp $KBUILD_OUTPUT/defconfig ~/tisdk/am62xx-evm/sources/meta-ti/recipes-kernel/linux/linux-ti-staging-5.10/k3
    
    # Close the bitbake devshell
    exit
    
    # Clean TI Kernel build target once more so we can witness the build environment to be
    # setup on our new custom defconfig part of the TI Kernel recipe in the next step
    MACHINE=am62xx-evm bitbake -c clean linux-ti-staging
    
    # Build the TI Kernel from scratch
    MACHINE=am62xx-evm bitbake linux-ti-staging

    Regards, Andreas

  • Thanks for the reply..

    Further to enable the drivers ..  I am not able to see the drivers in menuconfig which i have ported in drivers/net/ethernet/micrel may i know how to check i have updated Kconfig also in drivers/net/ethernet/micrel but still not able to see in menuconfig.. as a result .o or .ko objects not able to generate after compilations

  • Hi Manu,

    what I'd recommend is you clone your Kernel tree to a new folder somewhere on your machine, update it the way you need to by making source changes/additions (which checking those into Git), and then trying "local" Kernel builds using the entire sequence of 'make defconfig' and 'make menuconfig' and 'make all' to ensure you can successfully configure and build your Kernel (do your network drivers now show up in Kconfig?). THEN as a next step migrate those changes into Yocto.

    If you still can't see the Kconfig updates/additions in Yocto you probably need to clear out everything using a command like below to remove all output files, shared state cache, and downloaded source files for a target:

    $ MACHINE=am62xx-evm bitbake -c cleanall linux-ti-staging

    Regards, Andreas

  • Hi Andreas i have posted 1 more query regarding dts file here is the link https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1195490/dts-file-phy_sel-not-found-in-8-2-0-24

    can you please look at it or please forward to concerned team.. so that it will help!!! 

    Thanks

  • Hi Manu,

    that question was assigned to another engineer but I went ahead and added an answer there anyways. Please continue the relevant discussion on that thread as needed to keep things on topic.

    Regards, Andreas

  • Hi Andreas in regards to reply your answer on the dts file phy_sel not found in 8.2.0.24 - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums 

    i replied for the query can you please check and give reply on that( thats regarding ping issue)

    Also 1 fundemnetal question: may i know who will be assigning ip for the controller?

    awating your reply.. for that post

  • Hi Manu,

    this thread is assigned to a network domain expert, and I was just trying to pitch in initially to get you over the initial DTS-related hump. I've talked to the respective engineer and he has since replied to your post. Please continue the discussion on that thread.

    Regards, Andreas