Author Topic: GlassOS - Lithp Ith Happening (Read 35445 times)

AHelper · « **Reply #60 on:** October 25, 2011, 10:40:50 pm »

Well, I have been working on a greyscale function, but I need help... I am getting very odd images from this function:

http://fpaste.org/aHAj/

on-calc, the screen gets corrupted when first drawn, so $:-\$ . On the PC (WabbitEmu), the LCD is set, but what is displayed is wrong. I will post a screenie eventually...

Freyaday · « **Reply #61 on:** October 25, 2011, 11:44:58 pm »

Quote from: AHelper on October 25, 2011, 10:40:50 pm

Well, I have been working on a greyscale function, but I need help... I am getting very odd images from this function:

http://fpaste.org/aHAj/

on-calc, the screen gets corrupted when first drawn, so $:-\$ . On the PC (WabbitEmu), the LCD is set, but what is displayed is wrong. I will post a screenie eventually...

The screen is reaaaly crappy, and you have to wait 10 microseconds between updates, otherwise it displays garbage. Hope that helps! :O

DJ Omnimaga · « **Reply #62 on:** October 25, 2011, 11:53:20 pm »

Yeah from what I remember, the LCD delay needs to not be too quick. I don't remember if it's very different between calc hardware revisions, though.

AHelper · « **Reply #63 on:** October 25, 2011, 11:54:05 pm »

I use port 0x10 bit 7 to see when I can write to it... and I do. I revised the posted code and the same thing happens. Something really bad is going on with it... I will take a picture of it later tomorrow

AHelper · « **Reply #64 on:** October 26, 2011, 05:13:22 pm »

So, I have a screenie of what the calc and emulator do...

There is no RAM corruption at all. I have yet to step through the code

Also, the wavy lines should all be diagonal in one direction, not waving back and forth.

AHelper · « **Reply #65 on:** October 26, 2011, 09:45:37 pm »

Thanks to Runer112 at cemetech for pointing this out: (oops @credit)

Turns out that I didn't set the column back to 0... and the corruption was the launcher screen.

Greyscale works perfectly now! Here it is:

AHelper · « **Reply #66 on:** October 30, 2011, 09:32:15 pm »

Well, I have gotten the greyscale lib working and can be accessed easily. Things to use:

Code: [Select]

// FUNCTIONS
void grey_on(void); // Turns on greyscale
void grey_off(void); // Turns off greyscale
// VARIABLES
unsigned char greybuf[2]; // 0 - light, 1 - dark

Doing lcd_buffer = greybuf[0] (or [1]) will change the selected layer and can be drawn to it using gfx_* and ion_* functions. With that said, glassKILL was hacked into using greyscale (which I wanted to do before but never got around to it) here it is:

I already know it is slow to draw because I draw the background checkers like an idiot. I need a function to do it instead of a giant vertical sprite of checkers, then drawing it across..... >.<

Other than that, the greyscale ISR and ion_* functions are the only functions in the program in asm - the rest are in C.

Upcoming changes will be a better title screen, a highscore tracker, fixed icons (slow bot is hard to see when on white, garbage is garbage), and non-flickering checkerboard. Maybe a menu for a help and about page.

AHelper · « **Reply #67 on:** November 01, 2011, 03:09:59 pm »

The background drawing is fast now and draws in under 1 frame ^_^ However, the tasking system is bugged and isn't quitting programs properly and task switching sometimes causes violations... :-(

LincolnB · « **Reply #68 on:** November 04, 2011, 10:38:50 am »

Quote from: AHelper on October 26, 2011, 09:45:37 pm

Thanks to Runer112 at cemetech for pointing this out: (oops @credit)

Turns out that I didn't set the column back to 0... and the corruption was the launcher screen.

Greyscale works perfectly now! Here it is:

This looks like it some SERIOUS potential for being the best graphics I've ever seen on a calculator. You can seriously go awesome places with stuff like that, like putting it in menus and good stuff. When I start getting into programming calcs from computers (not everything on calc like it is now for me) I'm going to start writing programs for this OS

Freyaday · « **Reply #69 on:** November 04, 2011, 06:24:52 pm »

Is Dualbooting even a remote possibility?

willrandship · « **Reply #70 on:** November 05, 2011, 01:13:38 am »

With TI-OS? I got the idea from KnightOS's devving that it requires quite a bit of work, which I haven't seen happen (in the dual-booting scene) in glassOS. I could be very wrong on both counts but I haven't heard anything about them, and besides, I would happily switch given the fact that GlassOS has its own CAS!

AHelper · « **Reply #71 on:** November 05, 2011, 01:52:00 pm »

Quote from: buttsfredkin on November 04, 2011, 10:38:50 am

Quote from: AHelper on October 26, 2011, 09:45:37 pm
Thanks to Runer112 at cemetech for pointing this out: (oops @credit)

Turns out that I didn't set the column back to 0... and the corruption was the launcher screen.

Greyscale works perfectly now! Here it is:

This looks like it some SERIOUS potential for being the best graphics I've ever seen on a calculator. You can seriously go awesome places with stuff like that, like putting it in menus and good stuff. When I start getting into programming calcs from computers (not everything on calc like it is now for me) I'm going to start writing programs for this OS

"Technically", you can start writing programs the same that that i write them. The catch is that you must write programs in the OS that will be included in the .8xu as the USB drivers are lacking my attention. But the greyscale lib will be getting more work done when the OS undergoes a large change... which will not be fun to do :-S

Quote from: willrandship on November 05, 2011, 01:13:38 am

With TI-OS? I got the idea from KnightOS's devving that it requires quite a bit of work, which I haven't seen happen (in the dual-booting scene) in glassOS. I could be very wrong on both counts but I haven't heard anything about them, and besides, I would happily switch given the fact that GlassOS has its own CAS!

I talked with SirC about dual booting a while back. it seems possible, but TIOS must be modified to not touch certain sectors from reading, writing and GC deletion. We both have different ideas about the boot manager, but both will work. I don't have any current plans to add one right now, but maybe in the future...

About gCAS2, it still needs much more work right now, and it has a large hatred of SDCC. So far, graphing works, but because it uses floats, it is slow and has math issues. My plan is to find a 32-bit double library (fixed point math) that can compile and run and use that for gCAS. Floats right now work, but precision is lost.

willrandship · « **Reply #72 on:** November 05, 2011, 06:25:20 pm »

Well, for graphing you don't need gigantic floats, especially with the resolution we deal with.

Also, it might be a good idea to support sci. notation in the numbers: That should allow for deep zooms without massive floats.

LincolnB · « **Reply #73 on:** November 05, 2011, 09:50:36 pm »

ooh, good luck with USB support.

AHelper · « **Reply #74 on:** November 05, 2011, 11:21:40 pm »

The USB stack works, the file transfer protocol is there, but not coded yet. Besides that, the USB is stable (or was, untested after many changes) and uses libusb1 on linux.

Author Topic: GlassOS - Lithp Ith Happening (Read 35445 times)

AHelper

Re: GlassOS

Freyaday

Re: GlassOS

DJ Omnimaga

Re: GlassOS

AHelper

Re: GlassOS

AHelper

Re: GlassOS

AHelper

Re: GlassOS

AHelper

Re: GlassOS

AHelper

Re: GlassOS

LincolnB

Re: GlassOS

Freyaday

Re: GlassOS

willrandship

Re: GlassOS

AHelper

Re: GlassOS

willrandship

Re: GlassOS

LincolnB

Re: GlassOS

AHelper

Re: GlassOS