OMAPL138 SW & HW Comparison
- 1 Overview
- 2 Available Software
- 3 Software Comparison Chart
- 4 Hardware Development Platform Comparison Chart
- 5 FAQ
- 5.1 General
- 5.2 Hardware
- 5.2.1 Q: Why isn't the EVM supported anymore?
- 5.2.2 Q: Where do I find HW documents (schematics, BOM, etc.) for the EVM and Experimenter kit now that they are no longer available?
- 5.2.3 Q: I am starting an OMAP-L138 design. Where can I find hardware design guides and example schematics showing how OMAP-L138 was used?
- 5.3 Software
- 5.3.1 Q: I am currently using OMAPL138 Starterware in my project, should I upgrade to MCSDK?
- 5.3.2 Q: I have a product in production already using the Linux PSP, DSPlink and SYS/BIOS. I have a product update coming, should I upgrade to MCSDK?
- 5.3.3 Q: I am using the C6748 DSP, should I use the MCSDK?
- 5.3.4 Q: Where can I find video codec for OMAPL138?
- 5.3.5 Q: What does it mean when you say ‘Starterware is available AS IS’
- 5.3.6 Q: What should I do if I have bugs in OMAPL138 Starterware?
- 5.3.7 Q: Will OpenCV be supported with the MCSDK 1.1?
- 5.3.8 Q: I'm currently using C6EZFlo (embedded in CCS) to generate preliminary SysBIOS-based DSP code for my project. What is TI’s plan for maintaining this feature in future CCS versions?
- 5.3.9 Q: When will other SysBIOS drivers be available in MCSDK?
- 5.3.10 Q. Is there any software provided for leopard imaging sensor on LCDK?
- 5.3.11 Q: Can I obtain the optimized DSP libraries by themselves?
Welcome! We're happy that you have chosen or are considering the OMAPL138 SOC for your design. If you are beginning a new design, it's recommended that you visit the OMAPL138 product folder to obtain the latest device and software information for the platform. If you are an existing customer, this page will help you understand what options are available to you for software and hardware development. The goal of this page is to provide you with enough information to make an informed decision about how to proceed with your development. For all customers, we recommend that you check out the newly released Multicore Software Development Kit (MCSDK) for the OMAPL138. It's the software package that will be supported moving forward and will provide a robust development path for your software design well into the future.
|Development Phase||SW Recommendation||HW Recommendation|
|New Design / Evaluation (i.e. Starting development)||Multicore Software Development Kit (MCSDK)||OMAPL138 LCDK (TMDXLCDK138)|
|Development in progress (i.e. Product is in development with legacy software)||Evaluate options with information on this page.||Evaluate options with information on this page. Note that the OMAPL138 EVM and Experimenter kit are only available while supplies last.|
|Design in production / Maintenance (i.e. Product is already completed, in production, or near completion with legacy software)||Continue with legacy software. Evaluate options for future development with information on this page.||OMAPL138 LCDK (TMDXLCDK138)|
The Multicore Software Development Kit (MCSDK) is the latest software release on the OMAPL138 platform. It is the software package that will be supported by TI moving forward. Customers will still have access to legacy software on the OMAPL138 platform, but this software is made available AS IS. Legacy SW has no planned updates, no bugs fixes and no direct TI support moving forward. If a customer chooses this path, support will come solely from e2e forums.
- DaVinci (ARM9) PSP Releases
- DSP/BIOS Platform Support Package for OMAP-L138/C6748
- WindowsCE(WinCE) Software Development Kit for OMAP-L138
- QuickStartOMAPL1x rCSL
Software Comparison Chart
|SW CATEGORIES||CURRENT||LEGACY SDKs|
|Device Supported||OMAPL138||OMAPL138||OMAPL138||C6748||OMAPL138 / C6748|
|H/W platform||LCDK||EVM||LCDK||LCDK||LCDK / EVM|
|HLOS||Linux v3.3||Linux v2.6.37||Linux v3.1||N/A||N/A|
|IPC Stack||SysLink||DSPLink||SysLink||IPC SDK||IPClite|
|Optimized DSP Algorithm Libraries||DSPLIB, IMGLIB, MATHLIB||None||None||DSPLIB, IMGLIB, MATHLIB||None|
|DSP Protocol Stack||None||None||None||NDK||Various|
|DSP Driver Component||PDK (Not available as separate download) - See Below||BSL (Not available as separate download)||None||(Old) BIOS PSP||See table below.|
DSP Driver Comparison Chart
(Part of MCSDK)
|StarterWare|| BIOS PSP
(Add-on package on top
| Old BIOS PSP
(Included in BIOS_C6SDK)
|Device Supported||OMAPL138||OMAPL138 / C6748||C6748||C6748||C6748|
|Parallel Port (uPP)|
|EMAC||x + lwIP|
|EMIF - NAND||x|
|Power and Sleep controller (PSC)||x||x|
|Power Management ( DVFS)|
Hardware Development Platform Comparison Chart
|Hardware||Logic PD OMAP-L138/C6748 EVM + UI card||OMAP-L138/C6748 LCDK|
|Processor|| C6748 VLIW DSP and
ARM926 RISC GPP
| C6748 VLIW DSP and
ARM926 RISC GPP
|DDR||128 MB mDDR SDRAM||128 MB DDR2|
|Flash|| 8 MB SPI NOR Flash
(8MB NOR, 8bit 512MB NAND on UI card)
|128 MB NAND Flash|
|USB|| One USB 2.0 high-speed OTG &
One USB 1.1 full-speed host
| One USB 2.0 high-speed OTG &
One USB 1.1 full-speed host
|Network||10/100 Mbps Ethernet with RJ45 Ethernet jack||10/100 Mbps Ethernet with RJ45 Ethernet jack|
|Audio|| TLV320AIC3106 codec with
line in and line out only
|TLV320AIC3106 with 1 LINE IN & 1 LINE OUT & 1 MIC IN)|
|Display|| Integrated (touch and backlight LCD)
& Character display(on UI card)
|Video||Svideo in and composite ( on UI card)|| Composite Video
|Signals brought out from connector*||Signals brought out from connector|
|SD/MMC||MMC/SD slot||MicroSD slot|
|Power supply||PMIC –control through I2C||Fixed Voltage Regulator|
|Boot modes|| NOR EMIFA, NAND-8 EMIFA, SPI0 FLASH,
SPI1 FLASH,UART0, UART1, SD/MMC, Emulator
|UART2, NAND-16 BIT, Emulator|
|Debug|| 14 pin JTAG interface &
XDS100 emulation circuit
|14 pin JTAG interface|
|Security||Secure SOM available||No Secure LCDK|
Q: I’m a new customer, what do I start with?
- A: New customers to the OMAPL138 should consider starting software development with the OMAPL138 MCSDK. The recommended hardware development platform is the OMAPL138 LCDK. The SW Comparison Chart above provides detail on what software components are available on MCSDK versus the legacy software packages. While MCSDK is the software package that will be supported moving forward, customers are able to leverage components from legacy software releases to fill any gaps that may exist in the SW support required versus SW provided in MCSDK.
Q: Why are we making the change to MCSDK?
- A: With the goal of making software development easier for customers, TI is consolidating many of our DSP platforms around the Multicore Software Development Kits (MCSDK). The MCSDK provides optimized bundles of foundational, platform specific drivers to enable development. This software is available for many TI platforms, and more details can be found here.
Q: Why isn't the EVM supported anymore?
- A: In an effort to consolidate support around a single cost-effective platform that allow customers to quickly evaluate the OMAPL138 device, TI has chosen to normalize support around a single platform, the OMAPL138 LCDK. The EVM and Experimenter kit will be available to customers while supplies last, but the newest MCSDK software release will only support the OMAPL138 LCDK.
Q: Where do I find HW documents (schematics, BOM, etc.) for the EVM and Experimenter kit now that they are no longer available?
- A: You can access all HW documents for the EVM and Experimenter kit on the Logic PD web site. You will need to register your board to access these documents.
Q: I am starting an OMAP-L138 design. Where can I find hardware design guides and example schematics showing how OMAP-L138 was used?
- A: The development platform recommended for customers starting designs with the OMAPL138 is the OMAPL138 LCDK. On the tool folder for this page, you'll have access to schematic and design files for this development platform. If you are looking for a pre-engineered OMAPL138 module, you may consider contacting Critical Link or Logic PD. Both have existing system on module (SOM) boards that they sell for the OMAPL138 platform.
Q: I am currently using OMAPL138 Starterware in my project, should I upgrade to MCSDK?
- A: If you are satisifed with the software you have, there is no need to change. The previous versions of software are still available, though there is no development planned.
- A: The information on this site is provided to help you decide whether to use the MCSDK or to continue using the software that you have. This decision should be based on the variables that are most important to your development, such as timeframe and features needed. The previous versions of software are still available, however, no further software updates are planned.
Q: I am using the C6748 DSP, should I use the MCSDK?
- A: The MCSDK contains a DSP software component, which could be used on the C6748. However, testing on the C6748 DSP only device was not carried out. Note that the Starterware and DSP PSP packages are still available for download, as is the C6x BIOS SDK. To determine the SW package that will be most beneficial for you, please use the SW Comparison Chart and DSP Driver details provided in the charts above.
Q: Where can I find video codec for OMAPL138?
- A: Please see here
Q: What does it mean when you say ‘Starterware is available AS IS’
- A: The software is provided as-is, and is still available for download. However, no further software updates are planned.
Q: What should I do if I have bugs in OMAPL138 Starterware?
- A: The source code for Starterware is provided in the package. You may also consider checking with the community at E2E Forum.
Q: Will OpenCV be supported with the MCSDK 1.1?
- A: OpenCV is not included with the MCSDK 1.1 for OMAPL138. This software was originally put into the face detect demo described [here]
Q: I'm currently using C6EZFlo (embedded in CCS) to generate preliminary SysBIOS-based DSP code for my project. What is TI’s plan for maintaining this feature in future CCS versions?
- A: Please see the main wiki article at: C6EZFlo
Q: When will other SysBIOS drivers be available in MCSDK?
- A: New features are continuously being evaluated for inclusion into the product. Please make a request into the E2E Forum.
Q. Is there any software provided for leopard imaging sensor on LCDK?
- No, we don`t provide any software drivers for the leopard imaging camera sensor that can be used with the 36 pin zip connector
Q: Can I obtain the optimized DSP libraries by themselves?
- A: Yes, please search TI.com. For example, DSPlib can be downloaded directly.