Occasional Contributor
ContributorHi Scotty2,
1, Would it be possible to explain how the "NameHash" at the end of the RPD file is generated by Quartus?
When I generate an RPD file, I did not see this info as you showed in your code. There's also no related info in our documentations. Is it possibly something created by yourself?
2, How come the RPD file generated by Quartus is slightly different than the one read back from the flash using the rsu_client?
I will confirm this question with our RSU experts.
3, Would it be possible to know how the contents of the JIC file is translated and converted by the JTAG programmer to the QSPI flash?
As you can see in "Programming File Generator", when you generate the JIC file, the "FLASH loader" must be selected. Therefore, there's actually a "FLASH loader" in JIC file.
When you start programming with JIC file, the "FLASH loader" will firstly be configured to FPGA, so that the FPGA will act as a bridge between Programmer and the FLASH. After the bridge is built, the raw configuration data will be programmed into FLASH through FLASH loader.
Not sure if this explanation answers your question?
Definition of JIC file: https://www.intel.com/content/www/us/en/programmable/quartushelp/current/index.htm#reference/glossary/def_jic.htm
Thanks & Regards,
Xiaoyan
Occasional ContributorHi Xiaoyan,
1. I have rechecked my Bitstream and RPD file generation process, while I do run Quartus post flow and post module scripts, they do not try to embed any hash into the binaries. The "nameHash" also does not match the one generated by Quartus at the end of the generation with the name "Design Hash".
2. Any update on this?
3. Yes, thank you.
Regards
