Ndless 2.0 for TI-Nspire Clickpad/Touchpad

[ExtendeD]

Ndless combines a resident program and utilities to open the TI-Nspire to third-party C and assembly development.

Ndless 2.0 is the upcoming version compatible with OS 1.7/2.0/2.1, and with Touchpad models.

The up-to-date source code is available on the Subversion trunk (The login/password: guest/guest, you can accept the certificate).


To build and hack into Ndless 2.0:

 - Install a Subversion client such as TortoiseSVN
 - Checkout (don't Import!) the source code with the URL and account above
 - Set up a C development environment
 - Set up the development environment for Ndless and built it: follow the procedure described in src/doc/Ndess-Development.txt in your working copy
 - Install it on nspire_emu or your calculator by following src/doc/ReadMe.txt

Update frequently your SVN working copy to get and rebuild the latest version.

You may browse the Development resources on Hackspire to start your own programs.

Links to download the TI-Nspire OSes are available in this topic.


Major known issues:

• Installation message replaced by a document format warning on real harware:
  The program loader is called before it is installed, earlier than on OS 1.7. The issue doesn't appear on nspire_emu.
  
  

Other possible enhancements and known issues are available on the tracker.


Planned features:

• A simple console: The console integrates with programs through stdin and stdout/stderr (replacing the default RS232 interface), to make ports of non-TI-Nspire programs easier. The keyboard is used to type in strings, which are echoed on the screen. stdout/stderr is displayed on the scrolling screen.
  A simple shell may also be added, with history and auto-completion of file names to make possible the execution of command-line tools with arguments.

Your help is needed:

- Post any bug report, source-level if possible
- Help us to extend the list of supported syscalls
- Any details, diagnostic or patch which would help fixing the defects is extremely valuable

Ndless is an Open Source project, which means:

• Time is not a constraint. Quality and Features are. Please don't ask for release dates.
• Any contribution (patches, information, problem reports) for this version can be valuable.

[ExtendeD]

And here comes a major problem: nspire_emu doesn't support file transfers for OS 2.x, so debugging is not easy.
Someone once suggested to transfer the file from OS 1.7 and then upgrade the OS. But I get a crash on OS startup, and anyway I wild get mad after a few debug sessions.

[Munchor]

And here comes a major problem: nspire_emu doesn't support file transfers for OS 2.x, so debugging is not easy.
Someone once suggested to transfer the file from OS 1.7 and then upgrade the OS. But I get a crash on OS startup, and anyway I wild get mad after a few debug sessions.

your emulator can't open/edit regular .tns files made in OS>2?

[ExtendeD]

Ncubate directly relies on the link features of Goplat's original nspire_emu.

This is a pure problem of file transfer and does not depend on the version of the .tns.

[Munchor]

Ncubate directly relies on the link features of Goplat's original nspire_emu.

This is a pure problem of file transfer and does not depend on the version of the .tns.

So, I suppose you're gonna have to fix that and make a new version of nspire_emu?

[DJ Omnimaga]

I hope to see new development on Ndless 2 soon. Hopefully you won't run into many more problems in the future. I hope the emulator issue can be fixed as well.

[qazz42]

Does this include CAS touchpad?

[Munchor]

Does this include CAS touchpad?

That would be sweet, but I believe it does (Afterall it should work for 2.x operating systems)

[Galandros]

The new keyboard is indeed better to use, so I saw a lot of people upgrading to Nspire 2.0 to use it.
Supporting the 2.0 OS would be a win-win for usability and running cool stuff.

Waiting for updates.

[Goplat]

And here comes a major problem: nspire_emu doesn't support file transfers for OS 2.x, so debugging is not easy.
Someone once suggested to transfer the file from OS 1.7 and then upgrade the OS. But I get a crash on OS startup, and anyway I wild get mad after a few debug sessions.

Here's another possible workaround, that just takes a reboot instead of a full OS reinstall: create a patched boot2 that doesn't try to load the OS but goes straight into download mode. (e.g. patch the code at offset 0x1244 from 31 06 00 eb to 15 00 00 ea). Send documents using the patched boot2 (may need to set the target folder to the empty string, it doesn't seem to like sending to Examples). Save flash, quit, and restart using the original boot2.

Edit: what do you mean by getting a crash on OS startup? If you're referring to the problems in OS 2.1 CAS, here's a fix: it expects GPIO 2 to be high (indicating battery door closed, not open)

Code: Select All | Copy To Clipboard

1 2 3 4 5 6 7 8 9 10 11 12 13 14

Index: apb.c =================================================================== --- apb.c       (revision 56) +++ apb.c       (revision 57) @@ -15,7 +15,7 @@                         case 0x10: case 0x14: case 0x1C: case 0x20: case 0x24:                                 return 0;                         case 0x18: -                               return i == 1 ? 1 : 0; +                               return 0x0104 >> (i * 8) & 0xFF;                 }         }         return bad_read_word(addr);

[ExtendeD]

Thanks Goplat, I like it!

Edit: what do you mean by getting a crash on OS startup?

When upgrading for non-CAS 1.7 to 2.0.1, I get (in OS 2.0.1):

Code: Select All | Copy To Clipboard

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

Purging temporary files... Launching system... Error at PC=1028C97C: r0 = ff000000, nav user = 11f1ee14         Backtrace: Frame     PrvFrame Self     Return   Start 1800FAC4: 1800FB64 1800FAC8 1028C288 1028C924 1800FB64: 1800FB9C 1800FB68 1027D35C 1028C1F8 1800FB9C: 1800FBE4 1800FBA0 1027D138 1027D2CC 1800FBE4: 1800FC14 1800FBE8 1027CFB0 1027CFF0 1800FC14: 1800FC4C 1800FC18 1027CC74 1027CEF4 1800FC4C: 1800FCC4 1800FC50 1028B5BC 1027C6D8 1800FCC4: 1800FCE4 1800FCC8 1028B070 1028B10C 1800FCE4: 1800FD14 1800FCE8 101C7B3C 1028AFD8 1800FD14: 1800FD34 1800FD18 101C7C58 101C7B04 1800FD34: 1800FD9C 1800FD38 1000124C 101C7BC0 1800FD9C: 1800FDD4 1800FDA0 102F0F70 10000FC8 1800FDD4: 1800FDF4 1800FDD8 10265938 102F0F24 1800FDF4: 1800FDF8 1800FDF8 00000000 10265920

[Munchor]

* Goplat saves the world

[Goplat]

Error at PC=1028C97C: r0 = ff000000, nav user = 11f1ee14

Yeah, it's not good to be resetting while leaving the usblink hack active, especially to a different OS version where addresses will have changed. I should fix it to clean everything up on reset. Anyway, shouldn't be a problem with the method I described.

[SirCmpwn]

^++ I'd love to hear how this is progressing.

[ExtendeD]

But December the 4th was just last week...
I have professional and personal changes at the moment, please don't except any progress that soon on Ndless.