• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 3 answers
  • Subscribers 98 subscribers
  • Views 330 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.

PROCESSOR-SDK-OMAPL138: Basic build issues

Risto Hedman
Expert 1770 points
Part Number: PROCESSOR-SDK-OMAPL138

Hi,

Some novice questions.

We're upgrading from mcsdk_1_01_00_02 to ti-processor-sdk-linux-omapl138-lcdk-06.00.00.07. and have been studying  docs/06_00_00_07/linux/Overview.html and related. We've downloaded and installed ...install.bin for RTOS and Linux. We've successfully built Linux and uBoot for LCDK  with defaults - OK. I would like to ask few basic questions to verify if we're on right path, HW is custom and has major differences to LCDK:

  • top level Makefile makes with 'tisdk_omapl138-lcdk_defconfig' and skips .config which we' ve just reconfigured - which is the right way to customize configuration
  • Which is recommended RFS, 'arago-base-tisdk-image-omapl138-lcdk'  or??
    • How can we forward 'install' there?
  • We need wpa_supplicant and gstreamer with related drivers, are they included in some of those filesystems or should we build and install them 'manually'?

We would like to minimize our effort to this upgrade as our resources are involved in application. Are there parties which could do this configuration with USD?

Best regards,

ristoH

  • 0
    TI__Guru**** 161600 points

    Hi Risto,

    top level Makefile makes with 'tisdk_omapl138-lcdk_defconfig' and skips .config which we' ve just reconfigured - which is the right way to customize configuration

    For the latest Processor SDK Linux the correct way to customize the defconfig is by using make menuconfig. For this you should not use the toplevel makefile. You need to export all needed environment variables:
     export ARCH=arm

     export CROSS_COMPILE=/home/users/ykovachev/ti-processor-sdk-linux-omapl138-lcdk-<version>/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/arm-linux-gnueabi-

     make tisdk_omapl138-lcdk_defconfig

     make menuconfig => here you include all the needed drivers (built-in the kernel image or built as modules)

     make (to build kernel images).

    Or you can open the toplevel make file and see what commands are used under make linux and execute them one by one (adding the make menuconfig in between make defconfig and make zImage).

    Which is recommended RFS, 'arago-base-tisdk-image-omapl138-lcdk'  or??
    • How can we forward 'install' there?

    All filesystems: arago-base-tisdk-image-omapl138-lcdk, tisdk-server-extra-rootfs-image-omapl138-lcdk and tisdk-server-rootfs-image-omapl138-lcdk can be used. The tisdk-server-extra-rootfs-image-omapl138-lcdk is the most complete and has all packages provided in the yocto release in it, while the arago-base-tisdk-image-omapl138-lcdk is the lightest version using only the basic packages needed for ycoto fs to run.

    We need wpa_supplicant and gstreamer with related drivers, are they included in some of those filesystems or should we build and install them 'manually'?

    Gstreamer is included in the Processor SDK Linux, wpa_supplicant is not (you need to port it on your board). You can check what is available in processor SDK Linux by inspecting docs/software_manifest.htm.

    Best Regards,
    Yordan

  • 0 in reply to Yordan Kovachev
    TI__Guru**** 161600 points

    As for third parties, you can find a list of such companies here:
     

    Check the Software Design Houses column.

    Best Regards,
    Yordan

  • 0 in reply to Yordan Kovachev
    Expert 1770 points

    Hi Yordan,

    Thank you for your reply - it helped me a lot to understand - 'how to'. I followed your instructions but failed with final 'make' in ~/ti/ti-processor-sdk-linux-omapl138-lcdk-06.00.00.07/board-support/linux-4.19.38+gitAUTOINC+4dae378bbe-g4dae378bbe$

    scripts/kconfig/conf --syncconfig Kconfig
    CALL scripts/checksyscalls.sh
    HOSTCC scripts/extract-cert
    scripts/extract-cert.c:21:10: fatal error: openssl/bio.h: No such file or directory
    #include <openssl/bio.h>
    ^~~~~~~~~~~~~~~
    compilation terminated.
    scripts/Makefile.host:90: recipe for target 'scripts/extract-cert' failed

    Best Regards,

    ristoH

  • 0 in reply to Risto Hedman
    Expert 1770 points

    Hi,

    With google we managed to get forward:

    apt-get install libssl-dev

    solved this problem.

    BR, ristoH