Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed the week of November 23.

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.

C2000WARE: Recommended architecture for rehosting a C2000 bitfield-based application on Linux

Part Number: C2000WARE

Hello,

I am developing a Linux-based Software-in-the-Loop (SIL) / rehost environment for an existing C2000 application.

The application uses the C2000Ware bitfield register model (SciaRegs, GpioCtrlRegs, EPwm1Regs, etc.) rather than DriverLib.

My goal is not to emulate the C2000 CPU or peripherals. I only want to execute the application logic on Linux while communicating with an external Python-based test framework through shared memory.

The main objective is to minimize modifications to the production application so that the same application logic can be tested on both the target hardware and the host environment.

Before implementing the complete solution, I would like to understand whether TI recommends a particular architecture for this kind of project.

  • Is there an officially recommended approach for running a C2000 application on Linux or Windows for Software-in-the-Loop (SIL) or host execution?
  • Has TI published any application notes, reference implementations, or example projects demonstrating host execution or software rehosting?
  • Since my project already uses the C2000Ware bitfield register model, would TI recommend keeping this model, or would migrating to DriverLib significantly simplify host execution?
  • If you were implementing a maintainable Linux-based SIL environment for a C2000 application today, what architecture would you recommend?
  • Hi John,

    I'm checking with the c2000 team and I'll get back to you soon.

    Thanks,

    Ira

  • Hi John,

    Thanks for your patience. 

    1.We don't have any such toolkit to run C2000 code on Linux. MATLAB/Simulink and Embedded Coder model based workflow can be used to generate Software-in-the-Loop (SIL) code.
    2. There are currently no App notes on this topic.
    3. Migrating to driverlib is inherently easier to mock a functional API call like than to mock a hardware register read operation . However changing to DriverLib will requires rewriting the entire device peripheral interface layer.

    Thanks,

    Ira