Here are the maximal free space sizes, with all pruned and original TI-Nspire OSes:



With OS 1.4 or later, you can increase your free space by 2-3.5Mb by using the TNOC tool.


If new OSes go on being bigger an bigger, users are going to have problems when upgrading/downgrading, because the free space won't be enough to store the temporary tno/tnc file during installation.

They'll have to remove the OS through the maintenance menu before...

TI is so stupid...

Yes, there will be a manual decoder.

Anyway it's not Morse. Morse code doesn't have colors.
But it's similar. And because there are colors, less signals are needed per letter.

I've made other tests for the "LED-locking" protection.

I've tested:
* a basic TI-Nspire with OS 1.3.2438 + Ndless 1.3
* a basic TI-Nspire with OS 1.4.11653 + Ndless 1.4

OS 1.4 seems to have the "LED-locking" protection.
But... OS 1.3 doesn't seem to have it.

So with OS 1.3.2438 (there is another one, 1.3.2407, which is not supposed to be compatible with Ndless 1.3), you just run my program and it should work on the 1st try!


So we may assume:
* non-CAS OSes 1.1-1.3.2438: no "LED-locking" protection
* non-CAS OSes 1.4.11653 and newer: "LED-locking" protection (but which can be disabled temporary: see previous posts)

I don't know if it's the same thing for CAS OSes.
Nspire CAS ClickPad didn't have a DEL (although they have the circuit). So it's hard to test... That protection might be absent because of that.
Nspire CAS TouchPad do have the DEL. I should downgrade to 1.3/1.4 and test.

Thank you ztrumpet.


I've finally rebooted my boot2 1.1 calculator myself.
The DEL was locked.


So let's sum up things:

- After "exit PTT" reboots, the DEL is unlocked and the program is fully working.
- After other reboots with OS 1.7, the DEL is locked and the program won't be able to turn it on.

Finaly, this doesn't seem to have anything to do with the boot2. Although my boot2 1.1 calculator does not reboot after exiting the program.
But the reboots might be totally unrelated to this program... I've had stange reboots while testing mViewer, while installing Ndless, and even when turning back on a Ndlessed calculator.


It would still be interesting to know if some other kind of reboot (reinstalling OS 1.7, reformatting the whole FS) leaves the DEL unlocked.

And it would still be interesting to test if only OS 1.7 is locking the DEL, of it even happens with OS 1.3/1.4 (which can be Ndlessed).
We can assume that OS 1.1 does not lock the DEL.

I've added a self-test mode in the program, which should let you figure out if the LED is locked or not.
I've finished the encoder.
Just the decoder is missing.

I've made further tests for the DEL with the following 4 calculators:
- 1x basic TI-Nspire ClickPad with Boot2 1.1 and OS 1.7
- 2x basic TI-Nspire ClickPad with Boot2 1.4 and OS 1.7
- 1x basic TI-Nspire TouchPad with Boot2 1.4 and OS 1.7


On the Boot2 1.1 calculator, no problem. The DEL is unlocked & working and the calculator is not rebooting.

On all 3 Boot2 1.4 calculators, if the DEL is unlocked, the program may trigger a reboot. It might happen when entering the program, or even severall minutes after exiting the program.
After this reboot, the DEL is locked. Writes to its memory port are just ignored and the DEL remains off whatever you do. Turning off/on or rebooting doesn't change anything.
The only way to unlock the DEL up to now is to enter and exit PTT mode. Just after the "exit" reboot, the DEL is unlocked.

This has even worked on the TouchPad.


Note I could be totally wrong, because I've only tested on 4 calculators, and only 1 "boot2 1.1" calculator.
I've attached an alpha binary if you want to try and help me.

Choose '4' to trigger my self-test.
If the last line has the "error" word, then your calculator LED is locked.
if not, it should be turned on by pressing G/Y/R keys.

I'd like to know for each calculator:
* which boot2 version you have
* what was the LED state on the 1st try: lock or unlocked (or reboot before knowing)
* how often it did reboot for you (if it does reboot)
* if you were able to unlock the led (if necessary) by entering and exiting PTT


Have fun turning your LED on/off and sending light-messages with your TI-Nspire.
(remembers me of my HP-48GX which had an I/R port to exchange data... but it was much faster! :p )


It would be interesting to make further test with boot2 1.4 calculators:
* checking if removing and reinstalling OS 1.7 does unlock the DEL
* checking if formatting the FS does unlock the DEL
* checking if the same "reboots" do happen on previous Ndless supported OSes (1.1, 1.3, 1.4)


Edit: further tests done:

* Basic TI-Nspire touchPad with boot2 1.4:
Triggering a 2nd reboot yourself after exiting PTT whith an unlocked DEL (after running the program, without having run the program, or even without having installed Ndless) does lock the DEL. Seems the DEL is locked by the Boot2 1.4 and/or the OS 1.7 at boot time, except with the "exit PTT" reboot.

I could be completly wrong, but the DEL locking could have something to do with boot2 1.4 (or with boot2 1.4 + OS 1.7).

The calculator which is working the best currently has boot2 1.1 + OS 1.7.
Itmight be totally unrelated though.

I'll make further tests later.
Currently, i'm developping the encoder(automatic)/decoder(manual).

I'm not even sure I want it to work  all the time.

It seems TI has added some software LED protection between OSes 1.1 and 1.7.
That protection is not 100% reliable (or you wouldn't have got the above video).

If we do hack / reverse enginer that protection, TI might get very mad...
I think I'm going to release the current code without adding any hack.

I won't try to understand more. The problem is not mainly me: TI might attack Ndless & ExtendeD.

So I'm not releasing code which hasn't been documented on HackSpire or used in BlockDude yet.

You know the protection is disabled by entering and exiting PTT mode, and is randomly triggered when launching the program.
If you find a way, you'll just have to add the lines in the code, before the 1st LED port reading/writing.