Spartan® Family FPGAs

[hgleamon1]

Hello,

I appreciate that there are a few older threads that cover, in part, this query but I am still a little confused as to how to apply it all to the way I would like to approach the use of Multiboot and the HWICAP.

As graphically noted in UG380, I would a 2-stream multiboot with a header. This is the easy bit. It becomes tougher when, via software running on an external CPU, I would like to write a new multiboot stream to the configuration memory that leaves the original multiboot intact to become the NEW golden image (i.e. a firmware update where the previous version becomes the golden image). This may continue for as long as firmware updates become available for this particular product, with the multiboot and golden image swapping places in physical memory.

I realise that, in this case, the header must be rewritten to change the information in the header. After the data writing, the software application will trigger a reconfiguration of the FPGA through the HWICAP module (or, possibly, cycle the PROGRAM_B pin). The software writing to the configuration memory is required (I think) to ensure that the new firmware image is loaded first on the cycling of power.

So, a couple of questions:

1. Is it possible to "move" the location of the golden image to a new memory location (i.e. move the address values extant in GENERAL1 and GENERAL2 to GENERAL3 and GENERAL4 respectively)?

2. If I write a new header (outside of the ISE environment), is there a minimum set of information that the header must contain to allow all of the above to function?

Thanks,

Howard

[mcgovern · Accepted solution]

Hi Howard,

1. Is it possible to "move" the location of the golden image to a new memory location (i.e. move the address values extant in GENERAL1 and GENERAL2 to GENERAL3 and GENERAL4 respectively)?

Yes. You can write to these registers using the ICAP and so "move" your Golden image. Be careful with this approach if you intend to use Multiboot for Safe Update.

2. If I write a new header (outside of the ISE environment), is there a minimum set of information that the header must contain to allow all of the above to function?

Thsi really depends on your Multiboot and Fallback requirements. Reference the SP605 Multiboot design. It has info on generating a header and is an excellent resource to customize your header.

-P