Too many positional options when parsing xxx

Vivado 2022.2

[Common 17-165] Too many positional options when parsing ‘Interface.srcs/utils_1/imports/synth_1/SPI_Master.dcp’, please type ‘read_checkpoint -help’ for usage info.

省流：检查一下工程文件和工程目录是否有空格

这一个错误在百度上搜，能搜到的内容很少
一开始搜到到的解决办法
解决方法：打开Sources->Utility Sources->utils，找到.dcp文件，remove后再编译。

来自 https://blog.youkuaiyun.com/qq_45899513/article/details/124528765

但是治标不治本，下次综合仍然会有这样的错误

于是去寻找有关dcp文件、和“checkpoint”的信息，在此过程中发现
从 Vivado 2019.1 开始，Vivado 综合引擎支持增量流。这使用户能够在设计更改较小时减少整体综合运行时间。
可以使用 Vivado IDE 启用此流程，也可以使用 Tcl 命令进行批处理模式。有关流程的更多详细信息，请参阅 (UG901)。

来自 https://support.xilinx.com/s/article/976545?language=en_US

于是在设置“setting”里找到与增量综合的设置，并试了一下

发现当关闭增量综合功能，并删掉dcp文件之后进行综合就不会再生成dcp文件了

但是如果需要用到这个功能呢?
于是尝试在bing上搜索了一下，发现有说是文件目录存在空格的原因，也可能是电脑的用户名存在空格，跟我的情况符合

Core inserter error – ERROR: [Common 17-165] Too many positional options when parsing
Applies to Exostiv for Xilinx netlist insertion / automatic insertion mode.
When setting up the Exostiv IP with the core inserter, the following error can be encountered when browsing the design for the nodes and clocks:
ERROR: [Common 17-165] Too many positional options when parsing…
Diagnostic: this error message is returned by Vivado when the user name on the machine contains ‘space’ characters (like User = “FirstName LastName”).
As for many instances, it is advised not to use special characters in user names, as they will affect the name of special temporary directories (like ‘Temp’ in Windows’).
Spaces in paths are sometimes not well supported by scripting interfaces such as this of Vivado.
Solution: use a user name without spaces or special characters in it.

来自 https://www.exostivlabs.com/knowledgebase/core-inserter-error-error-common-17-165-too-many-positional-options-when-parsing/

That space in the name is breaking the auto generated scripts created when running a simulation from the Vivado GUI. This kind of stuff is why I only use the GUI to generate a script to find all the simulation code for the IPs and then write my own simulation script.

来自 https://www.edaboard.com/threads/error-common-17-165-too-many-positional-options-when-parsing.371254/

最后创建了一个没有空格的工程，解决了