Omnimaga

Calculator Community => TI Calculators => ASM => Topic started by: Jerros on August 16, 2010, 10:51:10 am

Title: How do you know when your App is getting too big for 1 page?
Post by: Jerros on August 16, 2010, 10:51:10 am
So I've been working on an App, making it larger each day, but now I get the feeling random bugs pop up out of nowhere.
It's kind of similar to what happened when my programm breached the 8kB limit and had to be turned into an App.
Thus the next step would be to add another page to the App, although I dont know wether that's needed or not.
Any way to check that?
Title: Re: How do you know when your App is getting too big for 1 page?
Post by: thepenguin77 on August 16, 2010, 11:14:27 am
It's when it gets over 16,384 bytes that it requires two pages. There are two ways to check for this.

1. compile your app as a program and check it's size on the computer. This will give you a rough estimate of how bit it is.

2. Download Omnicalc (http://www.ticalc.org/archives/files/fileinfo/226/22626.html) run it and press 6, 1, 3. Then find your app, when you have it selected, press Alpha H. Your are now looking at your app as it is in calculator memory. Alpha G is goto, so by using that, you can look for the end of your file. You'll know you found the end because it will go from random bytes to all FF's. The max size for a one page app is $4000 bytes, so if the end is around $7800, you'll be needing two pages soon.
Title: Re: How do you know when your App is getting too big for 1 page?
Post by: souvik1997 on August 16, 2010, 11:22:33 am
It's when it gets over 16,384 bytes that it requires two pages. There are two ways to check for this.

1. compile your app as a program and check it's size on the computer. This will give you a rough estimate of how bit it is.

2. Download Omnicalc (http://www.ticalc.org/archives/files/fileinfo/226/22626.html) run it and press 6, 1, 3. Then find your app, when you have it selected, press Alpha H. Your are now looking at your app as it is in calculator memory. Alpha G is goto, so by using that, you can look for the end of your file. You'll know you found the end because it will go from random bytes to all FF's. The max size for a one page app is $4000 bytes, so if the end is around $7800, you'll be needing two pages soon.

I think you meant Calcsys, not Omnicalc.

Title: Re: How do you know when your App is getting too big for 1 page?
Post by: Happybobjr on August 16, 2010, 11:28:10 am
its like 16,0000,  a little bigger than that actually.

go to your memory on the calc.  look at the amount of memory your smallest app takes. if it is about 16000 then thats it.  now subtract about 150 from it, just because of ummm, well i dont remember why
Title: Re: How do you know when your App is getting too big for 1 page?
Post by: Quigibo on August 16, 2010, 01:51:24 pm
You don't need to check because I doubt your app signer will sign an app that's too large.  But I use this:

Code: [Select]
#define VALIDATE(last) #if ($+0 > (last)) \ .echo "ERROR: MEMORY: " \ .echo ($+0 - (last)) \ .echo " bytes too large\n" \ ld q,q \ #endif
So then I just do VALIDATE($7FBD) at the end of the program.  The lower size is to give enough room for the signature.  Its great to use for any self modifying code that you copy to ram to make sure you don't overflow the buffer.  Spasm has many of these macros built in as well.  The ld q,q is just there to generate an error by the way.
Title: Re: How do you know when your App is getting too big for 1 page?
Post by: thepenguin77 on August 16, 2010, 08:35:33 pm
It's when it gets over 16,384 bytes that it requires two pages. There are two ways to check for this.

1. compile your app as a program and check it's size on the computer. This will give you a rough estimate of how bit it is.

2. Download Omnicalc (http://www.ticalc.org/archives/files/fileinfo/226/22626.html) run it and press 6, 1, 3. Then find your app, when you have it selected, press Alpha H. Your are now looking at your app as it is in calculator memory. Alpha G is goto, so by using that, you can look for the end of your file. You'll know you found the end because it will go from random bytes to all FF's. The max size for a one page app is $4000 bytes, so if the end is around $7800, you'll be needing two pages soon.
I think you meant Calcsys, not Omnicalc.

Good thing you caught that, he would have been really confused. Calcsys (http://www.ticalc.org/archives/files/fileinfo/97/9781.html) is what you're after.

Calcsys Omnicalc, sp pc, they're all the same thing.  :)




Title: Re: How do you know when your App is getting too big for 1 page?
Post by: Jerros on August 17, 2010, 04:17:06 am
Okay, I'll check it with your tips, thanks.
The programm is currently ~6000 lines, but I guess that what Quigibo said is right, my compiler will probably error if I'm exeeding the limit.
Thanks all.
Title: Re: How do you know when your App is getting too big for 1 page?
Post by: ACagliano on August 17, 2010, 07:21:30 am
Can Axe compile to a second page, or are we limited to 16,000 bytes?
Title: Re: How do you know when your App is getting too big for 1 page?
Post by: DJ Omnimaga on August 17, 2010, 07:51:06 am
Well, he's using ASM, not Axe, so Axe is out of the question here.
Title: Re: How do you know when your App is getting too big for 1 page?
Post by: Jerros on August 17, 2010, 08:49:47 am
News-flash:
My compiler just said my header is "invalid". (while I havent touched the header in months)
I guess I just hit the limit.
I don't hope adding another page will be alot of work though...