From: claveman@cod.nosc.mil (Charles H. Sampson)
Subject: Green Hills Ada, VxWorks, and MVME2700
Date: 1999/12/17
Date: 1999-12-17T01:04:31+00:00 [thread overview]
Message-ID: <83c26v$l81$1@newpoisson.nosc.mil> (raw)
Our project uses the configuration in the subject line of this
post, along with a variety of military boards on the VME bus. Our code
is currently running when we download from a Solaris, our host environ-
ment. However, when we put the code into flash memory, in order to cre-
ate a standalone system, it begins executing and then dies very quickly.
We've already got some modifications to the documented procedures
for putting code into flash memory. For example, we know that the net-
work code is included automatically when we download but it has to be
explicitly included for flash memory.
Does anyone have any experience with this environment, enough to
give us some hints as to what's going wrong? Both Green Hills and Wind-
River are looking at the problem and they are stumped. Green Hills does
claim that it's a WindRiver problem.
One other piece of information. We use the VxWorks logging task to
output messages, to prevent them from being interleaved when coming from
multiple tasks. Those messages are not coming out. (We've verified
that the task is running.) We have duplicated them with Text_IO output,
and we do see those messages.
Charlie
--
******
For an email response, my user name is "sampson" and my host
is "spawar.navy.mil".
next reply other threads:[~1999-12-17 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-17 0:00 Charles H. Sampson [this message]
1999-12-21 0:00 ` Green Hills Ada, VxWorks, and MVME2700 Ted Dennison
1999-12-21 0:00 ` Robert Dewar
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox