OS upgrade files: Difference between revisions
(Creation, TI-Nspire.cer) |
(→TI-Nspire.img: Added) |
||
Line 15: | Line 15: | ||
:0260 - 140 : A second one! The beginning and the end of the 2 fields are similar. | :0260 - 140 : A second one! The beginning and the end of the 2 fields are similar. | ||
240 - 128 : Same field ID as in the .tno/.tnc. Certificate signature. | 240 - 128 : Same field ID as in the .tno/.tnc. Certificate signature. | ||
FFF0 - 0 : END_OF_CERT | <br/>FFF0 - 0 : END_OF_CERT | ||
==TI-Nspire.img== | |||
As for ''TI-Nspire.cer'', the file is organized as a certificate. | |||
(''Format of the following section: <tt>Field ID (hex) - size (dec) - @TI-Nspire: offet of the current version (hex) - @TI-Nspire CAS: offset): comment. </tt> The indentation corresponds to subfields.) | |||
8000 : AMS Header - Invalid size?? | |||
:8040 : Product Name: "TI-Nspire" | |||
:8010 : First part of Product ID | |||
:80E0 : Different on TI-Nspire and TI-Nspire CAS | |||
:8020 : Version number: "1.1.9253"/"1.1.9170" | |||
:8020 : Version number, a second time | |||
:8080 : ? | |||
:0320 - 6 : Product code : 0 | |||
:80F0 - 64 : A signature? Equivalent to TI-68k's field 200? (but it doesn't seem to be the MD5 of the product code). The first 8 bytes and the 16 last bytes are the same on TI-Nspire and TI-Nspire CAS. | |||
:8210 : ? 24ED68 on TI-Nspire, 0BA9CB on TI-Nspire CAS | |||
:8200 : Starts with PK. PK-Zipped file system, see further. | |||
:8070 - TI-Nspire:2403720, TI-Nspire CAS:2339224 - @TI-Nspire: A7F36, @TI-Nspire CAS: 490E2: Crypted, probably also compressed. Only the 8 first bytes are the same between the .tno and the .tnc. | |||
0240 (024D) - 128 - @TI-Nspire: 2F2CBE, @TI-Nspire CAS : 28427A: the signature of the .img, similar to TI-68k's 64 bytes long field 0200. | |||
<br/>FFF0 - 0 : END_OF_CERT | |||
Additional remarks: | |||
*The crypted field 8070 is 195568 bytes longer in the .tno than in the .tnc, that is the TI-84 Plus emulator of the TI-Nspire would be ~200kb bigger than the CAS of the TI-Nspire CAS! May be the two OS integrates a CAS, but it is not enabled on the TI-Nspire. | |||
==We need your help== | ==We need your help== | ||
*Find out what the unknown fields of ''TI-Nspire.cer'' mean | *Find out what the unknown fields of ''TI-Nspire.cer'' and ''TI-Nspire.img'' mean |
Revision as of 21:16, 4 August 2007
The latest versions of the TI-Nspire and TI-Nspire CAS Operating System are available here. This article describes the format and content of the current versions (v1.1.9253 and v1.1.9170) of the .tno and .tnc files.
.tno/.tnc
A .tno/.tnc is a PK-Zip file with a custom ASCII header describing the OS update file. The PK-Zip file contains a certificate file (TI-Nspire.cer) and a .img file (TI-Nspire.img).
TI-Nspire.cer
The file follows TI's standard certificate format used on many caculator models. See TIGCC's documentation for more information (more particularly cread and cfindfield).
(Format of the following section: Field ID (hex) - size (dec) : comment. The indentation corresponds to subfields.)
350 - 298 : top-level field, similar to TI-68k's FLASH_APP_CERT (0x0300), PRODUCT_CODE (0x0320), FLASH_ROM_CERT (0x0330), etc.
- 0010 - 4 : ?
- 0100 - 4 : Revision Number (same field as for the TI-68k)
- 0260 - 140 : ?
- 0260 - 140 : A second one! The beginning and the end of the 2 fields are similar.
240 - 128 : Same field ID as in the .tno/.tnc. Certificate signature.
FFF0 - 0 : END_OF_CERT
TI-Nspire.img
As for TI-Nspire.cer, the file is organized as a certificate.
(Format of the following section: Field ID (hex) - size (dec) - @TI-Nspire: offet of the current version (hex) - @TI-Nspire CAS: offset): comment. The indentation corresponds to subfields.)
8000 : AMS Header - Invalid size??
- 8040 : Product Name: "TI-Nspire"
- 8010 : First part of Product ID
- 80E0 : Different on TI-Nspire and TI-Nspire CAS
- 8020 : Version number: "1.1.9253"/"1.1.9170"
- 8020 : Version number, a second time
- 8080 : ?
- 0320 - 6 : Product code : 0
- 80F0 - 64 : A signature? Equivalent to TI-68k's field 200? (but it doesn't seem to be the MD5 of the product code). The first 8 bytes and the 16 last bytes are the same on TI-Nspire and TI-Nspire CAS.
- 8210 : ? 24ED68 on TI-Nspire, 0BA9CB on TI-Nspire CAS
- 8200 : Starts with PK. PK-Zipped file system, see further.
- 8070 - TI-Nspire:2403720, TI-Nspire CAS:2339224 - @TI-Nspire: A7F36, @TI-Nspire CAS: 490E2: Crypted, probably also compressed. Only the 8 first bytes are the same between the .tno and the .tnc.
0240 (024D) - 128 - @TI-Nspire: 2F2CBE, @TI-Nspire CAS : 28427A: the signature of the .img, similar to TI-68k's 64 bytes long field 0200.
FFF0 - 0 : END_OF_CERT
Additional remarks:
- The crypted field 8070 is 195568 bytes longer in the .tno than in the .tnc, that is the TI-84 Plus emulator of the TI-Nspire would be ~200kb bigger than the CAS of the TI-Nspire CAS! May be the two OS integrates a CAS, but it is not enabled on the TI-Nspire.
We need your help
- Find out what the unknown fields of TI-Nspire.cer and TI-Nspire.img mean