Author Topic: Casio Prizm documentation  (Read 235601 times)

0 Members and 2 Guests are viewing this topic.

Offline SimonLothar

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 129
  • Rating: +35/-1
    • View Profile
Re: Casio Prizm documentation
« Reply #465 on: March 11, 2011, 06:44:47 pm »
Direct display access

syscall 0x026B (void Bdisp_SetPoint_DD( int x, int y, unsigned short color )) writes a point directly to the display.

BTW: syscall 0x025F Bdisp_PutDisp_DD() transfers the data from VRAM to display-RAM via DMA. The DMAC-address for this operation is 0xFE008020 (channel 0). The address of DMAOR is 0xFE008060. The DMAC functions seem to be similar, if not identical compared to those of the 7705's DMAC (0xA4000020) or the 7720's DMAC (0xA4010020). The base address of the displaydriver is 0xB4000000, which does not mean, that this address can be simply used to write directly to the display! The special (undocumented) processor instruction 0x00AB seems to be kind of ping, after something has been written to a DD-related register, perhaps to sync the MPU/DD-interaction. The correspnding DMA-source register (DMARSx) is difficult to identify. At least 0xA4050130 and 0xA405013C are involved.
Every single register-address involved in accessing the display does not occur in the 7705- or 7720-lists.

I'll be back.

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 #466 on: March 11, 2011, 06:50:38 pm »
You mean that they put hardware support in for the screen?  O.O

Seems like overkill to me.
∂²Ψ    -(2m(V(x)-E)Ψ
---  = -------------
∂x²        ℏ²Ψ

Offline SimonLothar

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 129
  • Rating: +35/-1
    • View Profile
Re: Casio Prizm documentation
« Reply #467 on: March 12, 2011, 12:57:40 am »
You mean that they put hardware support in for the screen?  O.O
Seems like overkill to me.
The amount of data to transfer when copying the complete VRAM to the display is 162 times greater than on a fx-9860. DMA seems to be reasonable.
I'll be back.

Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55943
  • Rating: +3154/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • Dream of Omnimaga Music
Re: Casio Prizm documentation
« Reply #468 on: March 12, 2011, 04:12:10 am »
...but are add-ins made by the community still always appearing at the same place all the time in the menu?
No. I just loaded a second copy of insight.g3a to my Prizm, using the filename insigh2.g3a and it appeared as additional item in the menu. Different filenames give different menu items, as it is with the legacy systems.
Ah ok, good to hear. :D
You mean that they put hardware support in for the screen?  O.O

Seems like overkill to me.
What is hardware support in this context? I am a bit lost there. Is it some sort of hardware acceleration? I'M not tech-savy about that stuff, so sorry if my question sounds stupid. ???
« Last Edit: March 12, 2011, 04:12:29 am by DJ_O »

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 #469 on: March 12, 2011, 04:53:55 am »
You mean that they put hardware support in for the screen?  O.O
Seems like overkill to me.
The amount of data to transfer when copying the complete VRAM to the display is 162 times greater than on a fx-9860. DMA seems to be reasonable.

Had to look up the acronym :P

Yeah, it seems like a good idea, given how large the screen buffer is. How do you think the cache works with it, though?

@DJ, in this context it means that there's special hardware for directly transferring memory mapped RAM that doesn't rely on the processor. It's faster than doing it with something like IonFastCopy.
« Last Edit: March 12, 2011, 04:55:53 am by Qwerty.55 »
∂²Ψ    -(2m(V(x)-E)Ψ
---  = -------------
∂x²        ℏ²Ψ

Offline SimonLothar

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 129
  • Rating: +35/-1
    • View Profile
Re: Casio Prizm documentation
« Reply #470 on: March 12, 2011, 05:29:23 am »
How do you think the cache works with it, though?
I think the cache has to be flushed before DMA (direct memory access) occurs. Perhaps it is done automatically by the DMA request or by setting/toggling certain bits of the registers involved. As these registers are undocumented, this is not easy to verify (at least for me).

EDIT: I forgot to mention. VRAM usually is accessed using base address 0xA8000000, which lies within area P2, a non-cacheable memory range. Caching could be a problem, if you access VRAM using base-address 0x88000000.
« Last Edit: March 14, 2011, 08:10:42 am by SimonLothar »
I'll be back.

Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55943
  • Rating: +3154/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • Dream of Omnimaga Music
Re: Casio Prizm documentation
« Reply #471 on: March 13, 2011, 12:49:49 am »
@DJ, in this context it means that there's special hardware for directly transferring memory mapped RAM that doesn't rely on the processor. It's faster than doing it with something like IonFastCopy.
Ah cool, thanks for clarifying. :D

Offline fxdev

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 177
  • Rating: +34/-6
    • View Profile
Re: Casio Prizm documentation
« Reply #472 on: March 18, 2011, 02:29:41 pm »
The monochrome picture at 0x290 and those names starting at 0x0170 are used for eActivity strips.
Just in case, this is not known yet.
« Last Edit: March 18, 2011, 03:01:19 pm by cfxm »

Offline JosJuice

  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1344
  • Rating: +66/-14
    • View Profile
Re: Casio Prizm documentation
« Reply #473 on: March 18, 2011, 03:06:04 pm »
Interesting. What does that mean, and how do eActivities work? I don't have a Prizm yet, so I'm clueless about some of the math/education related stuff.

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 #474 on: March 18, 2011, 03:37:57 pm »
The monochrome picture at 0x290 and those names starting at 0x0170 are used for eActivity strips.


As well as the language packs, right?
∂²Ψ    -(2m(V(x)-E)Ψ
---  = -------------
∂x²        ℏ²Ψ

Offline z80man

  • Casio Traitor
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 977
  • Rating: +85/-3
    • View Profile
Re: Casio Prizm documentation
« Reply #475 on: March 18, 2011, 08:45:03 pm »
eActivity is a file format for the Prizm. Casio thinks of it as an education tool, but I see it as a potential pdf like viewer. It can hold customizable text, pictures, and a few gui elements. Maybe I will make an editor some time later.

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 fxdev

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 177
  • Rating: +34/-6
    • View Profile
Re: Casio Prizm documentation
« Reply #476 on: March 18, 2011, 09:10:53 pm »
As well as the language packs, right?
I don't understand your question... :)
Language add-ins have nothing to do with eActivity strips nor any .g3a header. They extend message and menu language only.
« Last Edit: March 18, 2011, 09:16:18 pm by cfxm »

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 #477 on: March 18, 2011, 09:28:00 pm »
The add-in names are used to determine the language title to be displayed, right? That would imply that if the language changes, then the offset that the name is read from is changed correspondingly.
∂²Ψ    -(2m(V(x)-E)Ψ
---  = -------------
∂x²        ℏ²Ψ

Offline fxdev

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 177
  • Rating: +34/-6
    • View Profile
Re: Casio Prizm documentation
« Reply #478 on: March 18, 2011, 09:46:05 pm »
Yep.

Offline JosJuice

  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1344
  • Rating: +66/-14
    • View Profile
Re: Casio Prizm documentation
« Reply #479 on: March 19, 2011, 04:24:15 am »
eActivity is a file format for the Prizm. Casio thinks of it as an education tool, but I see it as a potential pdf like viewer. It can hold customizable text, pictures, and a few gui elements. Maybe I will make an editor some time later.
Okay. In what way are add-ins and eActivities related? Can a "link" to an add-in be displayed in an eActivity, with the monochrome icon being displayed?