[Dev/Disassembly] The beginners' guide to Evo ECU table lookups
Dec 2, 2010, 10:10 PM
#64
Nothing worth mentioning at this point, I borrowed some books from a buddy of mine he had sitting around from college days. Been searching through those as well as reading through that full textbook I linked to in the other thread. I have been very busy lately dealing with all the holiday stuff going on here as well which has slowed my progress but I am still hitting it hard 
Dec 3, 2010, 08:08 AM
#66
Yes we most certainly can if we know how to lol. I am still having trouble making heads or tails of just how to locate tables in this thing. I can basically see some similairities in the different code I get pointed to when I punch an address from my XML in IDApro. But thats about it at this point I cant tell how on earth these guys can determine what it might do and how to display that info in ecuflash lol.
Oct 10, 2012, 05:50 PM
#67
bit of a thread revival, but i would like to ask
do 2D & 3D tables have a footer byte? i noticed that while looking at the tables, they all end with an 0xFF
cheers
do 2D & 3D tables have a footer byte? i noticed that while looking at the tables, they all end with an 0xFF
cheers
Oct 30, 2012, 03:14 PM
#71
Evolved Member
Not seen any reference to the HDW registers in the any disassembly I've seen, but then I'm a bit rubbish at assembly. dparrish - also from Sydney did a nice expansion on Acumas's disassembly script. Seems to do good things.
Oct 31, 2012, 04:42 PM
#73
Look in the hardware manual, it explains all the hardware registers.
Sorting them all out can actually help quite a bit in getting an idea of what a piece of code might be doing if it starts using hardware registers.
Since this is a thread revival, it's worth saying thanks to those that have helped others understand some of this. While my future in SH disassembly will be limited to simply a hobby, learning how a processor works at the machine code level has provided a strong foundation for me and I am now using embedded processors at work.
It's a hell of a lot easier writing source code than figuring out what machine code is doing. Gives me a huge appreciation for what goes on behind the scenes when writing a couple lines of code to look up a table though.
Sorting them all out can actually help quite a bit in getting an idea of what a piece of code might be doing if it starts using hardware registers.
Since this is a thread revival, it's worth saying thanks to those that have helped others understand some of this. While my future in SH disassembly will be limited to simply a hobby, learning how a processor works at the machine code level has provided a strong foundation for me and I am now using embedded processors at work.
It's a hell of a lot easier writing source code than figuring out what machine code is doing. Gives me a huge appreciation for what goes on behind the scenes when writing a couple lines of code to look up a table though.
