![]() I'm doing my proof of concept against the known values in Universal Patcher for the time being to flesh out this concept. Then the 3rd layer is where the global var is used in an if statement against the fan 1 temp setting in the tune and changes so bits on a ram value which I suspect is some sort of fan status var. The function where the temp var is moved into the global var changed 3100 vs 3400/3800 (slight change but it breaks the mask). The code to read the ECT sensor is the same across all 3. Why reverse engineer the same basic file 20 times because of small changes?Īnyway, I made a really basic proof of concept in c# and tested it against the 3 P04 bins I have (3100, 3400, and a 3800 SC one). In theory I could take this concept a step farther and confirm function references, validate if a given function changes between oses, etc. Once a sensor value is tracked to a function, I count the whole function as "validated" and other references within the function can be extracted via the mask setup. Since it's doing the reverse engineering as an automated process it works on masks to identify sections of code where sensors are read, which memory addresses they are stored in, when they are assigned to global vars, etc. The very basic concept if a program that reads a bin file and spits out an xdf file. I've been poking at a concept I've thought of and figured I'd make a post to log the status of my work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |