TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Subject:
From:
Ken Garlington <[log in to unmask]>
Date:
Thu, 14 Nov 1996 12:49:48 +0000
Organization:
Lockheed Martin Tactical Aircraft Systems
Reply-To:
Ken Garlington <[log in to unmask]>
Parts/Attachments:
text/plain (20 lines)
Philip Johnson wrote:
>
> This is what I was trying to point out.  Rather than produce an Ada
> subset for embedded controller systems why not just add the packages
> to support the architecture.  I have some embedded systems that have
> a limited control domain (raise/lower, open/close) that is very small
> and runs in 256 bytes of memory located on the processor.  I mostly
> have embedded control systems that has a real-time executive in EEROM
> that provides the OS functions with limited multitasking (8-16 tasks).
> The RT OS calls can be implemented in the system package, etc.

You can do 8-16 tasks with 256 bytes (not Kbytes, but bytes) of RAM,
and still leave the user space for a stack and a heap? How big are your
TCBs? How much space do you allocate for each entry? Could you post the
source for the system packages you used to implement this?

--
LMTAS - "Our Brand Means Quality"
For more info, see http://www.lmtas.com or http://www.lmco.com

ATOM RSS1 RSS2