Hi Lee,

 

Yes, that’s the expectation from Zephyr project.

Initially, I posted the same set of questions in https://zephyrproject.org/contact-us/. They recommended to post these questions in dev & user mailing list.

 

Regards,

Karthik

 

From: Lee Courtney <leec2124@...>
Sent: Monday, May 16, 2022 11:07 PM
To: Karthik Thangavel <kthangav@...>
Cc: devel@...; P Hanumath Prasad <phanumat@...>; Veera Venkata Satish Kumar Kothamasu <vkothama@...>
Subject: Re: [Zephyr-devel] RTOS Feasibility Study

 

Karthik,

 

Is your expectation with this post that someone with the Zephyr Open Source Project will research your questions, complete your RFP, and return to you? I may be wrong, but that's not the way typical Open Source project work. 

 

If I am wrong I would love to see the results, especially for the automotive space as that is the area I am looking at Zephyr for.

 

Lee Courtney

 

On Mon, May 16, 2022 at 10:12 AM Karthik Thangavel <kthangav@...> wrote:

Hi Zephyr Dev Team,

 

We are evaluating different RTOS for our upcoming project.

Can you share us below details for Zephyr RTOS,

 

HW Spec:-

ARM Cortex R52 (32-bit)

Number of Cores ==> 2/4

 

RTOS Requirement:-

 

Below are the different RTOS requirements,

 

License:

Looking for no-royalty, Open Source free redistribution license.

 

SMP:

RTOS should be able to see all Cortex R52(Same Architecture). CPU’s will share the common memory space. Single instance of RTOS that runs on all the CPUs, dividing work between them.

 

Memory Footprint:

RTOS memory footprint should be < 100KB. What is the memory footprint of Zephyr RTOS.

 

Scheduling Algorithm & Policy:

Scheduler determines which thread to run on each CPU in the system at any given time. What is the scheduling algorithm used in Zephyr RTOS.

 

CPU Affinity:

Affine particular task to specific CPU core. Group a list of process & assign it to particular CPU core. Zephyr supports this ?

 

Interrupt Affinity:

Affine particular interrupt to specific CPU core. Always IRQ-x will be routed to specific CPU core to service the interrupt. Zephyr supports this ?

 

Interrupt Handling:

Process the interrupt even the CPU executing the user process. May be disables the scheduler to avoid interrupt handler preemption. Provision to initialize interrupt vector with the proper interrupt handler. Triggers the specific handler associated with the IRQ.

 

Thread Safety feature:

Safe for use from multiple threads; operation is protected by an RTOS primitive and can be used from multiple threads.

 

Safety Certified:

Automotive functional safety certified ISO 26262.

 

Context Switching:

Save the current task state (with the intention for it to be restored at a later point in time) and switching it with another task/process already saved task state.

 

RTOS Components Configurable:

Suppose File System is not required, in that case to reduce the memory print of OS. There should be a configuration to enable to disable such modules.

 

Toolchain:

Compatible with ARM Cortex R52

 

Any existing automotive customers using Zephyr RTOS ?

 

Even if you don’t have RTOS readily supports all the above features, share the RTOS details which comes closure to our requirement & whether it can be extended to fulfill the requirements.

 

Regards,

Karthik

 

--

Lee Courtney

+1-650-704-3934 cell

Hi Zephyr Dev Team,

 

We are evaluating different RTOS for our upcoming project.

Can you share us below details for Zephyr RTOS,

 

HW Spec:-

ARM Cortex R52 (32-bit)

Number of Cores ==> 2/4

 

RTOS Requirement:-

 

Below are the different RTOS requirements,

 

License:

Looking for no-royalty, Open Source free redistribution license.

 

SMP:

RTOS should be able to see all Cortex R52(Same Architecture). CPU’s will share the common memory space. Single instance of RTOS that runs on all the CPUs, dividing work between them.

 

Memory Footprint:

RTOS memory footprint should be < 100KB. What is the memory footprint of Zephyr RTOS.

 

Scheduling Algorithm & Policy:

Scheduler determines which thread to run on each CPU in the system at any given time. What is the scheduling algorithm used in Zephyr RTOS.

 

CPU Affinity:

Affine particular task to specific CPU core. Group a list of process & assign it to particular CPU core. Zephyr supports this ?

 

Interrupt Affinity:

Affine particular interrupt to specific CPU core. Always IRQ-x will be routed to specific CPU core to service the interrupt. Zephyr supports this ?

 

Interrupt Handling:

Process the interrupt even the CPU executing the user process. May be disables the scheduler to avoid interrupt handler preemption. Provision to initialize interrupt vector with the proper interrupt handler. Triggers the specific handler associated with the IRQ.

 

Thread Safety feature:

Safe for use from multiple threads; operation is protected by an RTOS primitive and can be used from multiple threads.

 

Safety Certified:

Automotive functional safety certified ISO 26262.

 

Context Switching:

Save the current task state (with the intention for it to be restored at a later point in time) and switching it with another task/process already saved task state.

 

RTOS Components Configurable:

Suppose File System is not required, in that case to reduce the memory print of OS. There should be a configuration to enable to disable such modules.

 

Toolchain:

Compatible with ARM Cortex R52

 

Any existing automotive customers using Zephyr RTOS ?

 

Even if you don’t have RTOS readily supports all the above features, share the RTOS details which comes closure to our requirement & whether it can be extended to fulfill the requirements.

 

Regards,

Karthik