« previous next »
Pages: 1 2 3 [4] 5   Go Down

Author Topic: Prizm goals  (Read 25129 times)

0 Members and 2 Guests are viewing this topic.

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: Prizm goals
« Reply #45 on: April 13, 2011, 05:31:25 pm »
DJ, the max Prizm clock speed was based on the processor core being the normal SH3 7705 core used in previous calcs. We have evidence to suggest that it's a SH4A 7780/7781 core, which can handle much higher clock speeds (200 MHz). It's really a matter of how high the frequency multiplier will go if that's indeed the case.
Logged
∂²Ψ    -(2m(V(x)-E)Ψ
---  = -------------
∂x²        ℏ²Ψ

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: Prizm goals
« Reply #46 on: April 13, 2011, 05:33:50 pm »
Really? I didn't know that. It would be nice if it could.

By the way is it confirmed that it's the same processor as in the FX-9860G?
Logged

Offline z80man

  • Casio Traitor
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 977
  • Rating: +85/-3
    • View Profile
Re: Prizm goals
« Reply #47 on: April 14, 2011, 12:56:18 am »
The current processor seems to have been developed exclusively for Casio and is most likely a SH4A without the fpu and many of the peripherals. Also the total amount of ram is 2 MB and for the most part is free. Archive totals as 32 MB, but the OS currently claims 16 MB of that. Because the OS is only 6 MB long, there is the possibility of expanding more archive space in the future. Based off what I have found we can only overclock the proc in software so far until we reach a limit. After that the pll 2 circuit will have to change values, which is set via hardware. My guess is that maybe the careful use of a pencil could change that multiplier.
Logged

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 Munchor

  • LV13 Extreme Addict (Next: 9001)
  • *************
  • Posts: 6199
  • Rating: +295/-121
  • Code Recycler
    • View Profile
Re: Prizm goals
« Reply #48 on: April 14, 2011, 06:09:03 am »
So, basically, what we have is a max of 200Mhz? And in the 84+SE the max is 15Mhz? Freaking fast!
Logged

Offline z80man

  • Casio Traitor
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 977
  • Rating: +85/-3
    • View Profile
Re: Prizm goals
« Reply #49 on: April 14, 2011, 11:24:09 am »
Quote from: Scout on April 14, 2011, 06:09:03 am
So, basically, what we have is a max of 200Mhz? And in the 84+SE the max is 15Mhz? Freaking fast!
don't forget clock cycles. The average z80 instruction is about 7 cycles while most Super H instructions are only 1.
Logged

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: Prizm goals
« Reply #50 on: April 14, 2011, 11:28:28 am »
The worst exception is division, because that can take something like 96 cycles to do.
Logged
∂²Ψ    -(2m(V(x)-E)Ψ
---  = -------------
∂x²        ℏ²Ψ

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: Prizm goals
« Reply #51 on: April 17, 2011, 08:30:29 pm »
Does this means that certain things might actually be slower than on a 84+?
Logged

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: Prizm goals
« Reply #52 on: April 17, 2011, 08:32:15 pm »
It's probably faster than on the 84+, because the worst case is the 32 bit division I was referring to, which would be even slower with a z80. Also, the processor runs quite a bit faster than the 84+, so 96 cycles isn't as bad as it sounds.
Logged
∂²Ψ    -(2m(V(x)-E)Ψ
---  = -------------
∂x²        ℏ²Ψ

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: Prizm goals
« Reply #53 on: April 17, 2011, 09:00:18 pm »
Ah ok good to hear. I was worried that we got our hopes up too much for hardcore gaming X.x
Logged

Offline z80man

  • Casio Traitor
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 977
  • Rating: +85/-3
    • View Profile
Re: Prizm goals
« Reply #54 on: April 18, 2011, 12:22:46 am »
Quote from: Qwerty.55 on April 14, 2011, 11:28:28 am
The worst exception is division, because that can take something like 96 cycles to do.
Well in that case you need to be careful. Of course speed optimizations can be done by rolling out the for loop. But even better is try to avoid division it in the first place. The best thing to do is bit shifts for the cases of when you are dividing by powers of 2. And the SH4 is just brilliant at bit shifts ;D
Logged

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 Eiyeron

  • Urist McEiyolobster
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1430
  • Rating: +130/-10
  • (-_(//));
    • View Profile
    • Rétro-Actif : Rétro/Prog/Blog
Re: Prizm goals
« Reply #55 on: October 08, 2011, 08:32:26 am »
Ey! What just axe for Prizm, there is Fx-9860GII too! :p
Logged

Offline z80man

  • Casio Traitor
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 977
  • Rating: +85/-3
    • View Profile
Re: Prizm goals
« Reply #56 on: October 11, 2011, 12:44:12 am »
Quote from: Eiyeron on October 08, 2011, 08:32:26 am
Ey! What just axe for Prizm, there is Fx-9860GII too! :p
Well the problem is that most Casio developers are either Prizm or 9860g exclusive. Added to that is the difficulty of porting the compiler over as both calculators have extensive technical differences that would need to be addressed. I for one do not own a 9860g and have no intention of porting any axe like language to it as that is not my area of development.
Logged

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 Eiyeron

  • Urist McEiyolobster
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1430
  • Rating: +130/-10
  • (-_(//));
    • View Profile
    • Rétro-Actif : Rétro/Prog/Blog
Re: Prizm goals
« Reply #57 on: October 12, 2011, 09:54:56 am »
So, do you have already tested some overclocking?
Logged

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: Prizm goals
« Reply #58 on: October 26, 2011, 04:32:41 am »
From what I remember, they could overclock the calc fine, but the problem is that when we do so, it gets reset, so it's pretty much useless until they figure out how to get around that.
Logged

Offline Eiyeron

  • Urist McEiyolobster
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1430
  • Rating: +130/-10
  • (-_(//));
    • View Profile
    • Rétro-Actif : Rétro/Prog/Blog
Re: Prizm goals
« Reply #59 on: October 26, 2011, 06:29:47 am »
Do you know why accesong the vram is so slow? A friend tried to make his own PutDD, and that was very slow (about 25 fps with, and 33 wihtout)
Logged
Pages: 1 2 3 [4] 5   Go Up
« previous next »