Forums

Nucleus RTOS on non-MMU based processor

Started by rhaudiogeek November 13, 2006
Folks, 

Does anyone have any expirence porting Nucleus on a non-MMU based
processor ? 
What are some of the issues and/or challenges in doing this.

Appreciate some inputs as we are investigating supporting Nucleus RTOS for
our products

Thnaks



On Nov 13, 8:40 am, "rhaudiogeek" <rohanhu...@yahoo.com> wrote:
> Folks, > > Does anyone have any expirence porting Nucleus on a non-MMU based > processor ? > What are some of the issues and/or challenges in doing this. > > Appreciate some inputs as we are investigating supporting Nucleus RTOS for > our products > > Thnaks
Nucleus has a memory mapped extensions, but the non-mmu is probably the more common case. Linux would be the other way, much less common without an MMU. The challenges with non-MMU Nucleus is the same as any non-MMU environment, the entire app is running unprotected. If you can get your code to work properly, Nucleus will do its part. Nucleus is stable and mature. It is not the only choice for RTOS. Regards, Steve
stevecalfee@hotmail.com wrote:
> Nucleus is stable and mature. It is not the only choice for RTOS.
Nucleus Plus (the core RTOS) is stable and mature and works as advertised. I would however avoid the extra add-ons if you can. Some of them do not fit into the stable or mature category.
Darin Johnson wrote:
> stevecalfee@hotmail.com wrote: > > Nucleus is stable and mature. It is not the only choice for RTOS. > > Nucleus Plus (the core RTOS) is stable and mature and works as > advertised. I would however avoid the extra add-ons if you can. > Some of them do not fit into the stable or mature category.
You are right. But would this not apply to all software, old stuff is better and more stable than new stuff? Regards, Steve
stevecalfee@hotmail.com wrote:
> You are right. But would this not apply to all software, old stuff is > better and more stable than new stuff?
It's a matter of degree. There is "not as good as the old stuff", and "not as good as the old stuff when it was still new". (Imagine if you will a hypothetical situation where you have to describe to the developer of a device driver you purchased what deadlocks are and why the particular code at line x causes a deadlock and why it should be fixed even if he can't reproduce the hang on his setup.) -- Darin Johnson