TiLP
a TI Linking Program

• conversion of TILP from Glade to GTK+Builder: the bulk of the work was done by Jon Sturm, it opens the door to further improvements on the code base.
• Initial, incomplete TI-84+CSE support: OS upgrades, FlashApps, pictures and possibly certificate files are supported (provided the files are renamed from *.8c? to *.8x?), background images not supported.
• new TI-Z80 ROM dumper, with improved 82/85 support, 84+ Flash unlocking, etc.
• USB scan at startup (options.auto_detect) enabled by default (but old config files are not updated, obviously), to match the behaviour of TI-Connect and TINC(L)S.
• no more cmd window for TILP on Windows: the output is now properly redirected to a file even when there's no such window (by Benjamin Moody).
• other features: raw mode external linking, loading libusb-win32 dynamically, tons of previously (wrongly) internal libticalcs functions now exported to user programs so that they no longer need to copy and paste thousands of lines of code if they merely want to implement a new command not yet implemented by libticalcs, Nspire remote control primitives, 83+ DBUS memory page dump primitive, initial TI-80 VSC support, etc.
• Bugfixes: more warnings, more crasher bugs, more undefined behaviour fixed (clang is a valuable tool !); upstream fixes to ease downstream packagers' job; relying on libarchive instead of embedding a patched copy of minizip.

• Massive Windows improvements: newer libusb version which enables side-by-side installation with TI-Connect/TINC(L)S (with manual configuration), per-user settings, less spam in the console output window, much more reliable GTK+ download procedure.
• Desktop integration: Drag&Drop code improvement, FreeDesktop.org .desktop files, MIME types files. Contributed by Jon Sturm.
• Nspire CX (and hopefully CM) support: getting screenshots, upgrading the OS.
• Bugfixes: crasher bugs, human-readable messages for previously unknown error codes, a number of TI-Z80-related bugs (most of these reported by Benjamin Moody).

• User interface improvements: for example, a menu at the top of the window.
• New libusb 1.0 backend for libticables: TILP II 1.15 will work for the users of the many distros which, unfortunately, don't package libusb 0.1 proper anymore.
• Bugfixes for DirectLink calculators: most of the causes of failure when sending or receiving files of peculiar sizes are gone.
• Nspire OS 2.x and 3.x support, several new operations, e.g. remote variable deletion.

• major bugfixes for the Z80 models: groups & file checksums, thereby significantly improving TILP's interoperability with TI-Connect files and vice-versa;
• major bugfixes for the Nspire models: connection is slower, especially on older OS, but reliable;
• addition of a DirectLink (USB) 84+ ROM dumper kindly contributed by Brandon Wilson.

• I have been working in the TI-68k community for about ten years, and I would like to focus on other activities that I have become more interested in,
• the community is dying or has been almost dead since 2007. The Nspire could have reversed the flow, but it remains, to date, a piece of hardware and software closed to third-party, amateur development. It's an enormous shame (in my opinion and in the opinion of many other TI-68k developers), because "hackability" and third-party development was THE factor of success in the marketplace for TI-Z80 and TI-68k calculators.

> Any ideas about this 'bug'? Is it related to kernel or bad hand-held
> hardware?

It is a bug in the Titanium firmware. In the logs for both handhelds you 
can see where the kernel sends a Set-Interface request after your driver 
releases the interface. (The kernel does this automatically so that the 
interface will be back in its original condition when the next driver 
binds to it.) Both devices return an error, which is a perfectly legal 
response.

However the Titanium then crashes. It doesn't respond to the Clear-Halt
commands sent by the kernel after the Set-Interface fails, whereas the
TI84+ acknowledges them correctly. Since it has crashed, your driver is 
unable to reconnect and you have to reset the device by unplugging it.

The source of the errors is the Titanium failure to respond to the 
kernel's Clear-Halt requests.

Alan Stern