• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 99 subscribers
  • Views 1005 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.

AM5728: Problem compiling SGX DDK

Michel Catudal2
Intellectual 620 points
Part Number: AM5728


Problem compiling ti-sgx-ddk-km-1.17.4948957 on SDK 6

My system runs on ArchLinux so in order to create the SDK I use AGL Docker server which has debian stretch

Everything is fine creating the SDK except for mariadb-5.5.64.tar.gz which is missing. I downloaded it from their website and yocto was able to finish

The problem I have is not with yocto but with TI's SDK, looking at the regenerated SDK, it looks identical.

For my Beagleboard X15 and Beablebone-AI I needed to recompile the kernel and associated files. TI broke the sdk at rev 4x as I recall. Once I fix it, the whole thing works fine.

In order to get a working Beagleboard X15 I just need to change the device tree. For my beaglebone AI boards I do need to be able to create the kernel and associates modules with the SDK.

Until there is a working SDK I plan to make a custom yocto tree. I don't feel to move to AGL for this, they took too much stuff off.

When using the SDK to do so only u-boot and the kernel compile

For the 2D and 3D GPU, no luck.

In the Makefile we have this for ti-sgx-ddk-km

For compilation

       cd `find . -maxdepth 1 -name "ti-sgx-ddk-km*" -type d`; \
        make -C ./eurasia_km/eurasiacon/build/linux2/omap_linux ARCH=arm TARGET_PRODUCT=jacinto6evm KERNELDIR=$(LINUXKERNEL_INSTALL_DIR)

For Installation

        cd ./eurasia_km/eurasiacon/binary2_omap_linux_release/target/kbuild; \
        make -C $(LINUXKERNEL_INSTALL_DIR) SUBDIRS=`pwd` INSTALL_MOD_PATH=$(DESTDIR) PREFIX=$(SDK_PATH_TARGET) INSTALL_MOD_STRIP=$(INSTALL_MOD_STRIP) modules_install

Generated code is on binary_omap_linux_xorg_release

In yocto build it is different and it is on binary_omap_linux_nulldrmws_release

I had similar results trying to compile that package on Funtoo with my ebuild script.

I will look into the yocto recipe to see the changes. Obviously your scripts for the SDK do not reflect the changes made

Also, when generating the kernel with the SDK it boots fine except that the video stalls at the prompt.

I never had such issue with kernel 4.9 and 4.4

Michel

  • 0
    TI__Guru 55345 points

    Hello Michel,

    Can you check whether you have all these Processor SDK 6 required packages installed on your host machine? Please also note that the Processor SDK is tested on Ubuntu distribution, if you use CentOS or AGL Docker server with Debian stretch it is possible some side effects to be seen.

    Best regards,
    Kemal

  • 0 in reply to Kemal R. Shakir
    Intellectual 620 points

    The problem is the Makefile in the SDK. It doesn't reflect the changes made in the yocto recipes.

    Michel

  • 0 in reply to Michel Catudal2
    TI__Guru 55345 points

    The Makefile in OE build system is shaped and adjusted by these recipes. You can check them out.

    <tisdk>/sources/meta-arago/meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile_1.0.bb
    <tisdk>/sources/meta-processor-sdk/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile_1.0.bbappend

  • 0 in reply to Kemal R. Shakir
    Intellectual 620 points

    From the first bb file

    ti-sgx-ddk-km_install:
            @echo ================================
            @echo      Installing ti-sgx-ddk-km
            @echo ================================
            @cd board-support/extra-drivers; \
            cd `find . -maxdepth 1 -name "ti-sgx-ddk-km*" -type d`; \
            cd ./eurasia_km/eurasiacon/binary2_omap_linux_release/target/kbuild; \
            make -C $(LINUXKERNEL_INSTALL_DIR) SUBDIRS=`pwd` INSTALL_MOD_PATH=$(DESTDIR) PREFIX=$(SDK_PATH_TARGET) INSTALL_MOD_STRIP=$(INSTALL_MOD_STRIP) modules_install

    From the generated file which matches the bb file from TI

    ti-sgx-ddk-km_install:
            @echo ================================
            @echo      Installing ti-sgx-ddk-km
            @echo ================================
            @cd board-support/extra-drivers; \
            cd `find . -maxdepth 1 -name "ti-sgx-ddk-km*" -type d`; \
            cd ./eurasia_km/eurasiacon/binary2_omap_linux_release/target/kbuild; \
            make -C $(LINUXKERNEL_INSTALL_DIR) SUBDIRS=`pwd` INSTALL_MOD_PATH=$(DESTDIR) PREFIX=$(SDK_PATH_TARGET) INSTALL_MOD_STRIP=$(INSTALL_MOD_STRIP) modules_install

    In order to get the Makefile to actually install the code I had to modify it to this :

    ti-sgx-ddk-km_install:
            @echo ================================
            @echo      Installing ti-sgx-ddk-km
            @echo ================================
            @cd board-support/new-drivers; \
            cd omap5-sgx-ddk-linux ; \
            cd ./eurasia_km/eurasiacon/binary_omap_linux_nulldrmws_release/target_armhf/kbuild; \
            make -C $(LINUXKERNEL_INSTALL_DIR) SUBDIRS=`pwd` INSTALL_MOD_PATH=$(DESTDIR) PREFIX=$(SDK_PATH_TARGET) INSTALL_MOD_STRIP=$(INSTALL_MOD_STRIP) modules_install

    This matches what is done in the bb file code in ./meta-ti/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb

    do_install() {
        make -C ${STAGING_KERNEL_DIR} SUBDIRS=${B}/eurasia_km/eurasiacon/binary_omap_linux_nulldrmws_release/target_armhf/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install
    }

    Michel

  • 0 in reply to Michel Catudal2
    TI__Mastermind 45015 points

    Hello Michel,

    Thank you for reporting the bug and it will be addressed in our next release.

    Regards,
    Krunal