Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - ralphdspam

Pages: 1 [2] 3 4 ... 63
ASM / Re: Sending Commands Over Link Cable
« on: March 24, 2013, 08:39:23 pm »
This might be what you were looking for. It took a while to remember where I had seen that info before, but I remember thinking it sounded rather snazzy.
Thank you, Xeda112358!  That's exactly what I was looking for.  :D

How would I send the program using the "Silent Linking" mentioned in the documentation?  Would I use something like SendRAMVarData?

ASM / Re: Sending Commands Over Link Cable
« on: March 24, 2013, 05:31:02 pm »
If I personally were doing this, I would probably just write my own linking routines using port 0.

However, if you go on wikiTI and go to the bcall section, almost anything that starts with "get" or "send" is what you're looking for. Two that come to mind are Get4Bytes and Send4Bytes. (Though, just looking at them I don't know how to use them).
Thank you.  That's not exactly what I want to do, though.  I want to send either asm code or basic tokens to be executed from the home screen (without a receiver program.).

Would it be possible to do by emulating the TI Keyboard?

ASM / Sending Commands Over Link Cable
« on: March 24, 2013, 03:06:56 pm »
Hi, everyone.

I heard it was possible to send commands from one calculator to another over the link port.  How would I go about doing that.

Is there any documentation about this?

Thank you!  :)

Also I've compared 3 vs 4 levels and 3 looks clean when scrolling while 4 looks really blurry. Maybe it's because I can't calibrate it correctly. ???
What you are seing is most likely an artifact of the grayscale mask.  How fast are you scrolling in relationship to the interrupts?  Have you tried scrolling at faster or slower rates?

There is almost absolutely no chance that the interrupt occurs between erase and draw ;)

You could also temporarily disable interrupts before the erase and enable them after the draw.  That way, you will never display a half-drawn screen.

EDIT: fixed quote formatting

How would you go about allowing moving objects on the screen with the interrupt running?  Would you have to somehow sync the refresh rate with the amount of frames? (Sorry if I worded that incorrectly)
You don't necessarily have to sync with the interrupts, but it would be good practice to use it to keep a constant framerate.  
The Stop command halts the CPU until an interrupt occurs.  Remember that a frame is not drawn every interrupt in this case.  You could call a piece of code each time the screen is drawn, but you have to keep your code short to avoid interrupting on itself.  Instead, you can set a variable each time the screen is drawn, then have a piece of main code that waits for the variable to be reset.  

I wrote the following code to have more precision in screen drawing.  The 8.16 fixed point number allows the screen display rate to alternate between whole numbers.  While you will be able to make the screen better, it will still not be as clean as the faster crystal timer interrupts.

Code: [Select]
:Fix 0
:Fix 5
:While 1
:If getKey(4)
:If T>(T+256→T)
:If getKey(3)
:If T=0
:If getKey(1)
:If T<(T-256→T)
:If getKey(2)
:Pause 100
:EndIf getKey(15)
:Fix 4
:Lbl DG
:If G=0
:If H<(H+T→H)

EDIT: Wait... This code crashes in Wabbit.  It works fine on my calculator, though.

Does Axe still draw the screen twice on the grayscale routine?  If so, that might give you sub-optimal results.

Casio Calculators / I need help wit the Prizm. I'm completely lost.
« on: March 20, 2013, 07:12:23 pm »
Hi, everyone.

I'm pretty confused about programming the Casio Prizm.  

I successfully compiled the Hello World test program, but I can't really do more than that.  I'm pretty much a noob at pointers in C.  

How exactly do I plot a pixel to the screen?  I know that vram is at 0xA8000000.  How do I make a pointer to it and copy a color
What is the format of the 16-bit colors?

Thank you so much for helping me.  :)

EDIT: Alright.  I managed to plot pixels on the screen.  Is there a way of disabling the annoying border?

News / Re: Overclocking the TI-83+SE / TI-84+/SE Family
« on: March 20, 2013, 12:03:22 am »
What an amazing development for the calculator community!  Thank you, Kerm and DrDnar!

Much soldering and trial-and-error later, I was able to get the calculator running stably up to 22.4 MHz. Any faster and memory reads and LCD writes get unpredictable. Although ports $2E and $2F can be used to let the calculator safely run at speeds up to an estimated 28 MHz, the effective CPU speeds are actually lower due to the added delays.
What exactly do you mean by memory reads?  Just flash?  I was wondering if you could make mode 3 the fastest possible to execute from ram and mode 2 the fastest possible for flash reads and port IO.

These look really neat!  Someone should really make a game based on the capillary action...

Site Feedback and Questions / Re: Omnimaga YouTube channel (OmnimagaTV)
« on: November 19, 2012, 12:59:12 am »
We should also create a playlist of already existing calculator videos, so others can easily find more programmers/enthusiasts.

May I help in some fashion?

General Calculator Help / Re: Wabbitemu Reaction to Keypresses
« on: November 18, 2012, 03:57:21 pm »
Sorry that I have no suggestions, but I have experienced this as well.

News / Re: A new z80 calc... in color?
« on: November 11, 2012, 10:24:45 pm »
I wonder if they'll use the 16-bit I/O port addresses (with undocumented opcode behavior) to implement the color screen.  Hopefully their ASIC provides full backwards compatibility for ports $10 and $11.

News / Re: The story behind the TI-84+ C discovery
« on: November 10, 2012, 01:05:33 pm »
It's very interesting to see the way news like this trickles down and who gets the credit.

Site Feedback and Questions / Re: Omnimaga saving act
« on: November 10, 2012, 01:02:20 pm »
One option is to make a new popular calculator game, the next nDoom.
Unfortunately with the increased popularity, we will attract many trolls.

Another approach is to try to bring in hardware enthusiasts from the maker movement.  We might try to encourage modding or creating devices for the link port.  (I don't know how well that would go with the standardized test folk.)

Pages: 1 [2] 3 4 ... 63