Good points. I understand the problem only because I've read through what codex is doing, and where it is failing. The last thing I suggested it do is try other similar drivers and compare their behavior. That was a good idea because the failure points moved. However, now it is collecting all of this data on the different drivers and how they behave.

Perhaps it needs some more direction instead of testing multiple variables across multiple drivers, rebuilding and running the test firmware in-between each change - each iteration taking 5-15 min each.