I also looked at help and found this -- did not work

#The -full-io switch links the application with a third-party, proprietary I/O library. The  third-party I/O library provides a complete implementation of the ANSI C  Standard I/O functionality at the cost of performance (compared to the Analog  Devices I/O library). For details, see "stdio.h".

#Invoke this switch using two options: the  Full I/O check box located in the VisualDSP++ Project Options dialog box (Compile : Processor (1) page) and the Full  ANSI C Compliance option button located in the I/O Libraries area of the VisualDSP++ Project Options dialog box (Link : Processor page).

Hi Craig

I am still using the HPPC-ICE links to my boards -- any chance that it is an (updated) driver issue?

Now the weekend's over , going to try it in my University lab to see if I can duplicate the effect.

Just tried it with the simulator -- no window pop-up so I think that says not a specific HPPCI driver issue

You noticed how many extra blank lines this site is adding for every blank line you type in?  Has somethiong changed?

I have a total of 4 'single blank lines inserted between sentences. Seeing 1 blank line, 3 blanlks lines, 2 blank lines and then 4 blank lines on the displayed page. Must be all those frustrated stdio pop-up windows trying to break through my screen   Just noticed that the ? has an extra blank line after it that I did not put in.  Would almost suggest that it is a linux  windows PC   "carriage return"  (0xD)  "line feed" (0xA) confusion  issue

Mike

I just checked under automatic

The  unhandled exception error breakpoint is enabled -- and I can ensure you that works well

The __primIO is enabled already

So I cleared it -- rebuit the example and ran it
now I am getting no I/O what so ever -- meaning print statements are NOT occurring

So I now set the __primIO breakpoint -- rebuilt the example and ran it

Print statements now occuring (O) but the gets is not (I)

Hi Craig

     I tried the other suggestions and initially thought they worked.

     The problem reappears with the JTAG frequency selection operation

    After the fixes -- I/O window popped up at 10 MHz JTAG frequency -- first time I tried the simple program
    Switched to 33 MHz JTAG connection -- At 33 Mhz -- pop-up window does NOTappear

    After a fight with the system I got the JTAG  back to 25 MHz -- pop-up window does not work

              -- Suggestion there -- tools should add a pop-up window that says 'recycle board and VDSP' as the selection arrow never moves until you power down VDSP

    Then got it back to 10 MHz -- pop-up window still does not work

    Tried building a new session  with the JTAG set at 10 MHz before building the session -- also recycled board and VDSP -- pop-up window does not work at 10 MHz.      

                 Question -- the arrow in the selection window says 10 MHz -- but is the system really at 10 MHz JTAG?

Mike

With the latest sort of tests with the very simple gets and print -- no

.vbs has been used -- also pop-up window worked until I changed JTAG

settings

Manually via the settings menu

However, I have loaded a script automatically when I start the system-- see cut-andpaste from the console window.

Loading C:\Program Files\Analog Devices\VisualDSP 5.0\System\EmbeddedUnit\VDSPTools.vbs
    Loading: "E:\Documents and Settings\smith\My Documents\My Webs\ENCM511_09\09Labs\DontPublish09_ENCM511LabValidation\CraigExample\Debug\CraigExample.dxe"...
    Load complete.

JTAG

That should not be running as it sets up some tools -- also it is counter indicated as the stdio window worked initially at 10 MHz

However I have gone back and reset the VDSP properties, causing JTAG to default to  10 MHz -- now the stdio window does not come back up

I could not find where I am automatically loading this file through the VDSP settings, so I went and changed its name so it could not be used.  I restared VDSP and saw the message

Error: Unable to open the file: C:\Program Files\Analog Devices\VisualDSP 5.0\System\EmbeddedUnit\VDSPTools.vbs

so the script is no longer loaded (and therefore can't be running in the background -- Unfortunately stdio window did not reappear

Message was edited by: Mike Smith