Author Topic: Casio Prizm documentation  (Read 240310 times)

0 Members and 1 Guest are viewing this topic.

Offline calc84maniac

  • eZ80 Guru
  • Coder Of Tomorrow
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2912
  • Rating: +471/-17
    • View Profile
    • TI-Boy CE
Re: Casio Prizm documentation
« Reply #375 on: February 09, 2011, 11:03:34 pm »
Do you have any idea of how to change the actual size of the application? If you have that info, you could probably generate an working add-in from scratch.
"Most people ask, 'What does a thing do?' Hackers ask, 'What can I make it do?'" - Pablos Holman

Offline z80man

  • Casio Traitor
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 977
  • Rating: +85/-3
    • View Profile
Re: Casio Prizm documentation
« Reply #376 on: February 09, 2011, 11:16:46 pm »
Do you have any idea of how to change the actual size of the application? If you have that info, you could probably generate an working add-in from scratch.
I can change the size of the app by changing a few bytes in the header. and by generate a working add-in from scratch, qwerty and I have already done this, but the apps are very simple so far because we had to program in SH3 hex.

List of stuff I need to do before September:
1. Finish the Emulator of the Casio Prizm (in active development)
2. Finish the the SH3 asm IDE/assembler/linker program (in active development)
3. Create a partial Java virtual machine  for the Prizm (not started)
4. Create Axe for the Prizm with an Axe legacy mode (in planning phase)
5. Develop a large set of C and asm libraries for the Prizm (some progress)
6. Create an emulator of the 83+ for the Prizm (not started)
7. Create a well polished game that showcases the ability of the Casio Prizm (not started)

Offline AngelFish

  • Is this my custom title?
  • Administrator
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 3242
  • Rating: +270/-27
  • I'm a Fishbot
    • View Profile
Re: Casio Prizm documentation
« Reply #377 on: February 14, 2011, 03:48:04 am »
Oh, if anyone's curious, the MD5 hash of the OS is probably the 16 byte sequence located at 0x00001854h in prizm3064. If it were executable code, it'd be an infinite loop.
∂²Ψ    -(2m(V(x)-E)Ψ
---  = -------------
∂x²        ℏ²Ψ

Offline AngelFish

  • Is this my custom title?
  • Administrator
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 3242
  • Rating: +270/-27
  • I'm a Fishbot
    • View Profile
Re: Casio Prizm documentation
« Reply #378 on: February 14, 2011, 03:47:14 pm »
I don't know about anyone else, but here's the data I've been wanting for quite some time:

Screen buffer address: 0xA8000000
Screen buffer size: 0x28800 (162 Kilobytes)

Enjoy  :)
∂²Ψ    -(2m(V(x)-E)Ψ
---  = -------------
∂x²        ℏ²Ψ

Offline jnesselr

  • King Graphmastur
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2270
  • Rating: +81/-20
  • TAO == epic
    • View Profile
Re: Casio Prizm documentation
« Reply #379 on: February 14, 2011, 06:21:24 pm »
I don't know about anyone else, but here's the data I've been wanting for quite some time:

Screen buffer address: 0xA8000000
Screen buffer size: 0x28800 (162 Kilobytes)

Enjoy  :)
Woot! Way to go, how did you find it? Did you shotgun your ram? And is it auto-update? e.g, mapped to that piece of ram?

Offline AngelFish

  • Is this my custom title?
  • Administrator
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 3242
  • Rating: +270/-27
  • I'm a Fishbot
    • View Profile
