Just a suggestion: When no reply were made after your post and it has been under 6 hours, use the edit/modify/quick modify button to update your post so you don't double or even triple post.

Quote from: apcalc on February 08, 2011, 07:44:36 pm

Quote from: Ashbad on February 08, 2011, 07:40:11 pm

Quote from: holmes221b on February 08, 2011, 07:28:48 pm

Quote from: apcalc on February 08, 2011, 07:24:06 pm

* apcalc threatens with some *unique* videos on the Nspire...

Hmm...porn on the Nspire? That would actually be interesting to see...

indeed

Well, it would be the perfect addition to the next ticalc.org CD!

And the fastest possible way to get those calcs banned from school.

I thought we were trying to convince teachers that calc programming is good.  

The importance with threads is that many parts of the Prizm run in parrellel(mainly the lcd, but also stuff like the serial port and clock) Otherwise the emulator is set up exactly like the SH3 core. First I already have a memory model set up that takes 32 bit physical adresses. Other core functionnalities are the registers are set up as global variables allowing them to be acseesed at all times. Also porting SH3 commnads will be easier to do because Reneas provided the C code equivalent for every command. They even suggested some good ideas that would make emulator coding much easier. One is that the registers are actually initialized as an array int R[16]. This makes it easier to then emulate instructions the code passed.

There are many other complicated features that can not be explained in just one post. Once I get farther on this project I will create its own thread and make a pdf documentation of the emulator.

I could code this is C++, but I will need to learn how C++ threads work first. Also I will need to learn to use a graphics library that works on all systems because currently all I know is Directx. Last is that non Windows users will have to compile the code themselves.

Great we could use more Prizm hackers. Feel free to browse the Prizm sub-forum to see what we have already hacked.

How can you lose in games where you cannot lose, though?

I meant, I like games where you cannot lose because in other win/lose games I often end up losing.

Edit: I think I overused the word lose

Interesting. I hope eventually your friend also gets more into calc stuff and joins the forums. This project seems interesting too. It's kinda like a game where you just wander around for fun and no way of winning and losing?

I like those kind of games because often I end up losing. 

Well I already figured out a memory model which a will give a brief description of. How it will work is when an instruction is passed for a memory location, the emulator then converts the physical adress into a virtual one which can be stored into a dynamic array. So in order of execution, a program on the Prizm passes a virtual address to the OS, which then converts that into a physical address, then the emulator converts that into a virtual adress, then the jre converts that into a different virtual address, and then converts that into a physical address. Wow this makes my head hurt. 

I have a feeling that pretty soon we will be capable of building a full Prizm emulator. Even though we haven't fully disassembled the OS yet and the ports are still unknown, an emulator can at least be started. The first thing that can be done is the SH3 emulation core. With this being already fully documented, emulating the instructions is possible and I was actually going to start writing the insructions soon too. This will be in Java for several reasons that I will explain later. Next thing to be emulated will have to be the memory. Now for Ti-83+ emulators you could just make a 64 kb array and call that memory (ignoring flash and ram pages at the moment). Now with a 32 bit proc this is a lot harder. So if anyone is good with writing memory management routines in java I could use some help. Then there is also the flash to be emulated which I believe could just be stored in a file and then accsessed from there. I'm not yet sure if the flash is set up in pages or if it just addresed similar to the ram.

In other hardware the keyboard shouldn't be that hard and the screen will be easy once we find where it is mapped to. usb could be hard to work with, but that shouldn't be nessecary in the initial version of the software. There is also the serial port, but it acts diffrently than the 83+ one because it has input and output buffers. The last hardware I can think of is the clock and that should not be hard to emulate either.

Now I want to go over some project details. Even though I'm mainly a C++ programmer, I wanted to do this in java, one because of portability. Two because my idea was to make each of the hardware devices its own thread so they can operate simultaneously. (this feature being very easy to implement in java) I also wanted to add full debugging software just like in wabbit. This project is also quite ambitious so I will need lots of help from everyone. Once I get started on this I will post updates and also send out help requests. For the past few weeks I have been very busy (especially because I have a job now), but I will have more free time in the near future. Lastly my current priority is to get that app signer out, to make Prizm programming much easier. It's just been I've just been very busy as I previously stated.

Black edition  I have never heard of this. Anyways make sure you get the screw out underneath the backup battery and then there are four clips holding the case together(two on each side). Use a knife or something and carefully pull apart the clips. It might take awile but eventually they will come off.

Once open be careful with the keyboard because the keys like to fall out and stuff and also you won't find a real z80, but instead TI's version one.