Occasional Contributor
ContributorHi beam_me_up_scotty,
RPD map is not provided for the security of user design.
If you want to include some version information to the RPD, there's an idea that maybe you can try to add a HEX page when you try to create an POF file in "convert programming file" window.
Since you mentioned that you may use RSU feature, also pay attention to avoid this HEX data from overwriting the RSU pointers.
Thanks & Regards,
Xiaoyan
Occasional ContributorHi Xiaoyan,
Thank you for the response, I will investigate adding the HEX file with the Programming File Generator. I do have a few follows ups!
Firstly, would it be possible to explain how the "NameHash" at the end of the RPD file is generated by Quartus?
00070020 53 69 67 6e 2d 32 31 2e 32 6e 64 2d 32 32 2e 34 |Sign-21.2nd-22.4| 00070030 61 63 73 2d 31 00 00 00 0f 00 00 00 54 00 00 00 |acs-1.......T...| 00070040 4e 61 6d 65 48 61 73 68 3a 34 31 31 39 39 46 44 |NameHash:41199FD| 00070050 37 30 32 38 45 46 43 35 32 44 46 34 36 37 46 44 |7028EFC52DF467FD| 00070060 45 34 35 32 33 45 38 38 37 39 34 36 42 39 31 42 |E4523E887946B91B| 00070070 41 30 39 36 42 39 33 38 33 30 31 37 39 34 37 45 |A096B9383017947E| 00070080 30 37 37 39 39 44 43 41 45 00 00 00 25 00 00 00 |07799DCAE...%...|
Secondly, how come the RPD file generated by Quartus is slightly different than the one read back from the flash using the rsu_client?
$$ cmp -l s0_dumped.rpd s0_quartus.rpd 7946 0 260 7947 0 3 7954 0 160 7955 0 5 8189 343 121 8190 64 276 8191 64 350 8192 53 113
Lastly, 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?
Thank you very much for your support.
