Occasional Contributor
Super ContributorYou can use various bin2hex tools for the conversion.
It's however not quite clear what you want to achieve. Why would you store .sof configuration file in on-chip ROM?
Or do you mean, you are converting .sof to .hexout with programming file generator tool? It's intended to program e.g. configuration flash.
Occasional ContributorIn my final design I wanted my FPGA able to receive a new programming file from an external source (possibly a processor), the FPGA will then write the new programming file into flash (EPCQ128A in this case) and use the Remote Update System in conjunction with the flash to update the FPGA.
Currently in the testing phase I don't have my external source setup, so I wanted to try storing the new programming file into a ROM and write the ROM contents into the flash.
Super ContributorI see what you want to achieve, problem is however that memory capacity of embedded ROM is much smaller than configuration image size. You can't store a full configuration bit stream in embedded ROM, even if device utilization is low and image compressed.
Occasional ContributorUnderstandable, I was planning on storing the data in mif files and supplying it to possibly 3 or 4 different ROM modules, hopefully this plan doesn't utilize all the available resources in the FPGA.
Occasional ContributorWould the hex translation of a .rbf file be a suitable version of the image to write to flash and be used with the Remote System update?
Super Contributor
