0 Members and 2 Guests are viewing this topic.
I have the notion, that they expanded the customized part of the MPU. T. i. some ports they use, are not longer documented in Renesas documentations. This delays the meals. The first thing I want to know is how the keyboard is read. PORT A of the good old 7705 is not detectable any more.
This is one of the projects I'd like to finish quick. At present I use the CASIO SDK assembler to program testcode. But C/C++ objects should work as well. I'd prefer C++. The result should be a G3A, of course.
By the way, does anyone have a quick bit of code to disable virtual memory for add-ins?
What happened if you try to access to 0xA4000120? MMU error or you simply always read 0?It would be annoying the Prizm processor isn't like a 7705, and I don't understand why Casio would do that.
be sure to introduce yourself in the introduce yourself sub-forum.
C:\casio>sh3_disass.py -s 20070 -e 20080 -p 80020070 prizm3064Dissassembly size: 0x1080020070: d202 .. MOV.L @($02*4+PC),R2 = #805EDCA880020072: 4008 @. SHLL2 R0 ; R0 = syscall number80020074: 002e .. MOV.L @(R0+R2),R0 ; load from table of pointers80020076: 402b @+ JMP @R0 80020078: 0009 .. NOP8002007A: 0000 .. 0000 ?8002007C: 805e .^ .data 805edca8 dword ref:80020070
This table has several thousand entries of which only a few are needed for the time being.