• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 105 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.

Original question:

Availability of SYS/BIOS and TI-RTOS on the AM335x Family

AM6442: Evaluating RTOS Options

Jagadish Gangaiah
Prodigy 30 points

Part Number: AM6442

We are evaluating RTOS options for the AM64x/AM243x R5F cores. Within our organization, FreeRTOS is not a preferred/recommended RTOS, and we are considering SEGGER embOS as an alternative.

Could you please clarify:

  1. Has TI or any customer successfully deployed embOS on the AM64x/AM243x R5F cores?
  2. Does TI provide any BSP, reference port, application note, or support guidance for integrating embOS with the MCU+ SDK?
  3. MCU+ SDK appears to be tightly integrated with FreeRTOS through the Driver Porting Layer (DPL). If embOS is used instead, what effort would be required to port the SDK while retaining existing functionality:
    • TI driver framework
    • IPC/RPMessage
    • Industrial communication stacks (EtherCAT, PROFINET, EtherNet/IP where applicable)
    • Networking stacks
    • Timers, semaphores, mutexes, interrupts, and task management
    • SysConfig-generated projects
  4. Is there a documented list of DPL APIs that would need to be reimplemented on top of embOS?
  5. Are there any known limitations or features currently available with FreeRTOS that would not be achievable or supported with embOS?
  6. Based on TI's experience, would this be considered a straightforward RTOS replacement at the DPL layer, or should significant SDK modifications be expected?

We are trying to estimate the engineering effort and technical risks associated with migrating from the MCU+ SDK FreeRTOS environment to embOS on R5F.

  • 0
    TI__Mastermind 24715 points

    Hi,

    Apologies for the delay. Please allow me some time to review this, please expect an update in 1-2 days.

    Best Regards,
    Meet.

  • 0 in reply to Meet Thakar
    TI__Mastermind 24715 points

    Hi,

    Jagadish Gangaiah said:
    Does TI provide any BSP, reference port, application note, or support guidance for integrating embOS with the MCU+ SDK?

    MCU+SDK doesn't support embOS port, it only supports FreeRTOS, it is expected that a user takes our FreeRTOS port as a reference and will port it themselves.

    Jagadish Gangaiah said:
    • MCU+ SDK appears to be tightly integrated with FreeRTOS through the Driver Porting Layer (DPL). If embOS is used instead, what effort would be required to port the SDK while retaining existing functionality:
      • TI driver framework
      • IPC/RPMessage
      • Industrial communication stacks (EtherCAT, PROFINET, EtherNet/IP where applicable)
      • Networking stacks
      • Timers, semaphores, mutexes, interrupts, and task management
      • SysConfig-generated projects
    • Is there a documented list of DPL APIs that would need to be reimplemented on top of embOS?

    DPL abstracts the OS, you can use the DPL layer from MCU+SDK as it is for your implementation: https://software-dl.ti.com/mcu-plus-sdk/esd/AM64X/12_00_00_27/exports/docs/api_guide_am64x/KERNEL_DPL_PAGE.html

    You can refer to the DPL implementation that is provided for FreeRTOS in the MCU+SDK, that you will give you an idea on what all DPL APIs and files need to be implemented for your embOS port: https://github.com/TexasInstruments/mcupsdk-core/tree/next/source/kernel/freertos/dpl 

    Jagadish Gangaiah said:
    Are there any known limitations or features currently available with FreeRTOS that would not be achievable or supported with embOS?

    I request you to reach out to SEGGER on this and also to get an estimation on the effort required to get embOS working on R5, you can check if they already have a embOS port available for R5F.

    Best Regards,
    Meet.