I have a question though: When I comment out "bl lcd_ingray" in the asm example, the editor promptly closes (crashes ?). Commenting out "lcd_ingray()" in the C example however doesn't crash and the program works fine.

It seems that nspireio2 supports color screen buffers although the ReadMe doesn't advertised it, so skipping lcd_ingray() may not be a problem.
But the ARM demo does expect a gray screen buffer (2 pixels per byte).

As Lionel Debroux points it out, ARM assembly is not the recommended language to develop for Ndless, although it can be a good option for low-level interaction with the hardware of for performance (as for example used by Goplat or calc84maniac for their emulators).

So I haven't really been maintaining anything in the Ndless SDK to make things really easy when developping in ARM.
But I have fixed what has been broken in the past revisions for your two to be able to get your hands on ARM assembly. Don't except things to go without any hassle, but you can report anything missing that could help you.

1) Download the Ndless SDK r833 or higher
2) Have a look at _samples\helloworld-asm I've added
3) The Makefile template and the Ndless Editor are now ARM assembly aware. When creating a new project, build your .S (mind the upper case, so that the file is processed by the preprocessor) with Tools>Build to generate the Makefile as you would do for a C/C++ program.

Some things (defines, structures, ...) won't always be directly available in assembly, in these cases you'll have to browse into the include files to understand the C definitions and translate them into assembly. The  Hackspire Wiki will also be a good source of information.

To load the file into the emulator, maybe some AutoIt hack would as I did for the NdlessEditor.

With Ndless 3.1 it's actually not really different than installing it on real HW. Create the folder ndless/, transfer ndless_resources to it, then ndless_installer as an OS update (there's an nspire_emu command for this in the link menu). it's a matter of seconds

This was an experiment not really meant for public announcement. I'm not actively working on the project at the moment.

So does the use of bFLT mean that the issues with global variables are now also solved?

Yes You can thank tangrs for this.

Nice Matrefeytontias
I suppose that cross-platform compatibility would require SDL, if it's now available on PRIZM.