This will take a while though, and there's a chance I'll have to fight bitrot, and that's why I haven't started yet. That's supposedly where I had the environment I used to develop Eigenmath and Utilities. I'll see if I can boot the Linux install I supposedly still have on the hard disk I used to have on my laptop. But I don't want to waste time figuring that out. It's probably fixed by now, or the problem might be in my code, or in libfxcg, after all. It appears that at the time these versions of GCC had some problem emitting code for the Prizm SH4 CPU architecture. I'm not sure but I think Eigenmath was the add-in where I had to use a library frankensteined from miniSDK or whatever that terrible libfxcg alternative was called.įinally, ideally I'd like to use the same 4.x GCC I used before, as a long long time ago I tried GCC 5 and 6 without success. Third, if I recall correctly there are some library shenanigans regarding the C math functions. Second, I need to use my fork of libfxcg (this is not very hard). And it's a bit tricky to set one up.įirst, I need a custom mkg3a (because the add-in has a eActivity strip, and vanilla mkg3a doesn't have support for that) and I'm not sure I still have the source code to that custom mkg3a anywhere. The problem is that I no longer have a Prizm development environment on any of my machines. Now, you may think that the problem is basically solved as the steps that are usually 90% of the work are done (identifying the problem and drafting a solution). I also know how to fix this in terms of code, it's a matter of reusing the solution from Utilities. It appears that the Graph 90+E uses a different VRAM address than the fx-CG50 (since on the emulator for the latter at least, the add-in doesn't show any problems). Eigenmath uses a hardcoded address for these custom functions, which is why on some calculators the graphics are glitched. Utilities doesn't have this problem, as it reads the VRAM address using the appropriate syscall when it starts, caching that address to RAM and using it for custom VRAM manipulation functions from then on. I have also identified the problem, in fact I did so some months ago. I am aware of that and I've seen the issue that was opened in the Eigenmath GitHub.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2023
Categories |