Lpc2000

--- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@...> wrote:
> For a system with multiple applications I'd definitely consider SWI.
 If I 
> used SWI theres a good chance I'd run the app in user mode as it's a 
> natural fit.

Although I do not know what you mean by "application" I do not
disagree with the above.

> For a standard single application system though there is no 
> advantage(1).

What you mean by "single application system" is important.

I prefer to look the "application" running on an embedded system as a
set of independent and cooperating tasks, where a task in an entity
that has a own state (stack), and which it returns to when it is
suspended (for any reason) and then resumed.

If by "single application system" you mean the system comprises of
only one task, then any monolithic system approach would do, and there
is little value in separating the things that the task does into
different baskets.

I did not think that any of the things that participants here are
doing with the LPC falls in the latter category.  This is why I
started with the SWI approach to my simple example atomic feed of
watchdog timer.

It does not matter to me what term is used to describe what happens on
the two sides of the SWI fence.  It could well be public vs private,
system vs user, kernel vs user, or infrastructure vs application.

Jaya