Skip to content

Failed to load argument parser (Vivado 2014.3) #348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
marbehant opened this issue Oct 28, 2014 · 7 comments
Open

Failed to load argument parser (Vivado 2014.3) #348

marbehant opened this issue Oct 28, 2014 · 7 comments

Comments

@marbehant
Copy link

Get following error when installing my own app in Vivado 2014.3:

tclapp::install utils
INFO: [Common 17-660] Loading Tcl app 'utils' into namespace {mycompany::utils}
ERROR: [Common 17-359] Failed to load argument parser (attempt to provide package ::tclapp::support::args 1.0 failed: no version of package ::tclapp::support::args provided).

Same app is working fine in previous versions of Vivado.

@marbehant
Copy link
Author

Still playing with XilinxTclStore in Vivado 2014.3

Actually the "Failed to load argument parser" error appears when opening the command help in the GUI (Xilinx Tcl Store > Details > Tcl Procs > Help...). Same error occurs with Xilinx apps.

Relative Tcl package name of installed apps is broken, we need to use fully qualified namespace to run commands.

% xilinx::projutils::convert_ngc -help
invalid command name "xilinx::projutils::convert_ngc"

% ::tclapp::xilinx::projutils::convert_ngc -help
ERROR: [Vivado-projutils-301] Unknown option '-help', please type 'convert_ngc -help' for usage info.
ERROR: [Common 17-39] 'send_msg_id' failed due to earlier errors.

@binochotta
Copy link
Contributor

projutils is loaded into the global namespace. You should run it without any namespace. E.g. convert_ngc –help.
Thanks,
Bin

From: Marbehant Jean-Francois [mailto:[email protected]]
Sent: Tuesday, October 28, 2014 6:42 AM
To: Xilinx/XilinxTclStore
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

Still playing with XilinxTclStore in Vivado 2014.3

Actually the "Failed to load argument parser" error appears when opening the command help in the GUI (Xilinx Tcl Store > Details > Tcl Procs > Help...). Same error occurs with Xilinx apps.

Relative Tcl package name of installed apps is broken, we need to use fully qualified namespace to run commands.

% xilinx::projutils::convert_ngc -help

invalid command name "xilinx::projutils::convert_ngc"

% ::tclapp::xilinx::projutils::convert_ngc -help

ERROR: [Vivado-projutils-301] Unknown option '-help', please type 'convert_ngc -help' for usage info.

ERROR: [Common 17-39] 'send_msg_id' failed due to earlier errors.


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60756245.

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

@marbehant
Copy link
Author

Hi Bin,

projutils was not the best example. But still “convert_ngc -help” doesn’t work for me.

I need to use fully qualified namespace for all apps (designutils…). I get the same error from the command help GUI (for example “invalid command name "xilinx::designutils::bisect_pblock"” in the Command Reference window).

Regards,
Jean-François

From: Bin Ochotta [mailto:[email protected]]
Sent: mardi 28 octobre 2014 16:39
To: Xilinx/XilinxTclStore
Cc: Marbehant, Jean-François
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

projutils is loaded into the global namespace. You should run it without any namespace. E.g. convert_ngc –help.
Thanks,
Bin

From: Marbehant Jean-Francois [mailto:[email protected]]
Sent: Tuesday, October 28, 2014 6:42 AM
To: Xilinx/XilinxTclStore
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

Still playing with XilinxTclStore in Vivado 2014.3

Actually the "Failed to load argument parser" error appears when opening the command help in the GUI (Xilinx Tcl Store > Details > Tcl Procs > Help...). Same error occurs with Xilinx apps.

Relative Tcl package name of installed apps is broken, we need to use fully qualified namespace to run commands.

% xilinx::projutils::convert_ngc -help

invalid command name "xilinx::projutils::convert_ngc"

% ::tclapp::xilinx::projutils::convert_ngc -help

ERROR: [Vivado-projutils-301] Unknown option '-help', please type 'convert_ngc -help' for usage info.

ERROR: [Common 17-39] 'send_msg_id' failed due to earlier errors.


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60756245.

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60776312.

This message is subject to the following terms and conditions: MAIL DISCLAIMERhttp://www.barco.com/en/maildisclaimer

@dpefour
Copy link
Contributor

dpefour commented Oct 28, 2014

Hi Jean-Francois,

Can you try to run tclapp::reset_tclstore and re-start Vivado?

Let us know if it works.

Thanks,
David

From: Marbehant Jean-Francois [mailto:[email protected]]
Sent: Tuesday, October 28, 2014 8:53 AM
To: Xilinx/XilinxTclStore
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

Hi Bin,

projutils was not the best example. But still “convert_ngc -help” doesn’t work for me.

I need to use fully qualified namespace for all apps (designutils…). I get the same error from the command help GUI (for example “invalid command name "xilinx::designutils::bisect_pblock"” in the Command Reference window).

Regards,
Jean-François

From: Bin Ochotta [mailto:[email protected]]
Sent: mardi 28 octobre 2014 16:39
To: Xilinx/XilinxTclStore
Cc: Marbehant, Jean-François
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

projutils is loaded into the global namespace. You should run it without any namespace. E.g. convert_ngc –help.
Thanks,
Bin

From: Marbehant Jean-Francois [mailto:[email protected]]
Sent: Tuesday, October 28, 2014 6:42 AM
To: Xilinx/XilinxTclStore
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

Still playing with XilinxTclStore in Vivado 2014.3

Actually the "Failed to load argument parser" error appears when opening the command help in the GUI (Xilinx Tcl Store > Details > Tcl Procs > Help...). Same error occurs with Xilinx apps.

Relative Tcl package name of installed apps is broken, we need to use fully qualified namespace to run commands.

% xilinx::projutils::convert_ngc -help

invalid command name "xilinx::projutils::convert_ngc"

% ::tclapp::xilinx::projutils::convert_ngc -help

ERROR: [Vivado-projutils-301] Unknown option '-help', please type 'convert_ngc -help' for usage info.

ERROR: [Common 17-39] 'send_msg_id' failed due to earlier errors.


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60756245.

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60776312.

This message is subject to the following terms and conditions: MAIL DISCLAIMERhttp://www.barco.com/en/maildisclaimer


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60779044.

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

@binochotta
Copy link
Contributor

Hi Jean-François,

Did you use env XILINX_TCLAPP_REPO to point to your local repository? Can you send me vivado.log from where you start vivado?
Thanks,
Bin

From: Marbehant Jean-Francois [mailto:[email protected]]
Sent: Tuesday, October 28, 2014 8:53 AM
To: Xilinx/XilinxTclStore
Cc: Bin Ochotta
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

Hi Bin,

projutils was not the best example. But still “convert_ngc -help” doesn’t work for me.

I need to use fully qualified namespace for all apps (designutils…). I get the same error from the command help GUI (for example “invalid command name "xilinx::designutils::bisect_pblock"” in the Command Reference window).

Regards,
Jean-François

From: Bin Ochotta [mailto:[email protected]]
Sent: mardi 28 octobre 2014 16:39
To: Xilinx/XilinxTclStore
Cc: Marbehant, Jean-François
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

projutils is loaded into the global namespace. You should run it without any namespace. E.g. convert_ngc –help.
Thanks,
Bin

From: Marbehant Jean-Francois [mailto:[email protected]]
Sent: Tuesday, October 28, 2014 6:42 AM
To: Xilinx/XilinxTclStore
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

Still playing with XilinxTclStore in Vivado 2014.3

Actually the "Failed to load argument parser" error appears when opening the command help in the GUI (Xilinx Tcl Store > Details > Tcl Procs > Help...). Same error occurs with Xilinx apps.

Relative Tcl package name of installed apps is broken, we need to use fully qualified namespace to run commands.

% xilinx::projutils::convert_ngc -help

invalid command name "xilinx::projutils::convert_ngc"

% ::tclapp::xilinx::projutils::convert_ngc -help

ERROR: [Vivado-projutils-301] Unknown option '-help', please type 'convert_ngc -help' for usage info.

