No, but I have collected pieces to make one.

The connector itself will have to be homemade -
  a trimmed perferated circuit board where the wires are fastened that make contact with the nspire contacts.
  Then a heavy duty rubber band straps it down to those contacts, and keeps the cover from sliding
  down at the same time. A solder contact seems too unreliable and can damage those contacts.

They probably flashed boot1 onto those calculators, and then boot2,diags, and the OS through RS232.

Ok guys. I've filmed the 1.1.7xxx diags code yesterday. It took me 90 minutes, with the finger on the down arrow, and exiting/restarting the NAND reader every 5-6 minutes as there is a bug (see above).

That diagnostics version is quite interesting, as it has a NAND reader and a NAND writer too. So you can read and modify anything in NAND, yes anything (like the downgrade protection for example).
It's very important to dump it, as we might be able to flash it on TI-Nspire CAS+ calculators for example and understand more about those older and strange prototypes running the 1.0 OS.

The range is 16B000-20FFFF.

But some some areas are filled with 0xFF bytes:
1CED0B-1FF7FF
200C90-20FFFF

So it seems we only have to dump:
16B000-1CED0A
1FF800-200C8F


Could some of you try to OCR the video with the appropriate tools?

I still have to dump the boot2 (it'll probably take me 3 hours) and the OS (...).
But I'd like to get some comments with the OCR first, before filming again.

Here are the files:
http://xandrean.free.fr/ns-1.1.7xxx-cam/


Thank you very much for helping.

I had an Idea regarding a dock connector. You Solder the pins to a pin header, and embed that into the spring-loaded plastic cover, and glue it down. You can still put on the slide case, so nothing's exposed during normal use.

I used an Ndless program here.
I think there is a key combination to launch it, but haven't found it - there is FlashFX strings in the boot code.
I also could not find it on OS2 with a simple binary search to patch that small Ndless program.

EDIT: I will add its Goplat's , charming, impresssive 16 byte program posted on another forum.

But Wifi cradles cost quite much, don't they?

In order to dump what's in the TI-XXXXXXXXXXX (oldest OS 1.1 based TI-Nspire prototype), I've made some flashing in RS232.
(it's not a problem, as I have 3 of them)

Remember the included OS doesn't seem to have an implemented USB linking protocol (device detected like all other TI-Nspire & TI-Nspire CAS prototype and production calculators, but not listed by TI-Nspire Computer Link).


Here are some pictures if you're messed up with all prototypes I've got:
http://ti.bank.free.fr/index.php?mod=galerie&action=img&id_gal=9&id_img=130


1) remove the 1.1.7320 OS

The 1.1.7314 boot2 "install OS" screen doesn't seem to provide any better USB linking protocol.

2) flash the newer 1.1.9227 OS (Ndlessable) in RS232

Failed...
See what I get:

Loading Operating System...

Error loading OS image. Removing OS remnants.
Deleting file [/phoenix/manuf.dat]
Removing directory [/phoenix/install/]

Waiting for OS download.
Starting Connectivity services.
Initializing USB subsystem...Done.
Setting Console Log Level = 0
RET - SC: TI_CN_Nspire_SC_Init called
NavNet Ready.
USB Download is enabled.
Press <Enter> to download through the serial port.
Checking battery level.
Battery level is OK.
Begin XMODEM file transfer.
File transfer complete. Saving pre-load file.
Error saving pre-load file.
BOOT2 Error: install failed
I tried to flash every developer tno file I've got: 1.1.8008, 1.1.8410, 1.1.9227.
Exactly the same error each time.
I even removed everything from the file system using the maintenance menu: no difference...

3) flash the newer 1.1.8007 boot2 (USB support) in RS232

ok
So there doesn't seem to be a problem with my serial interfacing.
I don't understand why I couldn't flash an OS...

4) flash the newer 1.1.9227 OS (Ndlessable) through USB

ok
No problem at all, which does confirm there's a problem with USB in 1.1.7314 boot2.

5) ndless the 1.1.9227 OS

ok

5) dump 1.1.7314 boot1 and 1.1.7387 diagnostics

ok


I still need to dump the 1.1.7314 boot2 and the 1.1.7320 OS from my other TI-XXXXXXXXXXX prototype.


I've tried to reflash an OS in RS232 with the installed 1.1.8007 boot2.
I've also tried after flashing all other developer boot2 files I have: the 1.1.8310 and 1.1.9170.

Same error...

What am I doing wrong?
Flashing an OS in RS232 seemed to "virtually" work in the early Goplat's emulator releases, as OSes were installed this way...


If I could flash the 1.1.9227 ndlessable OS on the other prototype in RS232, then i could dump the 1.1.7314 boot2.


Thanks for any advice.

Thanks for saving me the trouble on those video files.
I learned something about Video Text Recognition
which seems to be more of an art than a science .

Thanks for all your hard work, bsl.


But we're not done yet...
I could take a video of the boot2 and the OS!

Note that even if I manage to dump the boot2 by flashing an Ndlessable OS using the 1.1.7314 boot2, I can't see any way of dumping the OS...


By the way, any idea about that RS232 OS flashing problem ?

Although boot2.img is sent on RS232 as-is, OSes must be sent with a 32-byte header. The first 24 bytes, as far as I know, are unused. Bytes 24-27 are the size of the data to write to /tmp/manifest_img (nspire_emu always just set this to 0, and it worked, so I guess it's not important. Probably something left over from the CAS+.), and bytes 28-31 are the size of the data to write to /tmp/TI-Nspire.tnc. (Note: these sizes are big-endian)

printf("Loading OS from %s\n", os_filename);
FILE *f = fopen(os_filename, "rb");
if (f) {
        u8 *mem = ram_ptr(arm.reg[0]);
        u32 size = fread(mem + 32, 1, arm.reg[1], f);
        memset(mem, 0, 28);
        mem[28] = size >> 24;
        mem[29] = size >> 16;
        mem[30] = size >> 8;
        mem[31] = size;
        fclose(f);
        arm.reg[0] = 0;
} else {
        perror(os_filename);
        arm.reg[0] = 1;
}
arm.reg[15] = arm.reg[14];

Edit: Here's a possibility to recover the OS. Use Home-Enter-X to send a "temp image" (a .tno/.tnc file, without the 32 byte header) - it will run the sent OS without installing it. It will have to be compatible with the installed OS, though, in terms of filesystem contents. I tried using a modified nspire_emu to run 1.1.9227 on top of a 1.1.8008 installation; there were some messed-up text messages but other than that it seemed to work fine. If you could run a USB-capable OS on top of a 1.1.7320 installation, then you could probably just dump the old OS with TiLP.