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.

AM1808 SDK 05.03.02 kernel build error

Other Parts Discussed in Thread: OMAPL138, AM1808

Hello,

i am trying to build the kernel from last  AM180x SDK PSP Source Code (am180x-evm-sdk-src-05.03.02.00.tar.gz). I am doing:

make ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi- menuconfig

make ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi- uImage

I got the next error:

drivers/mfd/twl-core.c:41:24: fatal error: plat/board.h: No such file or directory
compilation terminated.
make[2]: *** [drivers/mfd/twl-core.o] Error 1
make[1]: *** [drivers/mfd] Error 2
make: *** [drivers] Error 2
Pls could you help me to fix this error?

Many thanks in advance

  • alberto liberal said:

    make ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi- menuconfig

    make ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi- uImage

    I think you need to perform the following commnad before the above 2 commands.  This is documented in the Software Developers Guide in the building section.

    make ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi- da850_omapl138_defconfig

  • Thanks,

    it is working now

    Best Regards

  • Hi

    A new Kernel configuration file is present in AM1808 SDK 5.03.02: tisdk_am180x-evm_defconfig (which is the same of .config in Kernel main folder).

    Which do I have to use for AM1808: tisdk_am180x-evm_defconfig or da850_omapl138_defconfig?

    Sitara Linux SDG has not been yet updated to support SDK 5.03.02...

    Regards, Max

  • The tisdk_am180x-evm_defconfig file is the one that corresponds to how the kernel for the SDK was built and should be the one used.  The SDG section has the following NOTE, but I will make this more clear/obvious going forward:

    NOTE: The configuration file used to build the pre-built binaries found in the SDK can be found in the arch/arm/configs directory as tisdk_<device>_config and can be used in place of the config file given below to reproduce the SDK Linux kernel configuration settings. The differences between these files generally revolve around enabing/disabling additional modules for expected SDK use cases.