Ok, here's the deal:  Your application header is fine.  Since you have a knowledge of ASM, I'll get into a little bit of technical talk, but you can always ask questions if you are confused.

Even though your application is run directly from flash ROM, you can only have access to one application page at a time.  As was said eariler, you need to switch pages to access them.  If you are running a 2-page application, you cannot run page 1 (the second page) until you switch to it from page 0.

Now, your calculator does all this switching for you, but you need to tell the calculator which page to jump to, and WHERE on the page to jump to.  You need what's called a "branch table."  This is where you put all functions (with labels, variables, etc) that must be called from another page.

After your application header, use a "jp" statement to jump to where your program begins. 

Now, you start typing in data for labels that are on your second page.  If there is a label on your second page that your first page needs to call, you need to place it in this branch table.  If there is a label on your second page that ONLY your second page uses, you don't need to type in any data about it.

Suppose you have a label on your second page called Access_Sprite_Data, and you need to call it from your first page.  Remember, your first page is called page 0, and your second page is called page 1. 

The data to tell the calculator about this label should be typed in after your JP statement.  However, make sure that this page data starts on a byte that is a multiple of 3--and I would not be the best person to help you with that.  If it does not start on a byte that is a multiple of 3, add some .db 0 statements until the data is.  We're going to pretend that the data starts on byte 132, which is a multiple of 3.

.dw Access_Sprite_Data        ; The label on the second page that you need to call from the first page
.db 1                                  ; This function is on the second page

Now, let's say you have a third application page, with a timer function.

.dw Adjust_Timer
.db 2

And so on and so forth.  Just remember that you only need to type in functions/labels that are called from another page.

But you're not done yet.  The data is there, but the calculator doesn't know it.  So what you need is a "nickname" for each label in that branch table.  We will use ASD as the nickname for Access_Sprite_Data, and Timer as the nickname for Adjust_Timer.

ASD .equ 44 * 3     ; 44 * 3 = 132.  We need this because the page data for Access_Sprite_Data is on byte 132 of the program.
Timer .equ 45 * 3   ; 45 * 3 = 135, and the data for Adjust_Timer is on byte 135 of the program


Now, to actually call the label, use B_CALL on the nickname.  DO NOT use call, and do not use the actual label name.

B_CALL ASD
B_CALL Timer


If you need to jump to a label instead of calling it, use B_JUMP.

Now, this technique can only be used for labels that can be called and jumped to.  You, unfortunately, cannot use this to access data from another page.  You should have functions on the page with your data to access that data.

The last thing is, you have to tell your compiler which data goes on which page.  But this differs with each compiler (which one are you using?), so that is something I cannot help you with

Nice screenshot!  It's great to see new progress.

I was using register B for holding the EOL when I should have used Max_Num_Of_Chars, which meant the cursor wasn't advancing and new chars were not being added to the name

Oops, I set the wrong breakpoint.  I can handle the debugging from here

One word: WOW

Are interrupts enabled and in "im 1"?

Yes, I'm afraid that's not the issue.

I think that if CAS is used, the calculator won't be allowed on SAT tests.