-
Notifications
You must be signed in to change notification settings - Fork 113
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
Need help to verify arch.*.xml and rr_graph.bin on spartan7 #2584
Comments
@mithro Could you give me some guidances? |
@KKtiandao There is no validation of the arch and RR graph apart from the internal checks within VTR. If the flow completes and you are able to get a bitstream (or at least a FASM) as an output, I believe it is enough. What can be verified is whether the output FASM file is actually correct, running |
@acomodi Thanks very much! I'll try fasm2bels. |
@acomodi I see tile-types listed in the CMakeList.txt is less than which actual in spartan7/artix7; While I try to append some new tile and pbtypes according to the info of prjxray-db, make failed. How do I correct the CMakeList.txt? |
Hi @KKtiandao. Can you please open a PR with the current WIP changes you have? This can help understanding a bit more what is going on. Also the error output is quite useful to get a picture of the problem. In general, those tiles and pb_types correspond to the ones defined here (for artix7) and if you want to add some other ones, e.g. the DSP which is currently not present, you need to first define the DSP tile, as well as the DSP pb_type, alongside with the other pb_types here. |
@acomodi Thanks for your reminder. I have created a PR.
@acomodi As dsp is a usefull model and it has already in the prjxray-db, why it is not present? Is there any differences in this flow between dsp and other tiles presented? |
To add spartan7 into arch_def flow, I do some modification based on this pr and ran the arch_defs flow completely. But how do i verify the outputs like arch.*.xml and rr_graph? Simulation?
The text was updated successfully, but these errors were encountered: