Forum Discussion
nhadzic
New Contributor
1 year agoThank you for your response and don't worry about the delays.
Before I continue, I would like to confirm a few items:
- I am using the Quartus Programmer to JTAG configure the FPGA and to burn POF images to the attached NOR flash. Is that what you mean by the "Flash Programmer tool"?
- Is it possible to change the flash configuration in some way? It appears to me that the default configuration size (44,032 KB) is not sufficient to hold binary images for larger FPGA utilization rates.
I just restored my card to the factory fresh setting by using the avst.pof image from the factory_recovery folder. I will repeat my .BIN experiment now and will report the results.
nhadzic
New Contributor
1 year agoI was finally able to perform the experiments: Sorry about the delay.
- I burned a known good image (FPGA is ~40% utilized). RBF for this image is 38MB. Even though I cannot use RBF, I like to use it as a proxy for the overall binary image size. This worked.
- I then generated binary image that contains a larger FPGA image (~52% utilized). This one is definitely larger than the allocated flash space but increased the size of the binary file so it overflows into the next flash range. This experiment did not work. Image is there as my script reads it back and compares the hash against the file we attempted to write.
- I then repeated step #1 to bring back the card to a working state
So it appears as if MAX-V only looks the "User HW1" location to configure an image from flash. Is there a way to increase the size of the User HW1?