This article is a summary of my study. If there are copyright or knowledge errors or problems, please contact me directly. Please leave a message
PS: Based on the principle of knowledge sharing, this blog can be reproduced, but please indicate the source!
1. Problem description
The vivado error problem warning is as follows:
[DRC NSTD-1] Unspecified I/O Standard: 1 out of 9 logical ports use I/O standard (IOSTANDARD) value 'DEFAULT', instead of a user assigned specific value.
This may cause I/O contention or incompatibility with the board power or connectivity affecting performance, signal integrity or in extreme cases cause damage to the device or the components to which it is connected. To correct this violation, specify all I/O standards. This design will fail to generate a bitstream unless all logical ports have a user specified I/O standard value defined. To allow bitstream creation with unspecified I/O standard values (not recommended), use this command: set_property SEVERITY {Warning} [get_drc_checks NSTD-1]. NOTE: When using the Vivado Runs infrastructure (e.g. launch_runs Tcl command), add this command to a .tcl file and add that file as a pre-hook for write_bitstream step for the implementation run. Problem ports: SYS_CLK.
The IO setting interface is as follows:
The IO working voltage is not clearly defined, so the following operations are required;
2. Solution:
Create a new. TCL file and write the following contents:
set_property SEVERITY {Warning} [get_drc_checks NSTD-1]
set_property SEVERITY {Warning} [get_drc_checks UCIO-1]
set_property SEVERITY {Warning} [get_drc_checks RTSTAT-1]
Add in vivado setting:
The error warning disappears after recompilation!
Read More:
- After vivado joined ILA, the [DRC lutlp-1] problem of error problem was solved
- Duplicate class com.xxx.xxx Find in modules problem solving (Aidl interdependence problem)
- [unable to calculate item metadata “% (fullpath)” unable to apply item metadata “% (fullpath)” to path] problem solving
- Online problem solving analysis
- VTK compilation problem solving
- Win10 system [createfile() error: 5] problem solving
- Solving windows error: [error 87] classification: problem summary
- Problem solving of runas 740 error
- The underlying provider failed on open problem solving
- Error: can’t access JTAG chain problem solving method
- Spring boot problem solving record (1)
- write error in swap file problem solving
- About solving the problem that vscode files cannot be edited
- Solving the problem of can’t create temporary directory of CVS under Windows
- Configuring OpenGL in Chinese version of VS2010 and problem solving
- Solve CONDA’s “solving environment: failed” problem
- npm ERR! Error: CERT_ Untrusted problem solving
- “Cannot access GitHub because this site uses HSTs.” Problem solving
- OpenGL + vs2015 environment configuration problem solving
- Call to undefined function oci_ Connect() problem solving