Article Details

ID: 2002
Case Type: faq
Category: Device Programming
Related To: ispVM System
Family: All Devices

Search Answer Database

Search Text Image

Why does the I/O vector editor in the Device Information window "Expand Option" not generate the I/O vector file (*.iov file), when I click \u201CApply\u201D instead of \u201CSave As"?

This is applicable to only "Custom" and "Dynamic" modes of the I/O State option in the Expanded window of Device Information GUI. 


By clicking \u201CApply\u201D, the changes in the I/O states are made, but these changes are stored in the .XCF file. These changes are reflected when the device configures. The disadvantage in this option is that you need to change the IO settings again in a different configuration setup, as that would require a different *.XCF file. Changing IO settings for a custom environment can be time consuming for device with high pin count. 


However, saving an I/O vector file (by clicking \u201CSave As\u201D) helps you to re-use the same I/O states for a particular device, but with different setup or a different .XCF file. That prevents you from changing IO settings every time you change configuartion set-up(resulting in a change in *.XCF file).