10 replies to this topic

[helder7]

Cross-posted from casio-scene.

For many users, the launch of a new ClassPad without color screen was a disillusion. I am sure that a ClassPad with Color Screen would be a "Nspire Cx Cas Killer".

However I was analyzing the Classpad 330 Plus manuals. I come here to refer to changes.



Hardware changes:
Sh4 processor


In the Initial Configuration
As in other models, now appears a window to choose the type of batteries:



Projector Connection
Now is possible use Classpad with Casio Compatible Projectors like Prizm!



Computer Connection
The calculator is a usb disk, like prizm. You no longer need to use software like FA-CP1 to put file on calc. Maybe the restriction on the transmission of unknown extension files to the calculator is removed.


Support 3 folder levels.

It uses memory files for programs, etc... with extensions .vcp and .xcp

Add-ins
Old add-ins doesnt work in new classpad, because the new classpad use a Sh4 processor (like power grapic 2 models and prizm).
There are also a new add-in format (.c1a). Maybe casio doesnt release any SDK.



This news does not surprise me. I'm waiting for the Color Classpad! I still prefer my classpad 330, because there are many add-ins developed for it and I have doubts about the success of this new model!

Edited by helder7, 02 July 2012 - 03:28 PM.

[flyingfisch]

This new classpad is a disappointment, i think. While there are some good points (acts like a USB drive, etc.), i think they are overshadowed by the fact that it has no addins for it yet, and does not have an SDK.

I think casio is going to convert all their calcs to the SH-4 processor. So far we have SH-4 9860's, 9750's, and of course, the prizm.


On another note, how hard will it be to make 3rd party SDKs? Would it be possible to port the old addins/emulate the old processor?

[MicroPro]

Thanks helder7, actually I've already posted that information here: http://community.cas...sspad-330-plus/

Anyway changes to the processor are inevitable if Casio wants to make it more powerful.

As for the SDK, I'm personally optimistic that Casio releases it. If not, making a third party sdk will require disassembling the OS or add-ins. Do you think it's hard?

[flyingfisch]

I don't necessarily think it will be hard, just its like as if casio made a whole new calc.... we have no programs for it. may be confusing for new users.

[MicroPro]

Hehe You know how Simon Lothar and others discovered all the syscalls for fx, yeah?

And then we know nothing about hardware, address space, etc etc.

[flyingfisch]

How did he figure out the syscalls? Trial and error?

[helder7]

On another note, how hard will it be to make 3rd party SDKs? Would it be possible to port the old addins/emulate the old processor?

Emulate is hard. Port add-in (without grayscales) is easy if the input methods, etc is the same... But more than 95% of the old classpad add-ins isn't open source...

Hehe You know how Simon Lothar and others discovered all the syscalls for fx, yeah?

And then we know nothing about hardware, address space, etc etc.

it's very hard...i dont know... inexperiente users can permanently brick calculator testing/finding syscalls...
also is needly test the syscalls in some calculators os models, (and calculators with different hardware)

[Forty-Two]

I was inder the impression that, unless you messed with the boot code that recieves an OS, you can't brick a calc. Erase information? yes. Brick? No.

[helder7]

SimonLothar quote (posted here)

// !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
// NEVER try undocumented syscall numbers randomly!
// mostly the calc will do nothing or hang, if the parameters are not chosen correctly.
// but someday you will call the sector erase syscall, which will kill your calc permanently!
// !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[Forty-Two]

So don't write to the boot sector, and you'll be fine.

[MicroPro]

Yes, you'll be fine for another 10 years to sit and discover the next syscalls...

The ClassPad has its own object oriented OS with standard widgets that are usable through the current SDK. Moreover it's a touch device and its user experience is far beyond displaying texts and graphics and then wait for a key press.

Actually, an entire new hardware+i/o+memory+gui framework must be written if there isn't a sdk.