Skip to content

BD Tcl generation fails when spaces present in project path #15

@Jargendas

Description

@Jargendas

Thank you for the scripts, they are really helpful! I noticed that generating the BD tcl fails when spaces are present in the project path in Windows. I couldn't pin it down to where exactly it fails, but multiple errors and warnings are thrown which indicate the path is split at the spaces:

INFO: [BD 5-453] Writing out BD creation steps for design_1 as a TCL proc
WARNING: [BD 5-452] The block design design_1 has not been validated, therefore, a block design created using this Tcl proc may result in errors during validation.
WARNING: [Vivado 12-818] No files matched 'C:/Users/<username>/Downloads/Contains'
WARNING: [Vivado 12-818] No files matched 'Space/vivado_project/Test.srcs/sources_1/bd/design_1/design_1.bd'
WARNING: [Vivado 12-818] No files matched 'C:/Users/<username>/Downloads/Contains'
WARNING: [Vivado 12-818] No files matched 'Space/vivado_project/Test.srcs/sources_1/bd/design_1/design_1.bd'
ERROR: [Common 17-55] 'get_property' expects at least one object.
Resolution: If [get_<value>] was used to populate the object, check to make sure this command returns at least one valid object.

The BD is placed in path C:/Users/<username>/Downloads/Contains Space/vivado_project/Test.srcs/sources_1/bd/design_1/design_1.bd in this example. Without the space, everything runs smoothly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions