I think you have created a tech support case to get more details regarding this. right?.
I think this is no problem. You can set the burst size to 1 which means every 2 words the flags are updatetd. And in my opinion the best solution is to slow down the write access if partial full is active and monitor the full flag in this mode. This is now described in the slave fifo application note (I think upon my suggestion here in the forum).
what makes me suspicious is the sentence that says the host needs to ignore flag changes in between:
"The device connected to FX3 is expected to complete a burst that it has started regardless of any flag changes in between"
Doesn't this imply that the flags can become invalid in between? And why would somebody want to define a burst size of more than 2?
Hmm...good question. Maybe the burst is also aborted on packet end....but I´m not sure. As I use 75MHz PCLK only, it works with burst = 0.