My raster routine works, but only after several NOPs inserted during increasingly superstitious testing. I am going back to count the path from the interrupt through the branch cases.
What do you write down when stabilizing a line?
Stable timing without a carpet of mystery NOPs
4 replies · opened 1 DAY ago
Every possible branch cost, where bad lines can occur, and whether the entry jitter has actually been removed.
Mark cycles beside instructions temporarily. It is tedious once and cheaper than rediscovering them after an edit.
Separate “alignment NOP” from “I do not know why this helps” in comments. The second kind gets investigated before release.
Found it: one branch crossed a page only in the failing build. Three mystery NOPs have now been honorably discharged.
Want to add to this transmission?
SIGN IN TO REPLY →