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
Reason for duplication toolchain_program function #141
Comments
The problem with using a common Also, not everything programs through Quartus. |
It seems that you got me wrong. Does that make more sense to you? |
Not all Intel FPGA boards inherently require |
Okay, you're right, that may be a possibility. So don't require But for the second part, what do you think about promiting the |
That would be a liability for the reason I have described: right now |
I'm not entirely getting your point here, but I'm ok with it. As said, if you think that's the right way to go because of the reasons you listed above, I'm fine with it. |
I'm playing around with a intel/altera based platform and found it very easy to define my own platform, that's amazing! ❤️ (I'm probably doing a PR in the near future for it).
What wonders me is that (at least this is true for IntelPlatform devices) the boards share (almost) the same programming code. The only difference I found is that they appear in a different position in the JTAG chain.
What is the reason for not having the code in (...) the
IntelPlatform
class?I also would like to see the
quartus_pgm
program in the required tools list ifdo_program
isTrue
.What are your thoughts about it? I would like to take that as an approach to commit to this project (:
The text was updated successfully, but these errors were encountered: