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.

OMAPL138B-EP: Is SYSLINK supported on ARM9

Part Number: OMAPL138B-EP
Other Parts Discussed in Thread: SYSBIOS, OMAPL138, TCI6638K2K, TCI6630K2L

From the SYSLINK release note, on L138, ARM run Linux, DSP run SYSBIOS, does it mean SYSLINK  is not supported on ARM or just not verified?

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/syslink/2_21_01_05/exports/syslink_2_21_01_05/syslink_2_21_01_05_ReleaseNotes.html

  • Hi,

    I think this is the case for syslink. However this software is quite outdated. If you want to develop RTOS applications I'd suggest you transition to Processor SDK RTOS, which has examples running on both ARM & DSP cores.

    Best Regards,
    Yordan

  • Yordan,

    Thanks, Seems IPC also only support SYSBIOS on L138.ARM9. Is it easy for customer to migrate IPC to ARM9 by themselves, is there a guide?

    C:\ti\ipc_3_47_02_00\examples\OMAPL138_linux_elf

     

    in the release notes: C:/ti/ipc_3_47_02_00/ipc_3_47_02_00_release_notes.html

    Validation

    This release was built and validated against using the following software components. Please use the versions below, or compatible:

    • XDCtools 3.50.03.33.core
    • SYS/BIOS 6.52.00.12
    • Pre-built binaries were built with the following toolchains:
      • gnu.targets.arm.A15F - 6.3.1
      • ti.targets.arm.elf.M4 - 16.9.2
      • ti.targets.arp32.elf.ARP32 - 1.0.0
      • ti.targets.elf.C66 - 8.1.3
    • In addition, binaries for LINUX & QNX were built with following toolchains for validation:
    • Linux GCC toolchain (ARMV7) - Linaro 4.7-2013.03-20130313
    • Linux GCC toolchain (ARMV5) - Linaro 6.2.1-ti2017.01-armv5-x86_64
    • QNX 7.0.0, 6.6.0 with additional patches applied depending on the version of the QNX BSP. Refer to the BSP documentation for more details.

    This release was validated using the following hardware platforms (though others are supported):

    • TCI6638K2K (Keystone II) - Linux on HOST, SYS/BIOS on HOST, C66 DSPs
    • TCI6630K2L (Keystone II) - Linux on HOST, SYS/BIOS on HOST, C66 DSPs
    • 66AK2E (Keystone II) - Linux on HOST, SYS/BIOS on HOST, C66 DSPs
    • 66AK2G (Keystone II) - Linux on HOST, SYS/BIOS on HOST, C66 DSPs
    • OMAPL138 - Linux on HOST, SYS/BIOS on C66 DSPs
    • DRA7XX (Vayu)
      • SYS/BIOS on HOST, DSP(s), EVE(s), SMP-BIOS on IPU(s)
      • SYS/BIOS on HOST, DSP(s), EVE(s), IPU1-0, IPU1-1, SMP-BIOS on IPU2
      • QNX on HOST, SYS/BIOS on DSP1, SMP-BIOS on IPU(s)
      • Linux on HOST, SYS/BIOS on DSP1 and DSP2, SMP-BIOS on IPU1 and IPU2
      • Android on HOST, SYS/BIOS on DSP1 and DSP2, SMP-BIOS on IPU1 and IPU2
  • Hi Tony,

    Here is the available document that I know of:
      

    Best Regards,
    Yordan

  •        

    Hi Yordan,

            From  the "SysLink Product Releases",   SysLink 2.x is intended for SYS/BIOS 6 users and does not support WinCE. DSP/BIOS 5 users (including most DVSDK users) should continue to use DSP Link releases!

           From the "IPC 3.x" ,  IPC 3.x merges the IPC 1.x and SysLink 2.x products, creating a single product that defines multiprocessor communication APIs and provides implementations for several OS's, including SYS/BIOS and HLOS's.

           

          Above two points,   do they  mean IPC 3.x  is not supported on DSP/BIOS?

        Thank you!

    https://e2e.ti.com/support/processors/f/791/p/825697/3055716#3055716

  • Hi,

    Yes, as far as I know IPC3.x is used on SYS/BIOS which is the supported rtos kernel on the latest Processor SDK RTOS releases. The earliest versions of IPC3.x might have backward compatibility with DSP/BIOS (the older rtos kernel version), but this is very outdated software and is currently not supported (or has limited support).

    Best Regards,
    Yordan