With the release of OS 2.55MP, it seems we're going to have to disassemble each update TI pushes out and see what they change, so I put together a little package to make it easier for myself, and if you care, you too.
I created a little C# thing last night called Pterodactyl that creates IDC scripts for use with IDA Pro generated from elements of ti83plus.inc to automagically set labels and cross references of page 0 calls and BCALLs throughout all (now 19) pages of the TI-OS, plus RAM equates.
This makes it very easy to get IDA to analyze most of the code for us and it makes it a lot easier to dive into any OS version and find out exactly what it's doing and why.
It's at http://brandonw.net/calcstuff/pterodactyl.zip and the source is at http://brandonw.net/svn/calcstuff/Pterodactyl/trunk/ if anyone wants to use it.
I was able to pound out an OS 2.55MP disassembly inside of an hour using this tool which I've uploaded at http://brandonw.net/crap/OS2.55MPDisassembly.zip if you want to dig into it yourself.
Hopefully this will help me/us analyze differences in OS versions quickly and more easily than before, and possibly figure out what TI did wrong with the MathPrint OSes and maybe even fix them.
Forgive the horrible code, it was quick and dirty and never meant to be used by your average user.
I created a little C# thing last night called Pterodactyl that creates IDC scripts for use with IDA Pro generated from elements of ti83plus.inc to automagically set labels and cross references of page 0 calls and BCALLs throughout all (now 19) pages of the TI-OS, plus RAM equates.
This makes it very easy to get IDA to analyze most of the code for us and it makes it a lot easier to dive into any OS version and find out exactly what it's doing and why.
It's at http://brandonw.net/calcstuff/pterodactyl.zip and the source is at http://brandonw.net/svn/calcstuff/Pterodactyl/trunk/ if anyone wants to use it.
I was able to pound out an OS 2.55MP disassembly inside of an hour using this tool which I've uploaded at http://brandonw.net/crap/OS2.55MPDisassembly.zip if you want to dig into it yourself.
Hopefully this will help me/us analyze differences in OS versions quickly and more easily than before, and possibly figure out what TI did wrong with the MathPrint OSes and maybe even fix them.
Forgive the horrible code, it was quick and dirty and never meant to be used by your average user.