New Contributor
Super ContributorHello,
flash programming through .jic generally only writes the memory range used by your design. It's important to enable compression in programming file converter for the .sof source(s). Also JTAG adapter speed is important. Some third party products with own drivers are using ineffective protocols. Best results are achieved with USB Blaster and USB Blaster II.
New ContributorHeh, we literally discovered that we were using the USB Blaster Rev Cs and that these are only 6M speed. We don't have the USB Blaster IIs, but are looking to get our hands on them (no one appears to have any). I am also going to try a third party device, but I don't have high hopes for reliability.
The guys who left us these projects were working a little haphazzardly on development units. I am fairly certain that this initial image uses about 12-15MB of the 128MB flash, and then the bulk of the image is clearing out/resetting it.
We are nearing production where programming time is becoming a crucial issue, and if we can cut down on the programming time by only writing what is necessary at this stage, we would like to do that. I am aware that it's best practice to erase the entire flash prior to initial programming, but 190 seconds is too long for production, and if those areas aren't used (or can be erased at a later step than this initial gating program step) we would be better off.
But from your answer it sounds like we should at least try and determine if this image is "playing it safe" and writing an extended image that isn't necessary.
Thank you!
