Omnimaga
Omnimaga => News => Topic started by: DJ Omnimaga on March 06, 2011, 02:25:13 pm
-
A few months ago (http://ourl.ca/8692), Qwerty.55 managed to run 3rd-party SH3 assembly code on his Casio fx-CG10 calculator. He made a program that set up the CPU clock speed to double of what it is normally. Unfortunately, the add-in caused a reset after running, so the result wasn't very concluding. However, recently, some add-ins that won't crash have actually been made, including a memory viewer called Insight:
(http://i-lost-the-ga.me/prizminsight.gif)
The current version can be downloaded here (http://ourl.ca/9205/181529).
Beforehand, someone under the nickname Kristaba created an add-in that shows the calculator FPS and fades in to red every second. Although this one isn't very useful, it is still nonetheless impressive to see third-party add-ins already running on the new calculator, despite its recent release.
(http://i-lost-the-ga.me/prizmkristabou.gif)
If you download and install it, be warned that to exit, you must pull a battery, though. It can be downloaded here (http://ourl.ca/8207/176520). It tests the LCD's framerate by filling the VRAM with a color.
And this is nothing, SimonLothar has been recently working on a third-party C SDK (http://ourl.ca/9205/181529), ported from a FX-9860G one made by the community a while ago. z80man, on his side, is working on an emulator. There is also a tool package that can be useful for PRIZM hackers located right here (http://ourl.ca/9490).
-
Wow, the Prizm development is looking great! Wonderful job Qwerty, Kristaba, SimonLothar, and z80man. :D
-
Wow! :D
Now we should be able to port games to color. :w00t:
-
Wow! :D
Now we should be able to port games to color. :w00t:
Well... Programming is still hard. I don't think we have discovered any display routines in the OS other than basic text stuff, and modifying the add-ins to match the checksums isn't exactly easy either.
-
Well... Programming is still hard. I don't think we have discovered any display routines in the OS other than basic text stuff, and modifying the add-ins to match the checksums isn't exactly easy either.
I am sure that you guys will be able to figure it out. :)
EDIT: W00t 69th post
-
I love the progress we are making with this :D So we know where the screen memory is then?
-
Yes.
-
Sweet ^^ Time for a graphics demo :P
*hides*
-
I can't wait to see a game or something! So why did this not take as long as the Nspire to "hack"?
-
Because it doesn't require OS exploits. The add-ins we generate are exactly the same to the calculator as those generated by Casio as far as the calculator's concerned.
-
hey, once you have graphics down I'll buy a prizm.
-
Nice. Perhaps I'll buy one after you guys get decent C support :D
-
it has a touch screen
does it have enough processing power to emulate ds games?
-
Sorry, no touch screen. Game boy DS games are also unlikely given that the DS runs on two processors simultaneously, one of which operates faster than the Prizm's processor does normally.
-
Probably GBA emulation, but given the last attempt on the faster TI-Nspire, it would most likely require a lot of experience in SH3 assembly.
-
@Qwerty.55: Yeah, but if the processor is underclocked, it means we can set it back to its original speed without causing any trouble to the calc, no ?! But even in that case, DS emulation seems very unlikely...
-
It can only overclock to 116 MHz, as far as we know, which probably isn't fast enough for an emulation layer to not be noticeable.
-
The DS has two CPUs of a different architecture. A real-time interpreter is definitely impossible, and a recompiler is unlikely. The GBA has only one CPU, an ARM at 16 MHz, so GBA emulation may be possible.
-
We have to take in account the fact these handhelds also got video memory or even video cards that requires to be emulated too, right?
-
As far as I know, emulating a dual cpu device with only a single cpu is near impossible even if the clock speed for the device is three times higher than the emulated one. Reason being is that you have to incorporate multi-tasking on a single threaded device which is hell on any programmer.
-
DS emulation is next to impossible, because there is two CPUs, and a gpu to emulate. Not to mention how awkward playing a game that uses the touchscreen would be on a calc.
-
Indeed. I think we should stick to other handhelds and older consoles like the NES, SNES, GB/C/A, Sega Megadrive/Genesis, etc.