I’m looking for help; I’m a noob. Something I know I need, is labeling large chunks of binary as an arbitrary data table, so it doesn’t try to find code patterns in it.
The primary focus.
And if anybody already worked on what I’m doing and can share a file with a bunch of the work done, that’d be awesome.
Done what I can with just tuning. Long story short, I’m trying to make the most basic, easy to tune, race ECU possible with this stock ECU, and as few sensors as reasonably possible, because this ECU is very accessible as far as cost and easy to find info.
It’s been a minute since I’ve used Ghidra at work but you need to define a new struct in the data manager and size it to hold the blob in bytes. Then link the blob to the struct and it won’t be analyzed. Be sure it’s not a struct that Ghidra is having difficulty auto-analyzing. Clues that it’s a struct would be one of the registerings derencing at various offsets in rapid succession. You can view the guessed structs in the data manager and see what Guides was able to infer about your block of code.
I’d expect to see a bit of this, especially with the knock sensors interpolating between high and low octane tables. I don’t follow the description super well, but even just based on the name. Makes sense to have a hardware function for something that needs to be low latency and happens a lot.