ERROR: [Common 17-39] 'send_msg_id' failed due to earlier errors.


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60756245.

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60776312.

This message is subject to the following terms and conditions: MAIL DISCLAIMERhttp://www.barco.com/en/maildisclaimer


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60779044.

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

@marbehant
Copy link
Author

Hi David, Hi Bin,

I’ve finally found the culprit: 250e258

And it raises an interesting question. My local repo is a clone of the master branch of XilinxTclStore. It also contains my own tcl apps.
From time to time I run “git pull” to fetch latest updates from GitHub.

Since XILINX_TCLAPP_REPO points to my local repo, first time I run a new version of Vivado, it copies the support package (XilinxTclStore/support) from my cloned repo to ~/.Xilinx/Vivado/20xx.y
And it looks like support/args/args.tcl is tightly tied to Vivado. So any breaking change in the support package and the wrong sequence of events lead to a broken XilinxTclStore.

The workaround is to unset XILINX_TCLAPP_REPO, delete ~/.Xilinx/Vivado/2014.3, re-run Vivado. After that I can use my local repo.
My feeling is that the support package should always be copied from the Vivado installation.

Maybe should I track a different branch for each version (which wouldn’t have helped here since the breaking change affects also the branch 2014.3).
And since I can no longer use “set_param tclapp.sharedRepoPath” in the init.tcl script of the Vivado installation, I have only one system-wide XILINX_TCLAPP_REPO env for all versions of Vivado installed on the server.

Will XilinxTclStore support multiple repositories? That would be the best solution.

Best regards,
Jean-François

From: dpefour [mailto:[email protected]]
Sent: mardi 28 octobre 2014 16:59
To: Xilinx/XilinxTclStore
Cc: Marbehant, Jean-François
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

Hi Jean-Francois,

Can you try to run tclapp::reset_tclstore and re-start Vivado?

Let us know if it works.

Thanks,
David

From: Marbehant Jean-Francois [mailto:[email protected]]
Sent: Tuesday, October 28, 2014 8:53 AM
To: Xilinx/XilinxTclStore
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

Hi Bin,

projutils was not the best example. But still “convert_ngc -help” doesn’t work for me.

I need to use fully qualified namespace for all apps (designutils…). I get the same error from the command help GUI (for example “invalid command name "xilinx::designutils::bisect_pblock"” in the Command Reference window).

Regards,
Jean-François

From: Bin Ochotta [mailto:[email protected]]
Sent: mardi 28 octobre 2014 16:39
To: Xilinx/XilinxTclStore
Cc: Marbehant, Jean-François
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

projutils is loaded into the global namespace. You should run it without any namespace. E.g. convert_ngc –help.
Thanks,
Bin

From: Marbehant Jean-Francois [mailto:[email protected]]
Sent: Tuesday, October 28, 2014 6:42 AM
To: Xilinx/XilinxTclStore
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

Still playing with XilinxTclStore in Vivado 2014.3

Actually the "Failed to load argument parser" error appears when opening the command help in the GUI (Xilinx Tcl Store > Details > Tcl Procs > Help...). Same error occurs with Xilinx apps.

Relative Tcl package name of installed apps is broken, we need to use fully qualified namespace to run commands.

% xilinx::projutils::convert_ngc -help

invalid command name "xilinx::projutils::convert_ngc"

% ::tclapp::xilinx::projutils::convert_ngc -help

ERROR: [Vivado-projutils-301] Unknown option '-help', please type 'convert_ngc -help' for usage info.

ERROR: [Common 17-39] 'send_msg_id' failed due to earlier errors.


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60756245.

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60776312.

This message is subject to the following terms and conditions: MAIL DISCLAIMERhttp://www.barco.com/en/maildisclaimer


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60779044.

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60780228.

This message is subject to the following terms and conditions: MAIL DISCLAIMERhttp://www.barco.com/en/maildisclaimer

@binochotta
Copy link
Contributor

Hi Jean-François,

Thanks for the detailed explanation of what went wrong.
We will look into it and see we can improve in the future.
Bin

