Omnimaga
Calculator Community => TI Calculators => ASM => Topic started by: Camdenmil on June 17, 2011, 12:08:28 am
-
I've noticed for a while that when I send 1C-1F to port 10 in calcsys, nothing happens. I tested this in an asm program and no blueness occurred. I also noticed that port 20 ignores bit 1. According to wikiti, port 20 has 4 settings and on a friends calc, sending 2 and 3 to port 20 acts like wikiti says it should. I have a ramless 84+SE and my lcd driver is 240 fps and it does support the mirring/flipping.
-
No blueness? No Nethams? D:
Never heard of it before!
On the back of the calculator, between warnings and the battery cover, there should be an engraved number. The advanced Asm programmers will be able to help/ask more questions.
-
I've noticed for a while that when I send 1C-1F to port 10 in calcsys, nothing happens. I tested this in an asm program and no blueness occurred. I also noticed that port 20 ignores bit 1. According to wikiti, port 20 has 4 settings and on a friends calc, sending 2 and 3 to port 20 acts like wikiti says it should. I have a ramless 84+SE and my lcd driver is 240 fps and it does support the mirring/flipping.
I think the port 20h issue is the OS's fault. thepenguin77 encountered that too.
-
Obviously, TI is using slightly different LCD driver models. As long as they're not using the super-slow ones, I don't think we should really care. There's little point to screwing around with the test mode anyway. Incidentally, the blue lines of death only seem to work on the TI-83+.
By the way, I thought that the maximum theoretical bandwidth for the LCD drivers was more like 120 FPS. Do the new ones require less delay?
-
If there is less delay, does that mean better grayscale (if programmed properly)?
-
That's a good question. The Desolate guy remarked to me that experimentation showed that the LCD driver only updated the screen at 60 FPS. I've been meaning to write a program for precisely checking this.
-
On my calculator, $1F is the only command that makes the blue screen of death occur. Just slightly different drivers.
The port 20h thing is caused by the OS like calc84 said. But actually it's caused by the OS executing hooks. I just looked at the code, and what the OS does, is when running the hooks, it sets the calculator in 6MHz mode. Then when the hook is done, it takes out the old port ($20) value and and's it with 1. That would be why it appears you can't set it to 3.
To prove my point. Turn your calculator off. Hold Left+Right and press on. Press clear. That just disabled all hooks. Now try it again in calcsys. You'll notice that you can now set 3.
And DrDnar. 120 FPS is the slowest the LCD drivers ever run. During my testing, I've seen K-Factor calculators hit 280 fps running >17MHz.
Edit:
The desolate guy? http://ourl.ca/9538/182589
-
Is there a place with the specs of each factory screen? (I guess it should belong on Wikiti or something.)
-
"The Desolate guy (http://www.ticalc.org/archives/files/fileinfo/348/34879.html)" is Patrick Prendergast, aka tr1p1ea. So, yes, the 60 FPS thing has been known since at least 2004.
-
Yeah, I know, who tr1p1ea is. I was just saying that I also found the same thing. The good news I guess would be that we both came up with the same conclusion :D He just did it long before I did.
-
Uninstalling hooks makes port 20 work. Too bad everyone can't experience the lcd burning experience of test mode. Oh well, yet another hardware variation.