• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 276 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.

SOFTWARE HIERARCHEY

Abdul Jarif
Prodigy 100 points
Other Parts Discussed in Thread: OMAPL138, OMAP-L138, SYSBIOS

Hello,

for real time image processing with omapl138 development kit what should be the OS?

1>lilnux SDK

2>BIOS

3>CCS

thanks

  • 0
    TI__Guru 64420 points

    Remove CCS from the list.  This is a host side Integrated Development Environment (IDE) tool for managing your target (OMAP-L138) software project, compiling, etc.

    I suspect you would utilize BIOS on the DSP side of the OMAP-L138 and perhaps Linux on the ARM side of the OMAP-L138.  There should be information on the OMAP-L138 Product folder regarding software development kits to get you started.

  • 0 in reply to BrandonAzbell
    Prodigy 100 points

    thanks for the reply..

    i have gone through a wiki page of OPMAL138 EVM  which states below option for software development.

    1>use RTOS i.e.SYS/BIOS dsp->arm procesors.

    2>use generic OS...

    3>or NO OS...

    MY target application is real time image processing..so what to use SYS/BIOS on DSP side and linux on ARM side. with CCS as IDE?

    please suggest....

    BR,

    Abdul

  • 0 in reply to Abdul Jarif
    TI__Mastermind 20790 points

    Abdul Jarif,

    The OMAP-L138 C6-Integra DSP+ARM processor which offer a variety of peripherals for networking,
    secure boot and multi-level encryption, and run Linux or the DSP/BIOS real-time kernel for operating system flexibility.

    Brandon have given more details and asked to look OMAPL138 product folder.
    So that you can understand and get more details, as mentioned the below link 
    http://www.ti.com/product/omap-l138

    Kindly give the working environment details like which TI processor and board are using, whenever create the new thread.  

    If you are using TI OMAP-L138 Development Kit (LCDK), refer the below link
    http://www.ti.com/tool/tmdxlcdk138
    If you are using OMAP-L138 Experimenter Kit, refer the below link
    http://www.ti.com/tool/tmdsexpl138
    Under the OMAPL138 kit link, you can see the "software" section, which is provided by TI.
    1. You can run SYSBIOS on DSP and DSPLink (DSP and ARM) package provides communicate between DSP and ARM.(Refer SYSBIOS User Guide)
    2. CCS used for build the project on DSP side
    3. Linux used for build the source and packages on ARM side.
    4. And also you can get the Linux version of CCS.

  • 0
    Guru 26430 points

    The amount of SW for the OMAP development is a bit daunting. Here's an incomplete list of SW I've had to deal with:

    1) Linux Platform Support Packages (LSP)
    Linux is usually always on the ARM. TI offers official releases in the form of LSPs. The LSPs are usually behind the the GIT at the Arago website. Unsure if the Linux mainline has L138 support. Linux is Rarely on the DSP. The C6 project puts Linux on the MMUless DSP but I believe that project is discontinued. Linux is usually required if your product needs to talk to the outside world in any way, eg. SD Card, Ethernet, USB, Hard Drives, etc. BIOS support of device is somewhat poor.

    2) U-Boot
    Bootloader for Linux. Should be in the LSPs? DVSDK? SDK?

    3) DSP/BIOS and SYS/BIOS or just BIOS
    An operating system for the DSP and ARM. Comes in in two major versions BIOS5 (aka DSP/BIOS) and BIOS6 (aka SYS/BIOS). The DSPBIOS version appears to be abandoned. No updates in several years.

    4) DSP Link and SysLink
    Inter-processor communication layer. Allows the ARM to load the DSP with a program, send between the ARM and DSP, etc. Usually DSPLINK is used with SYSBIOS and SYSLINK is used with SYSBIOS. Built on a Linux host. Requires the gcc cross compiler for the ARM side and the C600o CGT compiler for the DSP side.

    5) DSP/BIOS and SYS/BIOS Platform Support Packages (BIOSPSP)
    Device driver code. Not needed if the DSP just processes data. Different versions for DSPBIOS and SYSBIOS. The DSPBIOS version appears to be abandoned. No updates in several years.

    6) EDMA3 Low-level Driver
    Likely required by BIOSPSP driver code and DSPLINK/SYSLINK.

    7) Digital Video Sotware Development Kits (DVSDK)
    These kits combine most of the above. Easiest to start here first before updating or adding individual components.

    8) Software Development Kits (SDKs)
    Same concept as DVSDK. Different name and different content. Try starting here as well.

    9) ARM Cross Compiler Toolchain
    Compiler usuallys used for U-Boot and Linux. Some typical distros of the gcc include MontaVista, CodeSourcery and Arago. You need a Linux host to cross compile the Linux kernel.

    10) CCS
    Compiler/IDE usually used for DSP code. Not usually used for Linux code on the ARM. It can be used for ARM BIOS or Bare-Metal code.

    11) C6000 CGT (Code Generation Tools)
    C6000 cross compiler. On a PC host, it is part of CCS. On a Linux host, it is part on the SDKs? Not sure about that.

    12) DSP/BIOS BIOSUSB
    A USB stack that runs under DSP/BIOS. It is a stripped down Jungo stack. No version is available for SYS/BIOS.

    All depends on how much device driver support and communications protocol support you need. Linux is very rich in abilities but it requires a lot of tools.