Retrieving usercode from binary configuration image

Hey Frank,

Thanks for the additional details. I'd like to read a little more about these components, in case I want to use them. What is the best place to look? Is there an app note or user guide you recommend?

I do recall reading at some point that the RSU controller can be provided an image start address. If that is correct, then that could be utilized to add an additional layer of protection, i.e., you can add a header to your .RBF image that software can use for interrogation, and by setting the RSU image start address below that header, it will be ignored. Here's how it would be used;

1. Quartus creates .RBF

2. Add a custom header that identifies; project name, version, unique version control ID (for tracking the original source code used to create the image), target hardware, etc.

3. Use a flash programmer that compares the image header to the target hardware characteristics, eg., reads a board information register or EEPROM.

4. Use the flash programmer to program the entire image to flash, including the header details.

5. At some later point in time, the flash programmer can be used to verify or extract the flash image, and via the header, you can match the binary image to your version controlled code.

If my recollection is correct, then the hardware controller will skip all this information.

Cheers,

Dave