Re: Ada file IO & vxworks

[Steve O'Neill <steven.m.oneill@lmco.com>]

Make sure that your board can FTP into the NT host.  The file is buffered
in memory on the target board until the Close is invoked.  At this time
vxWorks transfers the complete file to the NT host via FTP.  It can appear
that this is working fine when, in fact, the transfer will fail.  I've been
burned by this in the recent past.

On the flip side, when you open an existing file VxWorks transfers the
entire contents of the file from the host into local target memory.

Steve O'Neill

Corey Ashford wrote:

> Doug Lewis wrote in message <35CF08D2.BA545027@ti.com>...
> >I'm having problems using the text_io file operations on a PPC board
> >running vxworks 5.3.1, the host is a NT pc.  I'm able to successfully
> >create and write to a file but the task doesn't perform the close
> >operation and I can find no existance of the file on the pc host.  Can
> >anyone provide some ideas about file operations that they successfully
> >implemented in an Ada/vxworks environment?
> >
>
> Which Ada compiler are you using?
>
> Since you aren't closing the file, it's possible that VxWorks and/or
> the Ada text_io implementation are buffering up the writes.  You
> might trying adding a call to Ada.Text_Io.Flush(<file>) after any
> writes that you want to be seen on the host.  However, that will only
> flush the Ada side, not the VxWorks side.  You may have to close
> the file periodically and reopen it with the mode set to Append_File.
>
> - Corey