From: Marbehant Jean-Francois [mailto:[email protected]]
Sent: Wednesday, October 29, 2014 5:11 AM
To: Xilinx/XilinxTclStore
Cc: Bin Ochotta
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

Hi David, Hi Bin,

I’ve finally found the culprit: 250e258

And it raises an interesting question. My local repo is a clone of the master branch of XilinxTclStore. It also contains my own tcl apps.
From time to time I run “git pull” to fetch latest updates from GitHub.

Since XILINX_TCLAPP_REPO points to my local repo, first time I run a new version of Vivado, it copies the support package (XilinxTclStore/support) from my cloned repo to ~/.Xilinx/Vivado/20xx.y
And it looks like support/args/args.tcl is tightly tied to Vivado. So any breaking change in the support package and the wrong sequence of events lead to a broken XilinxTclStore.

The workaround is to unset XILINX_TCLAPP_REPO, delete ~/.Xilinx/Vivado/2014.3, re-run Vivado. After that I can use my local repo.
My feeling is that the support package should always be copied from the Vivado installation.

Maybe should I track a different branch for each version (which wouldn’t have helped here since the breaking change affects also the branch 2014.3).
And since I can no longer use “set_param tclapp.sharedRepoPath” in the init.tcl script of the Vivado installation, I have only one system-wide XILINX_TCLAPP_REPO env for all versions of Vivado installed on the server.

Will XilinxTclStore support multiple repositories? That would be the best solution.

Best regards,
Jean-François

From: dpefour [mailto:[email protected]]
Sent: mardi 28 octobre 2014 16:59
To: Xilinx/XilinxTclStore
Cc: Marbehant, Jean-François
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

Hi Jean-Francois,

Can you try to run tclapp::reset_tclstore and re-start Vivado?

Let us know if it works.

Thanks,
David

From: Marbehant Jean-Francois [mailto:[email protected]]
Sent: Tuesday, October 28, 2014 8:53 AM
To: Xilinx/XilinxTclStore
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

Hi Bin,

projutils was not the best example. But still “convert_ngc -help” doesn’t work for me.

I need to use fully qualified namespace for all apps (designutils…). I get the same error from the command help GUI (for example “invalid command name "xilinx::designutils::bisect_pblock"” in the Command Reference window).

Regards,
Jean-François

From: Bin Ochotta [mailto:[email protected]]
Sent: mardi 28 octobre 2014 16:39
To: Xilinx/XilinxTclStore
Cc: Marbehant, Jean-François
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

projutils is loaded into the global namespace. You should run it without any namespace. E.g. convert_ngc –help.
Thanks,
Bin

From: Marbehant Jean-Francois [mailto:[email protected]]
Sent: Tuesday, October 28, 2014 6:42 AM
To: Xilinx/XilinxTclStore
Subject: Re: [XilinxTclStore] Failed to load argument parser (Vivado 2014.3) (#348)

Still playing with XilinxTclStore in Vivado 2014.3

Actually the "Failed to load argument parser" error appears when opening the command help in the GUI (Xilinx Tcl Store > Details > Tcl Procs > Help...). Same error occurs with Xilinx apps.

Relative Tcl package name of installed apps is broken, we need to use fully qualified namespace to run commands.

% xilinx::projutils::convert_ngc -help

invalid command name "xilinx::projutils::convert_ngc"

% ::tclapp::xilinx::projutils::convert_ngc -help

ERROR: [Vivado-projutils-301] Unknown option '-help', please type 'convert_ngc -help' for usage info.

ERROR: [Common 17-39] 'send_msg_id' failed due to earlier errors.


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60756245.

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60776312.

This message is subject to the following terms and conditions: MAIL DISCLAIMERhttp://www.barco.com/en/maildisclaimer


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60779044.

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60780228.

This message is subject to the following terms and conditions: MAIL DISCLAIMERhttp://www.barco.com/en/maildisclaimer


Reply to this email directly or view it on GitHubhttps://github.com//issues/348#issuecomment-60912539.

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants