Skip to content
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

Provide public api to add build commands #515

Closed
anuejn opened this issue Oct 26, 2020 · 6 comments
Closed

Provide public api to add build commands #515

anuejn opened this issue Oct 26, 2020 · 6 comments
Labels

Comments

@anuejn
Copy link
Contributor

anuejn commented Oct 26, 2020

It would be nice to have (semi) public API to inject custom build commands into the build_name.{sh,bat} files.
My specific use case is to generate a bash script that contains a base64 encoded version of the bit stream that loads the bit stream automatically via the linux fpgamanager infrastructrure on a zynq.
Currently, I am having quite a hack in place to implement that but that constantly breaks and is a very bad solution.

For me live would be easier if TemplatedPlatform had an extra_command_templates property that is guaranteed to be not a property object and therefore easy to override.

@whitequark
Copy link
Member

My specific use case is to generate a bash script that contains a base64 encoded version of the bit stream that loads the bit stream automatically via the linux fpgamanager infrastructrure on a zynq.

This sounds like it should be a part of an external programmer. Could you explain that workflow in a bit more detail?

@anuejn
Copy link
Contributor Author

anuejn commented Oct 26, 2020

At first that logic was inside the toolchain_program() function of the platform but I realized that I want that bash script to be generated for later use even if I do not program the FPGA directly. I see that file a bit more like what a svf file is compared to the normal bitstream format.

@whitequark
Copy link
Member

Ack, that makes sense. I'll see what can be done.

@anuejn
Copy link
Contributor Author

anuejn commented Oct 26, 2020

My workflow involves generating that file (which also contains other stuff from the design like a memorymap).
This file is then copied over to the zynq via scp and executed via ssh in the toolchain_program() function.

@anuejn
Copy link
Contributor Author

anuejn commented Oct 26, 2020

👍

@anuejn
Copy link
Contributor Author

anuejn commented Jun 8, 2021

see #618. Not needed.

@anuejn anuejn closed this as completed Jun 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants