From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,HK_NAME_MR_MRS autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,9bbec8931498da16 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-12-21 07:35:53 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!logbridge.uoregon.edu!arclight.uoregon.edu!wn4feed!worldnet.att.net!204.127.198.204!attbi_feed4!attbi.com!rwcrnsc51.ops.asp.att.net.POSTED!not-for-mail From: Mr. Caffiene Newsgroups: comp.lang.ada Subject: Re: Help! (Ada/Integrity/PEG) Message-ID: <20011221103954.4cd90f91.nospam@attbi.com> References: <1008948364.19337.0.nnrp-10.c2de4527@news.demon.co.uk> Organization: Caffienated Corps. X-Newsreader: Sylpheed version 0.6.5 (GTK+ 1.2.10; i586-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit NNTP-Posting-Host: LeIU7-23472-b_-5226@rwcrnsc51.ops.asp.att.net X-Complaints-To: abuse@attbi.com X-Trace: rwcrnsc51.ops.asp.att.net 1008948952 LeIU7-23472-b_-5226@rwcrnsc51.ops.asp.att.net (Fri, 21 Dec 2001 15:35:52 GMT) NNTP-Posting-Date: Fri, 21 Dec 2001 15:35:52 GMT Date: Fri, 21 Dec 2001 15:35:52 GMT Xref: archiver1.google.com comp.lang.ada:18204 Date: 2001-12-21T15:35:52+00:00 List-Id: On Fri, 21 Dec 2001 15:31:10 -0000 "TAMS Team" wrote: > We're just about to start our project using Integrity/AdaMulti to code the > main part of the application, with PEG as our GUI designer. The target > hardware will be a Radstone PPC4 board. The (Ada) application will decode > serial data coming from a remote processor to generate the screen layouts > and softkeys (and changes to their properties, e.g. text contents), and > encode serial data to send back to the remote processor which will > essentially only contain information about softkey presses and status flags > from the screen hardware. All the PEG task is required to do is to display > the appropriate windows or softkeys. > > Our first hurdle to overcome is how to get the main application task talking > to the GUI task. We're not quite sure how to get started, but I think we've > convinced ourselves we may have to use some form of messaging. However, > we're not certain of the form of messaging - i.e. typically how do you send > a message to the RTOS message queue, what form is it, and how does PEG pull > it from the queue? > > Any advice (or even sample code!) greatly received! > > (Please assume we're complete novices with absolutely no experience using > this combination of products, and you'll be pretty close to the truth!) > > Is the main application task coded in Ada or another language. If written in another language, you would want to use the the standard Ada "Interfaces" libraries to communicate with the task.(Assuming I understand what your saying.) Also, rather than using messaging, you could use a storage pool controlled by a "semaphore" of sorts, which might be much more efficient. A stack of some sort would probably be the fastest method, but also the most troublesome to work with.(Unless you happen to be using Forth. Heh.) A little more detail(if at all possible) on what your doing would enable us(or at least me) to provide a little more pertinent advice.(I use to do C coding on RTEMS, another RTOS. Thank G-d I discovered Ada. Heh.)