Re: Casio Prizm documentation
« Reply #380 on: February 14, 2011, 07:04:46 pm »
As much as I wish I had found that address, it was Simon Lothar who announced it. Apparently he's compiled quite a few bits of interesting information, some expected and others a complete surprise.
∂²Ψ    -(2m(V(x)-E)Ψ
---  = -------------
∂x²        ℏ²Ψ

Offline jnesselr

  • King Graphmastur
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2270
  • Rating: +81/-20
  • TAO == epic
    • View Profile
Re: Casio Prizm documentation
« Reply #381 on: February 14, 2011, 07:23:27 pm »
As much as I wish I had found that address, it was Simon Lothar who announced it. Apparently he's compiled quite a few bits of interesting information, some expected and others a complete surprise.
Who is that?

Offline AngelFish

  • Is this my custom title?
  • Administrator
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 3242
  • Rating: +270/-27
  • I'm a Fishbot
    • View Profile
Re: Casio Prizm documentation
« Reply #382 on: February 14, 2011, 07:27:00 pm »
A member of the Casio community who's been hacking the Prizm independently of us.
∂²Ψ    -(2m(V(x)-E)Ψ
---  = -------------
∂x²        ℏ²Ψ

Offline jnesselr

  • King Graphmastur
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2270
  • Rating: +81/-20
  • TAO == epic
    • View Profile
Re: Casio Prizm documentation
« Reply #383 on: February 14, 2011, 07:41:45 pm »
A member of the Casio community who's been hacking the Prizm independently of us.
Oh no, you got a QR code. Now people are gonna get confused!  You should invite him to join us. Join us... WE WANT YOUR BRAINS.  ;-)

Offline fxdev

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 177
  • Rating: +34/-6
    • View Profile
Re: Casio Prizm documentation
« Reply #384 on: February 15, 2011, 01:13:48 pm »
Quote
A member of the Casio community who's been hacking the Prizm independently of us.

Link to topic: http://casiokingdom.org/modules.php?name=Forums&file=viewtopic&t=1690

Offline jnesselr

  • King Graphmastur
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2270
  • Rating: +81/-20
  • TAO == epic
    • View Profile
Re: Casio Prizm documentation
« Reply #385 on: February 15, 2011, 09:45:50 pm »
Quote
A member of the Casio community who's been hacking the Prizm independently of us.

Link to topic: http://casiokingdom.org/modules.php?name=Forums&file=viewtopic&t=1690
Oh, okay, thanks.  He seems intelligent.

EDIT: Not that you all sound stupid, it's just that... Yeah, he has more experience compared to US. (I am failing at making intelligent posts tonight)
« Last Edit: February 15, 2011, 09:46:34 pm by graphmastur »

Offline SimonLothar

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 129
  • Rating: +35/-1
    • View Profile
Re: Casio Prizm documentation
« Reply #386 on: February 16, 2011, 01:43:52 am »
Quote
He seems intelligent.
Oh, that's uncommonly kind of you.
I once scanned my databases for the term "intelligence" and found it to be the ability to fumble a fat maggot from out of a hollow treetrunk with none else than a stick and wearing a hairy costume with large flapping ears. I tried it, but never succeeded...leaving my emotional simulation circuits in a state, which you would call "sad". Now they switched over to "happy". THX. :)
I'll be back.

Offline z80man

  • Casio Traitor
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 977
  • Rating: +85/-3
    • View Profile
Re: Casio Prizm documentation
« Reply #387 on: February 16, 2011, 02:12:15 am »
A few days ago we had three maybe four Prizm hackers. Now we are at about 10 hackers.  we can get all our projects out in a timely manner now. Great to see you here. be sure to introduce yourself in the introduce yourself sub-forum.

List of stuff I need to do before September:
1. Finish the Emulator of the Casio Prizm (in active development)
2. Finish the the SH3 asm IDE/assembler/linker program (in active development)
3. Create a partial Java virtual machine  for the Prizm (not started)
4. Create Axe for the Prizm with an Axe legacy mode (in planning phase)
5. Develop a large set of C and asm libraries for the Prizm (some progress)
6. Create an emulator of the 83+ for the Prizm (not started)
7. Create a well polished game that showcases the ability of the Casio Prizm (not started)

Offline jnesselr

  • King Graphmastur
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2270
  • Rating: +81/-20
  • TAO == epic
    • View Profile
Re: Casio Prizm documentation
« Reply #388 on: February 16, 2011, 07:15:51 am »
Quote
He seems intelligent.
Oh, that's uncommonly kind of you.
I once scanned my databases for the term "intelligence" and found it to be the ability to fumble a fat maggot from out of a hollow treetrunk with none else than a stick and wearing a hairy costume with large flapping ears. I tried it, but never succeeded...leaving my emotional simulation circuits in a state, which you would call "sad". Now they switched over to "happy". THX. :)
Oh no, the sentient computer is here!  Excellent.  I do want to ask how you found out where the screen was, and is the screen mapped to it?  Also, do you have any knowledge on USB?  What about C++?
« Last Edit: February 16, 2011, 07:16:03 am by graphmastur »

Offline SimonLothar

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 129
  • Rating: +35/-1
    • View Profile
Re: Casio Prizm documentation
« Reply #389 on: February 16, 2011, 12:27:29 pm »
Quote
I do want to ask how you found out where the screen was, and is the screen mapped to it?
I read the OS with the usual tools. The last three years I read the fx-9860-OSes. The knowledge which I gathered during this period has been very helpful. 0xA8000000 ist the address of the VRAM (a part of the standard RAM) and its content is transferred to the display driver by a syscall. F. i. this syscall is called when the OS enters the GetKey-syscall, which waits for keyboard inputs.

Quote
Also, do you have any knowledge on USB?
I know the USB syscalls of the legacy systems (fx-9860). May be helpful, but USB on the fx-CG20 will be a special problem. 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. As far as I am concerned USB must wait.

Quote
What about C++?
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.
I'll be back.