In a previous news, we discovered that Boot1/Boot2 version numbers couldn't be trusted to determine if a TI-Nspire handheld was a prototype or not.

Yes, we were told about a TI-Nspire prototype running both Boot1 1.1.8916 and Boot2 1.1.8981.



Today, we've finally got such a prototype between our hands.

And we are beginning to understand - let's check the OS:


1.4.8092... This prototype OS is more recent than everything we've found up to now.

It seems that the goal of the prototype versions of Boot1 1.1.8916 and Boot2 1.1.8981 was enabling TI engineers to go on testing trustfully development OSes on their prototypes.



But there is more - just have a closer look at the OS version string:
Full version string is "1.4.8092 debug" - this time it's not a simple development OS sent for testing to teachers/students...
It's a debug development OS coming from the TI development team!

A very nice find - as usually, prototypes used internally for development at TI have to be destroyed once they're no longer needed.



So what's special about this OS?
It creates a debug file "/documents/navnet.log.csv" where is stores lots of informations about the NavNet link engine.
Logged lines are mirrored to the RS232 console and all start with [64].

Just check the OS bootlog:
Beginning system initialization.
Preparing file system. This takes a while ...
   POSIX layer initialized.
   POSIX initialized devices.
Datalight Reliance v2.10.1150
Copyright (c) 2003-2006 Datalight, Inc..
Datalight FlashFX Pro v3.00 Build 1358
Nucleus Edition for ARM9
Copyright (c) 1993-2006 Datalight, Inc..
Patents: U.S. # 5860082, # 6260156 U.S..

   POSIX file system initialized.
File system ready.
* P1R2 battery door detection method
System build date: May 13, 2008, 11:30:55 p.m.
Available memory: 18624748 bytes
Purging temporary files ...
Launching system ...
Setting log file to / documents / navnet.log.csv with a buffer of 4096 bytes
Setting Console Log Level = 3
RET - UDP Echo: TI_Echo_UDP_Init Called + + +
RET - ECHO UDP Socket ID We created Successful. Socketid = 1
RET - UDP ECHO: TI_UDP_Echo_BindIPAddr + + +
RET - UDP ECHO: Successful NU_Bind
RET - UDP ECHO: --- TI_UDP_Echo_BindIPAddr
RET - UDP ECHO: EchoUDPListenerThread. Inside Thread + + +
RET - UDP ECHO: Init Called ---
[64] Register UDP stream connector, result = 0
[64] Called TI_NN_Init. LowAPI LowAPI LowAPI 02-06-2008
[64] CM: init_conn_mgr: Entered (NavStack: connection manager: 1/31/2008).
[59] CM: processLocalNodeRecvDeferredQueue: Entered (NavStack: stream manager:
/ 22/2008).

[64] Entered TI_NN_StartService. Service Id: 5000 + + +
[64] Start service: port 5000 '. NS_SVC.5000' service.
[64] End of TI_NN_StartService. 5000 Service started. ---
[64] Start sync services
[64] Entered TI_NN_StartService. Service Id: 4060 + + +
[64] Start service: port 4060 '. NS_SVC.4060' service.
[64] End of TI_NN_StartService. 4060 Service started. ---
[64] MS: MessageServiceRegister called.
[64] Entered TI_NN_StartService. Service Id: 4051 + + +
[64] Start service: port 4051 '. NS_SVC.4051' service.
[64] End of TI_NN_StartService. 4051 Service started. ---
[64] MS: MessageServiceRegister called.
[64] MS: MessageServiceRegister called.
[64] MS: MessageServiceRegister called.
[64] MS: MessageServiceRegister called.
[64] MS: MessageServiceRegister called.
[64] MS: MessageServiceRegister called.
[64] MS: MessageServiceRegister called.
[64] MS: MessageServiceRegister called.
[64] OS install Start Service
[64] Entered TI_NN_StartService. Service Id: 4080 + + +
[64] Start service: port 4080 '. NS_SVC.4080' service.
[64] End of TI_NN_StartService. 4080 Service started. ---
[64] Start node info service.
[64] Entered TI_NN_StartService. Service Id: 4020 + + +
[64] Start service: port 4020 '. NS_SVC.4020' service.
[64] End of TI_NN_StartService. 4020 Service started. ---
[64] Entered TI_NN_StartService. Service Id: 4042 + + +
[64] Start service: port 4042 '. NS_SVC.4042' service.
[64] End of TI_NN_StartService. 4042 Service started. ---
[64] Start screen Service
[64] Entered TI_NN_StartService. Service Id: 4024 + + +
[64] Start service: port 4024 '. NS_SVC.4024' service.
[64] End of TI_NN_StartService. 4024 Service started. ---
[64] Entered TI_NN_StartService. Service Id: 4052 + + +
[64] Start service: port 4052 '. NS_SVC.4052' service.
[64] End of TI_NN_StartService. 4052 Service started. ---
[64] Called TI_NN_RegNotifyCB. + + +
[64] CM: RegisterNotifyCallback called.
[64] End of TI_NN_RegNotifyCB. Notify Callback registered. ---
[64] New API: Load Effective connector all services started.
[64] Initializing 2 Connector (s).
NavNet Ready.

Something which could have been very useful if we got it sooner, when adding TI-Nspire support in TiLP for example.



In fact, this is not our first TI-Nspire debug OS.

Summer 2011 at TI-Dallas, Adriweb found a TI-Nspire running a debug version of the 1.8 Nspire OS, which was never released as we went straight from 1.7 to 2.0:



Sources:
http://tiplanet.org/forum/viewtopic.php?t=10671
http://tiplanet.org/forum/viewtopic.php?t=10669

Great work critor!

That is pretty epic! TI will never manage to block such stuff completley out