thanks for the responses guys. "The ROM code that you have in your driverlib.c file might differ in notation, however it should be binary compatible with the the code that you see in the individual peripheral source files." Famous last words. Has anyone actually compared the previous rom image against what the current code actually produces? I'm sure I'll figure all this out, but the current practices tend to introduce problems rather than reduce them. Not beating you guys up, trying to help. The driverlib is open source (BSD license). The way I would have dealt with this issue is a) first put the code (driverlib) in a git repository (github), b) when the ROM code was released to the sand folks to burn into the chip that is a release and I would have marked the repository accordingly. That would snapshot exactly what and how the driverlib got built for the ROM image and it is replicatable. then the new changes can get made and it would be explicitly clear as to what those changes are and what the exact state of the code is. Right now there are I don't know how many copies of all this source floating around. And there are various differences showing up in the files that should be same but aren't. Not only is it very confusing but its how bugs creep in. I was the 4th s/w engineer at cisco and we had to deal with this in spades as well. million+ lines of code.
↧