Author Topic: Casio Prizm documentation  (Read 234989 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: Casio Prizm documentation
« Reply #330 on: February 01, 2011, 04:47:19 am »
Well, it depends on the type of code. The section of virtual memory i used for the CPU changer is designed to be addressed the same. The code used for writing to the LCD was supposed to write to physical memory and I forgot to take it out of virtual memory, so it tried to write to invalid addresses. That's what the TLB error means. I made a simple mistake and I simply haven't had the time to fix it.
∂²Ψ    -(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: Casio Prizm documentation
« Reply #331 on: February 01, 2011, 04:52:57 am »
Ah ok. I see now X.x. Good luck figuring out. X.x

Offline JosJuice

  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1344
  • Rating: +66/-14
    • View Profile
Re: Casio Prizm documentation
« Reply #332 on: February 01, 2011, 10:11:20 am »

These are some of the files that are placed in Temp by the OS installer. The eActivities aren't interesting, but OSupdateDLL.dll might be...

Offline jnesselr

  • King Graphmastur
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2270
  • Rating: +81/-20
  • TAO == epic
    • View Profile
Re: Casio Prizm documentation
« Reply #333 on: February 01, 2011, 05:29:45 pm »
Could you send the dll?

Offline z80man

  • Casio Traitor
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 977
  • Rating: +85/-3
    • View Profile
Re: Casio Prizm documentation
« Reply #334 on: February 02, 2011, 12:30:54 am »
At 6 megabytes OSupdateDLL.dll seems a little large. What about fxASPI.dll, that is around the same size predictions I had for the update.

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 #335 on: February 02, 2011, 12:45:19 am »
The OS is secured with an MD5 hash. That means that we're not going to be breaking it anytime in the near future. At least it's not as bad as the Nspire RSA code.
« Last Edit: February 02, 2011, 12:51:15 am by Qwerty.55 »
∂²Ψ    -(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 #336 on: February 02, 2011, 12:59:02 am »
The OS is secured with an MD5 hash. That means that we're not going to be breaking it anytime in the near future. At least it's not as bad as the Nspire RSA code.
I've been reading up on MD5 hash and sources say that a 128 bit key can be cracked in only a few seconds using a collision attack algorthim. Do you think this may be possible with the OS.

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 #337 on: February 02, 2011, 01:08:56 am »
I'm not sure a collision would help much. We need the signing keys, not the collision.


You're right. We just have to make sure whatever OS collides with the MD5 hash.
« Last Edit: February 02, 2011, 01:10:25 am by Qwerty.55 »
∂²Ψ    -(2m(V(x)-E)Ψ
---  = -------------
∂x²        ℏ²Ψ

Offline JosJuice

  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1344
  • Rating: +66/-14
    • View Profile
Re: Casio Prizm documentation
« Reply #338 on: February 02, 2011, 01:27:56 am »
The OS is secured with an MD5 hash. That means that we're not going to be breaking it anytime in the near future. At least it's not as bad as the Nspire RSA code.
So you've found the OS file? Which one is it?

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 #339 on: February 02, 2011, 01:31:40 am »
I haven't found any files period. All I've found is code that checks the MD5 hash.
∂²Ψ    -(2m(V(x)-E)Ψ
---  = -------------
∂x²        ℏ²Ψ

Offline JosJuice

  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1344
  • Rating: +66/-14
    • View Profile
Re: Casio Prizm documentation
« Reply #340 on: February 02, 2011, 01:33:13 am »
Oh, okay. You're disassembling the exe?

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 #341 on: February 02, 2011, 01:40:04 am »
Yes. That contains all of the requisite data to update the OS.
∂²Ψ    -(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 #342 on: February 02, 2011, 02:19:50 am »
At $86800 in the exe it looks like there is maybe some C/C++ code. It does hava a lot of windows commands in it. I don't know if this will be useful or not, but it might unveal something.

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 #343 on: February 02, 2011, 04:08:50 pm »
I'm personnally looking for the usb code. It has to talk to the device at some point.  Also, if someone who doesn't care about the bugs please download "simple usb logger", and log the OS transfer? Thanks!

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 #344 on: February 03, 2011, 12:42:22 am »
It sucks that it's encrypted. I hope you can manage to decrypt the OS without too much hassle. I hope no other encryption methods were used in it...