X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C72563.FF3143F6@onstor-exch02.onstor.net>; Thu, 21 Dec 2006 16:56:21 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: Followup discussion with Wind River
Date: Thu, 21 Dec 2006 16:56:21 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E01D4CD08@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Followup discussion with Wind River
thread-index: AcclY/78WvLKeEMHQ6mnSerGWvhedw==
From: "Jay Michlin" <jay.michlin@onstor.com>
To: "dl-Cougar" <dl-Cougar@onstor.com>

Andy, Larry and I met again with Wind River today, as planned. The
discussion was limited because of the approaching holiday, but the
exchange was still a good one.

Our interest has always been in the possibility of exploiting Wind
River's sensor/probe/workbench software tools for development and
maintenance of Cougar. Notably they could help us find and fix obscure
memory leaks, among other things, both during initial development and
later when the product is in the field. Andy has previous experience
with these tools and reports that they are both powerful and applicable
to our situation.

We concluded that this could be done in fairly straightforward fashion
if we were to run VxWorks on our embedded cores with our own real time
OS (such as it is) as a task. This would readily give us access to all
the Wind River tools. We could do this strictly for debug environments,
while the shipped product would have our OS without VxWorks.

We agreed to think more about this, and I said I will contact Wind River
with an update the first week in January.

jay


