Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - critor

Pages: 1 ... 97 98 [99] 100 101 ... 137
1471
Other Calculators / Re: TI-Nspire prototype 1.1.7320
« on: March 19, 2011, 11:26:32 am »
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:

Code: [Select]
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.

1472
Other Calculators / Re: The 1st step into CAS+ flashing
« on: March 18, 2011, 06:02:57 pm »
I'm going to try all that.


I've used another terminal, and was able to get the complete hexadecimal output (including raw control/escape characters) from the "type devfiletree.zip" command.

As mentionned previously, there is no 0x00 byte in the file, meaning each time a 0x00 byte is encoutered, the rest of the read buffer is skipped/lost.

The success rate is very low: I only got 29Kb of data (the file is 624Kb).

In fact, I mainly got the system messages, and allmost no code I suppose.
So I'm attaching the file publicly, as I think there is no problem with such a bad allmost text-only file.

But if you think I'm wrong, just tell me.



Anything interesting in this file?


Would there be any command to segment files?
We might be able to get more data like that...

1473
Other Calculators / Re: The 1st step into CAS+ flashing
« on: March 18, 2011, 02:08:08 pm »
Hi!


I've done other tests today.

The CAS+ driver is very different from the final driver.
It seems to setup some virtual local "USB" network.

As you could see in "recent" CAS+ logs, there is some kind of a DHCP server on the calculator.

For example, if I plug a recent CAS+, I'm getting a new peripheral: "Texas Instruments Remote NDIS Network Devices". I'm getting a new network connection, which aumatically gets its IP (for example, it can get 172.16.80.29, with 255.255.255.252 mask).


I mentionned there was no trace of it in the oldest CAS+ log.
Allow me to correct: the DHCP server is there but is not launched automatically.
It is launched when you plug the USB for the 1st time.

When I plug my oldest CAS+, the "Texas Instruments Remote NDIS Network Devices" does appear, but fails at getting an IP.
After a long time, it gets by default the bad 169.254.145.44 IP address.

TI-Nspire Computer Link 1.0 isn't finding anything.


Here's the log, when I plug the USB for the 1st time (takes some time):

Code: [Select]
C:\>pn-srv6-457: nuc_init, release the hounds
01 00:23:23.000 0 | Waiting for next RPC call...
pn-srv6-463: nuc_init done
pn-srv6-333: msg Q id = 8
pn-srv6-1073: bound dhcp-wake [127.0.0.1:10005] to 1
pn-srv6-1073: bound dhcp-req [0.0.0.0:67] to 2

phoenix dhcp server  built 25-Apr-2006  running

pn-srv6-1193: usb insert 2,0,14
pn-srv6-1073: bound dhcp-ans [172.16.46.58:68] to 4
pn-srv6-701: request type 1
pn-srv6-821: ready to reply(hh=4, sz=281), typ=2, to port 68
pn-srv6-838: sent reply 2, len=281, to port 68
pn-srv6-701: request type 1
pn-srv6-821: ready to reply(hh=4, sz=281), typ=2, to port 68
pn-srv6-838: sent reply 2, len=281, to port 68

phoenix enum server  built 25-Apr-2006

pn-srv6-701: request type 1
pn-srv6-821: ready to reply(hh=4, sz=281), typ=2, to port 68
pn-srv6-838: sent reply 2, len=281, to port 68
pn-srv6-701: request type 1
pn-srv6-1073: bound dhcp-ans [172.16.177.46:68] to 8
pn-srv6-821: ready to reply(hh=8, sz=281), typ=2, to port 68
pn-srv6-838: sent reply 2, len=281, to port 68
pn-srv6-701: request type 1
pn-srv6-821: ready to reply(hh=8, sz=281), typ=2, to port 68
pn-srv6-838: sent reply 2, len=281, to port 68
pn-srv6-701: request type 1
pn-srv6-821: ready to reply(hh=8, sz=281), typ=2, to port 68
pn-srv6-838: sent reply 2, len=281, to port 68
pn-srv6-701: request type 1
pn-srv6-821: ready to reply(hh=8, sz=281), typ=2, to port 68
pn-srv6-838: sent reply 2, len=281, to port 68
pn-srv6-701: request type 1
pn-srv6-1073: bound dhcp-ans [172.16.50.34:68] to 9
pn-srv6-821: ready to reply(hh=9, sz=281), typ=2, to port 68
pn-srv6-838: sent reply 2, len=281, to port 68

If I unplug the USB, I get:

Code: [Select]
C:\>pn-srv6-1116: usb notify (0) 2,0,9
pn-srv6-1286: usb remove 2,0,9

If I replug the USB, I get:
Code: [Select]
pn-srv6-1116: usb notify (0) 2,0,9
pn-srv6-1286: usb remove 2,0,9
pn-srv6-1116: usb notify (0) 2,0,9
pn-srv6-1286: usb remove 2,0,9
pn-srv6-1116: usb notify (1) 2,0,9
pn-srv6-1193: usb insert 2,0,9

I've tried to force 172.16.80.29 as an IP address.
TI-Nspire Computer Link 1.0 doesn't find any calculator, but is taking more time looking for them...


Has somebody any idea of the problem?

The zip file from /phoenix/install is in the documents folder.
If I can just transfer one file, we can start looking into the OS.




Other various informations:


The "check" command is working:
Code: [Select]
check c:
relFs_Check v2.00.0451
Copyright (c) 2003 - 2005 Datalight, Inc.
Checking 27M Byte drive C:

Checking critical meta blocks.................................OK
Checking indices..............................................OK
Checking all directory contents and inodes....................OK
Checking allocation map.......................................OK
Checking for stranded blocks..................................OK
relFs_Check completed.

Volume Information:
   29,188,096 bytes in volume
   11,594,240 bytes in 238 files
       66,048 bytes in 102 directories
       34,304 bytes system overhead
   17,493,504 bytes available for use

          512 bytes per block
       57,008 total blocks in volume
       34,167 blocks available

The "show" command is working too:
Code: [Select]
show c:
Datalight Reliance v2.00 Build 0451
Copyright (c) 2003 - 2005 Datalight, Inc.
Settings for Volume 'c:'
  Drive number:                    2
  Total file/directory handles:   30
  Handles in use:                  0
  Physical Disk Info
    Sector size:                 512
    Total sectors:             57008
  Logical Disk Info
    Block size:                  512
    Total blocks:              57008
    Used blocks:               22866
    Free blocks:               34142
  Transaction points:           7945
  Transaction flags:          0x0FA7
Driver Settings:
  Maximum logical block size:  65536
  Cache size:                  256Kb
    Buffers:                     456
    Buffer size:                 512
    Write gather size:          16Kb
  Timed Transactions:       Disabled
  Discards:                  Enabled
    Supported by this volume
    Initial table size:         1024
    Current table size:         1024
    Dynamic Growth:         Disabled
  Byte order:             Big Endian
  Character mode:              ASCII
  Case sensitivity:              Off

C:\phoenix\install\>show a:
Datalight Reliance v2.00 Build 0451
Copyright (c) 2003 - 2005 Datalight, Inc.
Drive "a:" is not open.

Error = -3003

C:\phoenix\install\>show b:
Datalight Reliance v2.00 Build 0451
Copyright (c) 2003 - 2005 Datalight, Inc.
Drive "b:" is not open.

Error = -3003

"time" command is working too:
Code: [Select]
C:\phoenix\install\>time
Jan 01 00:12:20 1980

The following commands are unknown:
* exit
* sx
* rx
* transfer
* flashfxdump
* flashfxdiskinfo


You've read all this?
You deserve a little photo:

Spoiler For Spoiler:

1474
Other Calculators / Re: The 1st step into CAS+ flashing
« on: March 18, 2011, 06:08:50 am »
I don't think it's that important, but I've missed something at the end of my oldest bootlog:

Code: [Select]
Launching system...

Datalight Command Shell for Nucleus

A:�‘¤œ‘H>01 00:00:50.000 0 | Initializing xmlrpc library

As more recent CAS+ are only listing through USB and Computer Link modified code:
/
/phx/
/phx/documents/
/phx/tmp/

I'm wondering if this is related to those A: and C: drives.

Maybe this is the A: drive content, and "/phx/documents" and "/phx/tmp" folders are only links to the "/phoenix/documents" and "/phoenix/tmp" folders from the C: drive.

Maybe, those uninteresting folders are in A:.
If we could add the "C:" prefix in this code, maybe...

If possible, any idea about the Computer Link syntax for that?
"c:/..." ?
"/c/..." ?
"/c:/..." ?

1475
Other Calculators / Re: The 1st step into CAS+ flashing
« on: March 17, 2011, 10:28:04 pm »
I found a post with a list of commands (don't know if it is complete) of the Datalight shell from Boot2 1.4:

Quote
?                    - Display help
APPEND               - Appends data from the console to a file
CD                   - Change the current directory
Check                - Check a Reliance disk
COMPARE              - Compare the contents of two files
CompTest             - Run the Reliance for Nucleus compatibility test
COPY                 - Copy a file
CREATE               - Create a file
DCLTEST              - Execute the DCL unit tests
DEL                  - Delete a file
DIR                  - Display a directory listing
EXIT                 - Exit the shell
FlashFXCheck         - Check the spare unit on disk
FlashFXDiskInfo      - Display FlashFX information
FlashFXDump          - Dump a FlashFX disk image
FlashFXImage         - Read or write a FlashFX disk
FlashFXRemount       - Remount a disk
FlashFXStressMT      - Execute the Multi-threaded VBF unit test
FlashFXTestFMSL      - Execute the FMSL unit test
FlashFXTestVBF       - Execute the VBF unit test
Format               - Format a disk
FSIOTEST             - Execute the File System I/O tests
GetTrans             - Display the transaction mode
HELP                 - Display help
MD                   - Make a directory
RD                   - Remove a directory
REN                  - Rename a file
SetTrans             - Set the transaction mode
Show                 - Display information of a Reliance disk
Test                 - Run the Reliance test suite
TIME                 - Display the current time
TYPE                 - Display the contents of a file on the console
WRITE                - Write to a file using console input

I've striked what didn't work for me.
In bold, what worked.
The rest is untested.

Anything interesting? Anything dangerous?

1476
Other Calculators / Re: The 1st step into CAS+ flashing
« on: March 17, 2011, 10:20:53 pm »
I may be leading you astray
try +++ at the hyperterminal prompt
you might start xmodem transfer.

Sorry, I forgot to mention.
Unrecognized command... :(

1477
Other Calculators / Re: The 1st step into CAS+ flashing
« on: March 17, 2011, 09:55:51 pm »
Any command to trigger a Xmodem file transfer in DataShell ? . . .

If only DataShell was launched automatically like that on more recent CAS+...

1478
Other Calculators / Re: The 1st step into CAS+ flashing
« on: March 17, 2011, 09:30:28 pm »
Wait... the zip file is not yet in my computer...

Seems the type command can't be used to get the whole content of the file, as there are many escape characters (carriage return, new line, clear screen...)


Strangely, I cannot go back to the "a:" drive (error -3003).

I'm getting "error -3003" for "b:" and "d:" drives.
Starting from "e:" drive, I'm getting "command not found".


So, any way to get the content of this zip file without usb ?



Could some other terminal software with a big enough history be used to show "exactly" (any binary mode ?...) what the type command displays?

1479
Other Calculators / Re: The 1st step into CAS+ flashing
« on: March 17, 2011, 09:18:35 pm »
Now extend Goplat's earlier idea:
copy /phoenix/install/TI-Nspire.tnc /phx/documents/examples/OS.tns
and transfer through USB :)

Err....

It's the oldest CAS+ prototype.
I haven't managed to transfer anything through USB, neither with TI-Nspire Computer Link 1.0, nor with other CAS+ calculators.

I suppose there is no USB link protocol implemented in this OS.
(using the "send" menu item just returns immediatly, without any error...)

1480
Other Calculators / Re: The 1st step into CAS+ flashing
« on: March 17, 2011, 09:16:16 pm »
Strangely, the /phoenix/install directory is not empty.

Code: [Select]
C:\phoenix\install\>

1980-01-01 00:00:00     <Dir> .
1980-01-01 00:00:00     <Dir> ..
1980-01-01 00:00:00    639280 devfiletree.zip
1980-01-01 00:00:00        17 manifest

Free Space: 18773504 bytes

The "dir" and "cd" commands are working up to now.

Do you know other commands?


Edit: I can use the type command to get the content of a file.

Code: [Select]
C:\phoenix\install\>

1980-01-01 00:00:00     <Dir> .
1980-01-01 00:00:00     <Dir> ..
1980-01-01 00:00:00    639280 devfiletree.zip
1980-01-01 00:00:00        17 manifest

Free Space: 18773504 bytes


C:\phoenix\install\>
devfiletree.zip

C:\phoenix\install\>

"manifest" seems to only contain "devfiletree.zip".

"type devfiletree.zip" is giving me lots of system characters, starting with "PK".
But unfortunately, HyperTerminal history is not big enough...

1481
Other Calculators / Re: The 1st step into CAS+ flashing
« on: March 17, 2011, 09:09:54 pm »
(sorry for double-posting)

No there are things in the folders.
They're just hidden.

Have a look:
Code: [Select]
C:\phoenix\>

C:\phoenix\install\>

1980-01-01 00:00:00     <Dir> .
1980-01-01 00:00:00     <Dir> ..
1980-01-01 00:00:00    639280 devfiletree.zip
1980-01-01 00:00:00        17 manifest

Free Space: 18773504 bytes


C:\phoenix\install\>

I don't think it's big enough to be the OS though.


Unfortunately, "?" or "help" aren't triggering anything (unknown commands).

1482
Other Calculators / Re: The 1st step into CAS+ flashing
« on: March 17, 2011, 09:04:20 pm »
"dir" command isn't showing anything interesting in the A: drive.
Moreover, there seems to be some problem with the folder names encoding...

But I can access a "c:" drive:

Code: [Select]
A:Ôœ‘dœ‘—">01 00:00:50.000 0 | Initializing xmlrpc library


A:Ôœ‘dœ‘—">

A:Ôœ‘dœ‘—">
Command not found!

A:Ôœ‘dœ‘—">
Command not found!

A:Ôœ‘dœ‘—">
Command not found!

A:Ôœ‘dœ‘—">

Error = -1

A:Ôœ‘dœ‘—">

Error = -1

A:Ôœ‘dœ‘—">
Command not found!

A:Ôœ‘dœ‘—">
Command not found!

A:Ôœ‘dœ‘—">
Command not found!

A:Ôœ‘dœ‘—">
Command not found!

A:Ôœ‘dœ‘—">

A:Ôœ‘dœ‘—">
Command not found!

A:Ôœ‘dœ‘—">

Error = -3003

A:Ôœ‘H,o>

Error = -1

A:”œ‘dœ‘؆X®>

Error = -3003

A:>

Error = -3003

A:>

A:>
Command not found!

A:>

A:>

A:>
Command not found!

A:>
Command not found!

A:>
Command not found!

A:>

A:>

Error = -3003

A:>

Error = -3003

A:>
Command not found!

A:>

A:>

A:>

Error = -3003

A:Žœ‘>

C:\>

1980-01-01 00:00:00     <Dir> tmp
1980-01-01 00:00:00     <Dir> dev
1980-01-01 00:00:00     <Dir> phoenix
1980-01-01 00:00:00     <Dir> documents
1980-01-01 00:00:00     <Dir> logs
1980-01-01 00:00:00     <Dir> widgets

Free Space: 18773504 bytes


C:\>

C:\phoenix\>

1980-01-01 00:00:00     <Dir> .

Free Space: 18773504 bytes


C:\phoenix\>

C:\>

C:\dev\>

1980-01-01 00:00:00     <Dir> .

Free Space: 18773504 bytes


C:\dev\>

C:\>

1980-01-01 00:00:00     <Dir> tmp
1980-01-01 00:00:00     <Dir> dev
1980-01-01 00:00:00     <Dir> phoenix
1980-01-01 00:00:00     <Dir> documents
1980-01-01 00:00:00     <Dir> logs
1980-01-01 00:00:00     <Dir> widgets

Free Space: 18773504 bytes


C:\>

C:\tmp\>

1980-01-01 00:00:00     <Dir> .

Free Space: 18773504 bytes


C:\tmp\>

C:\>

C:\documents\>

1980-01-01 00:00:00     <Dir> .

Free Space: 18773504 bytes


C:\documents\>

C:\>

1980-01-01 00:00:00     <Dir> tmp
1980-01-01 00:00:00     <Dir> dev
1980-01-01 00:00:00     <Dir> phoenix
1980-01-01 00:00:00     <Dir> documents
1980-01-01 00:00:00     <Dir> logs
1980-01-01 00:00:00     <Dir> widgets

Free Space: 18773504 bytes


C:\>

Error = -3024

C:\>
Command not found!

C:\>

C:\logs\>

1980-01-01 00:00:00     <Dir> .

Free Space: 18773504 bytes


C:\logs\>

C:\>

C:\widgets\>

1980-01-01 00:00:00     <Dir> .

Free Space: 18773504 bytes


C:\widgets\>

C:\>

1980-01-01 00:00:00     <Dir> tmp
1980-01-01 00:00:00     <Dir> dev
1980-01-01 00:00:00     <Dir> phoenix
1980-01-01 00:00:00     <Dir> documents
1980-01-01 00:00:00     <Dir> logs
1980-01-01 00:00:00     <Dir> widgets

Free Space: 18773504 bytes


C:\>


There are interesting folders, but nothing inside apparently...

1483
Other Calculators / Re: The 1st step into CAS+ flashing
« on: March 17, 2011, 08:56:24 pm »
I can enter commands on my oldest CAS+.
Tried "dir", "ls" and things like that, but only got things like:

Code: [Select]
A:Ôœ‘dœ‘—">01 00:00:50.000 0 | Initializing xmlrpc library


A:Ôœ‘dœ‘—">

A:Ôœ‘dœ‘—">
Command not found!

A:Ôœ‘dœ‘—">
Command not found!

A:Ôœ‘dœ‘—">
Command not found!

A:Ôœ‘dœ‘—">

Error = -1

A:Ôœ‘dœ‘—">

Error = -1

A:Ôœ‘dœ‘—">

What should I type?

1484
Other Calculators / Re: The 1st step into CAS+ flashing
« on: March 17, 2011, 07:29:30 pm »
critor,
Try the key sequence to bring up the diags menu.
You indicated nothing happened  on another post, and you had to reboot.
Does this bring up the Datalight shell ?

No... The calculator just does not turn on and I have to remove the batteries.
Note according to the above log, there is no valid diags image on this CAS+.


But, I've managed to get the boot log of 2 rare older CAS+ prototypes (loan from DataMath.org).

You should have a look as it could help us to understand more on the CAS+, and to dump them some day.

Boot1/Boot2 1.0.491 (2006/7/26):
Code: [Select]
Boot Loader Stage 1 (1.0.491)
Build: 2006/7/26, 5:55:51
Copyright (c) 2006 Texas Instruments Incorporated

Last boot progress: 10600

System clock:        78 MHZ
SDRAM memory test:   Pass
Clearing SDRAM...Done.
Clearing SDRAM...Done.
Clearing SDRAM...Done.
Checking for NAND: NAND Flash ID: ST Micro NAND256W3A

Loading DIAGS software...

Error reading/validating DIAGS image

Loading BOOT2 software...

99%
BOOT1: loading complete (933 ticks), launching image.



Boot Loader Stage 2 (1.0.491)
Build: 2006/7/26, 5:59:39
Copyright (c) 2006 Texas Instruments Incorporated



Initializing graphics subsystem.
Checking for NAND: NAND Flash ID: ST Micro NAND256W3A
Initializing USB and networking.


Initializing filesystem.
Datalight Reliance v2.00.0451
Copyright (c) 2003 - 2005 Datalight, Inc.
Registered to #9DE08703
FlashFX sample project for the OMAP5912 OSK running Nucleus
Datalight FlashFX Pro v2.0 Build 966
Nucleus Edition for ARM9
Copyright (c) 1993-2005 Datalight, Inc.
Patents: US#5860082, US#6260156.
Detected FfxDelay() parameters: Count=58353 MicroSec=8192 Shift=13
FFX: NAND chip manufacturer: ST Micro (20) chip NAND256W3A (75)
Filesystem ready.

Loading Operating System...

100%

BOOT2: loading complete (3036 ticks), launching image.


Beginning system initialization.
Preparing file system...
Datalight Reliance v2.00.0451
Copyright (c) 2003 - 2005 Datalight, Inc.
Registered to #9DE08703
FlashFX sample project for the OMAP5912 OSK running Nucleus
Datalight FlashFX Pro v2.0 Build 966
Nucleus Edition for ARM9
Copyright (c) 1993-2005 Datalight, Inc.
Patents: US#5860082, US#6260156.
Detected FfxDelay() parameters: Count=60132 MicroSec=8192 Shift=13
FFX: NAND chip manufacturer: ST Micro (20) chip NAND256W3A (75)
File system ready.

phoenix dhcp server w/ VOODOO  built 12-Jul-2006 (start at 559)


phoenix enum server  built 12-Jul-2006


phoenix dhcp hook fwd w/ VOODOO  built 12-Jul-2006 (start at 559)

System build date: Jul 27 2006, 05:55:34
Available memory: 25789100 bytes
Launching system...

phoenix file mgt server  built 12-Jul-2006 (start at 659)

pn-srv2-632: pol_init = 0
It seems similar, although the developer/production keys aren't mentionned this time.


And the oldest known CAS+ prototype with boot1/boot2 built on Feb 27 2006:
Code: [Select]
Boot Loader Stage 1
Build: Feb 27 2006, 18:04:35
Copyright (c) 2006 Texas Instruments Incorporated

System clock:        78 MHZ
SDRAM memory test:
Data   (ticks=0)
Addr   (ticks=1)
Fill   (ticks=5)
Test   (ticks=11)
Pass (ticks=17)
Checking for NAND: NAND Flash ID: ST Micro NAND256W3A

Launching BOOT2 software...

100%
BOOT1 complete.



Boot Loader Stage 2
Build: Feb 27 2006, 18:06:34
Copyright (c) 2006 Texas Instruments Incorporated



Initializing graphics subsystem.
NAND Flash ID: ST Micro NAND256W3A


Initializing filesystem.
Datalight Reliance v2.00.0451
Copyright (c) 2003 - 2005 Datalight, Inc.
Registered to #9DE08703
FlashFX sample project for the OMAP5912 OSK running Nucleus
Datalight FlashFX Pro v2.0 Build 966
Nucleus Edition for ARM9
Copyright (c) 1993-2005 Datalight, Inc.
Patents: US#5860082, US#6260156.
Detected FfxDelay() parameters: Count=59276 MicroSec=8192 Shift=13
FFX: NAND chip manufacturer: ST Micro (20) chip NAND256W3A (75)
FlashFX SDK License ID #57363077
Filesystem ready.
100%


Beginning system initialization.
Preparing file system...
Datalight Reliance v2.00.0451
Copyright (c) 2003 - 2005 Datalight, Inc.
Registered to #9DE08703
FlashFX sample project for the OMAP5912 OSK running Nucleus
Datalight FlashFX Pro v2.0 Build 966
Nucleus Edition for ARM9
Copyright (c) 1993-2005 Datalight, Inc.
Patents: US#5860082, US#6260156.
Detected FfxDelay() parameters: Count=59365 MicroSec=8192 Shift=13
FFX: NAND chip manufacturer: ST Micro (20) chip NAND256W3A (75)
FlashFX SDK License ID #57363077
File system ready.
Unpacking data...
Creating directory phoenix
Unpacking file phoenix/components
Creating directory phoenix/ctlg
Unpacking file phoenix/ctlg/CtrlCtlg.sav
Creating directory phoenix/ctlg/locales
Creating directory phoenix/ctlg/locales/da
Unpacking file phoenix/ctlg/locales/da/strings.res
Creating directory phoenix/ctlg/locales/de
Unpacking file phoenix/ctlg/locales/de/strings.res
Creating directory phoenix/ctlg/locales/en
Unpacking file phoenix/ctlg/locales/en/2dtemplates.res
Unpacking file phoenix/ctlg/locales/en/all.res
Unpacking file phoenix/ctlg/locales/en/math.res
Unpacking file phoenix/ctlg/locales/en/strings.res
Unpacking file phoenix/ctlg/locales/en/units.res
Creating directory phoenix/ctlg/locales/fr
Unpacking file phoenix/ctlg/locales/fr/strings.res
Creating directory phoenix/ctlg/locales/it
Unpacking file phoenix/ctlg/locales/it/strings.res
Creating directory phoenix/ctlg/locales/no
Unpacking file phoenix/ctlg/locales/no/strings.res
Unpacking file phoenix/ctlg/NormCtlg.sav
Creating directory phoenix/dcol
Creating directory phoenix/dcol/locales
Creating directory phoenix/dcol/locales/da
Unpacking file phoenix/dcol/locales/da/strings.res
Creating directory phoenix/dcol/locales/de
Unpacking file phoenix/dcol/locales/de/strings.res
Creating directory phoenix/dcol/locales/en
Unpacking file phoenix/dcol/locales/en/icons.res
pn-srv6-423: nuc_init usb
Unpacking file phoenix/dcol/locales/en/strings.res
Creating directory phoenix/dcol/locales/fr
Unpacking file phoenix/dcol/locales/fr/strings.res
Creating directory phoenix/dcol/locales/it
Unpacking file phoenix/dcol/locales/it/strings.res
Creating directory phoenix/dcol/locales/no
Unpacking file phoenix/dcol/locales/no/strings.res
Creating directory phoenix/dlog
Creating directory phoenix/dlog/locales
Creating directory phoenix/dlog/locales/da
Unpacking file phoenix/dlog/locales/da/strings.res
Creating directory phoenix/dlog/locales/de
Unpacking file phoenix/dlog/locales/de/strings.res
Creating directory phoenix/dlog/locales/en
Unpacking file phoenix/dlog/locales/en/strings.res
Creating directory phoenix/dlog/locales/fr
Unpacking file phoenix/dlog/locales/fr/strings.res
Creating directory phoenix/dlog/locales/it
Unpacking file phoenix/dlog/locales/it/strings.res
Creating directory phoenix/dlog/locales/no
Unpacking file phoenix/dlog/locales/no/strings.res
Creating directory phoenix/geog
Creating directory phoenix/geog/locales
Creating directory phoenix/geog/locales/da
Unpacking file phoenix/geog/locales/da/strings.res
Creating directory phoenix/geog/locales/de
Unpacking file phoenix/geog/locales/de/strings.res
Creating directory phoenix/geog/locales/en
Unpacking file phoenix/geog/locales/en/icons.res
pn-srv6-431: nuc_init net
Unpacking file phoenix/geog/locales/en/strings.res
Creating directory phoenix/geog/locales/fr
Unpacking file phoenix/geog/locales/fr/strings.res
Creating directory phoenix/geog/locales/it
Unpacking file phoenix/geog/locales/it/strings.res
Creating directory phoenix/geog/locales/no
Unpacking file phoenix/geog/locales/no/strings.res
Creating directory phoenix/math
Creating directory phoenix/math/locales
Creating directory phoenix/math/locales/da
Unpacking file phoenix/math/locales/da/strings.res
pn-srv6-444: nuc_init dev N=1
Creating directory phoenix/math/locales/de
Unpacking file phoenix/math/locales/de/strings.res
Creating directory phoenix/math/locales/en
Unpacking file phoenix/math/locales/en/strings.res
Creating directory phoenix/math/locales/fr
Unpacking file phoenix/math/locales/fr/strings.res
Creating directory phoenix/math/locales/it
Unpacking file phoenix/math/locales/it/strings.res
Creating directory phoenix/math/locales/no
Unpacking file phoenix/math/locales/no/strings.res
Creating directory phoenix/ntpd
Creating directory phoenix/ntpd/locales
Creating directory phoenix/ntpd/locales/da
Unpacking file phoenix/ntpd/locales/da/strings.res
Creating directory phoenix/ntpd/locales/de
Unpacking file phoenix/ntpd/locales/de/strings.res
Creating directory phoenix/ntpd/locales/en
Unpacking file phoenix/ntpd/locales/en/icons.res
Unpacking file phoenix/ntpd/locales/en/strings.res
Creating directory phoenix/ntpd/locales/fr
Unpacking file phoenix/ntpd/locales/fr/strings.res
Creating directory phoenix/ntpd/locales/it
Unpacking file phoenix/ntpd/locales/it/strings.res
Creating directory phoenix/ntpd/locales/no
Unpacking file phoenix/ntpd/locales/no/strings.res
Creating directory phoenix/scpd
Creating directory phoenix/scpd/locales
Creating directory phoenix/scpd/locales/da
Unpacking file phoenix/scpd/locales/da/strings.res
Creating directory phoenix/scpd/locales/de
Unpacking file phoenix/scpd/locales/de/strings.res
Creating directory phoenix/scpd/locales/en
Unpacking file phoenix/scpd/locales/en/icons.res
Unpacking file phoenix/scpd/locales/en/strings.res
Creating directory phoenix/scpd/locales/fr
Unpacking file phoenix/scpd/locales/fr/strings.res
Creating directory phoenix/scpd/locales/it
Unpacking file phoenix/scpd/locales/it/strings.res
Creating directory phoenix/scpd/locales/no
Unpacking file phoenix/scpd/locales/no/strings.res
Creating directory phoenix/syst
Unpacking file phoenix/syst/localenames
Creating directory phoenix/syst/locales
Creating directory phoenix/syst/locales/da
Unpacking file phoenix/syst/locales/da/dialogs.res
Unpacking file phoenix/syst/locales/da/imechars.res
Creating directory phoenix/syst/locales/da/sampledocuments
Unpacking file phoenix/syst/locales/da/sampledocuments/Kom godt i gang.tns
Creating directory phoenix/syst/locales/da/settings
Unpacking file phoenix/syst/locales/da/settings/factory.zip
Unpacking file phoenix/syst/locales/da/strings.res
Creating directory phoenix/syst/locales/de
Unpacking file phoenix/syst/locales/de/dialogs.res
Unpacking file phoenix/syst/locales/de/imechars.res
Creating directory phoenix/syst/locales/de/sampledocuments
Unpacking file phoenix/syst/locales/de/sampledocuments/Erste Schritte.tns
Creating directory phoenix/syst/locales/de/settings
Unpacking file phoenix/syst/locales/de/settings/factory.zip
Unpacking file phoenix/syst/locales/de/strings.res
Creating directory phoenix/syst/locales/en
Unpacking file phoenix/syst/locales/en/dialogs.res
Unpacking file phoenix/syst/locales/en/icons.res
Unpacking file phoenix/syst/locales/en/imechars.res
Creating directory phoenix/syst/locales/en/sampledocuments
Unpacking file phoenix/syst/locales/en/sampledocuments/Getting Started.tns
Creating directory phoenix/syst/locales/en/settings
Unpacking file phoenix/syst/locales/en/settings/factory.zip
Unpacking file phoenix/syst/locales/en/strings.res
Creating directory phoenix/syst/locales/fr
Unpacking file phoenix/syst/locales/fr/dialogs.res
Unpacking file phoenix/syst/locales/fr/imechars.res
Creating directory phoenix/syst/locales/fr/sampledocuments
Unpacking file phoenix/syst/locales/fr/sampledocuments/Prise en main rapide.tns
Creating directory phoenix/syst/locales/fr/settings
Unpacking file phoenix/syst/locales/fr/settings/factory.zip
Unpacking file phoenix/syst/locales/fr/strings.res
Creating directory phoenix/syst/locales/it
Unpacking file phoenix/syst/locales/it/dialogs.res
Unpacking file phoenix/syst/locales/it/imechars.res
Creating directory phoenix/syst/locales/it/sampledocuments
Unpacking file phoenix/syst/locales/it/sampledocuments/Guida introduttiva.tns
Creating directory phoenix/syst/locales/it/settings
Unpacking file phoenix/syst/locales/it/settings/factory.zip
Unpacking file phoenix/syst/locales/it/strings.res
Creating directory phoenix/syst/locales/no
Unpacking file phoenix/syst/locales/no/dialogs.res
Unpacking file phoenix/syst/locales/no/imechars.res
Creating directory phoenix/syst/locales/no/sampledocuments
Unpacking file phoenix/syst/locales/no/sampledocuments/Komme i gang.tns
Creating directory phoenix/syst/locales/no/settings
Unpacking file phoenix/syst/locales/no/settings/factory.zip
Unpacking file phoenix/syst/locales/no/strings.res
Creating directory phoenix/syst/settings
Creating directory phoenix/tblt
Creating directory phoenix/tblt/locales
Creating directory phoenix/tblt/locales/da
Unpacking file phoenix/tblt/locales/da/dialogs.res
Unpacking file phoenix/tblt/locales/da/strings.res
Creating directory phoenix/tblt/locales/de
Unpacking file phoenix/tblt/locales/de/dialogs.res
Unpacking file phoenix/tblt/locales/de/icons.res
Unpacking file phoenix/tblt/locales/de/strings.res
Creating directory phoenix/tblt/locales/en
Unpacking file phoenix/tblt/locales/en/dialogs.res
Unpacking file phoenix/tblt/locales/en/icons.res
Unpacking file phoenix/tblt/locales/en/strings.res
Creating directory phoenix/tblt/locales/fr
Unpacking file phoenix/tblt/locales/fr/dialogs.res
Unpacking file phoenix/tblt/locales/fr/strings.res
Creating directory phoenix/tblt/locales/it
Unpacking file phoenix/tblt/locales/it/dialogs.res
Unpacking file phoenix/tblt/locales/it/strings.res
Creating directory phoenix/tblt/locales/no
Unpacking file phoenix/tblt/locales/no/dialogs.res
Unpacking file phoenix/tblt/locales/no/strings.res
Finished unpacking.
System build date: May  1 2006, 15:15:42
Launching system...

Datalight Command Shell for Nucleus

A:�‘¤œ‘̘">

This one seems much different.
It's running the antic OS 1.0.1.0.334T built on May 1 2006.

* Note the OS seems to be unpacked at each boot.

* Note there is no DHCP messages this time. I cannot exchange data through USB, neither with the Computer Link 1.0 (it doesn't find the calculator, and the network CAS+ interface is failing getting an IP), neither with other CAS+ calculators (no error message, the "Send" menu item seems to be "fake"...)

* Strangely, a phoenix directory is mentionned, although it is not visible on later CAS+ which are only listing the following folders:
/
/phx
/phx/documents
/phx/tmp

* Where is the OS? There's nothing in the above folders (except /phx/documents), but the file system capacity is 27.8Mb, and more than 5Mb are used...
- Hidden directories?
- Something related to the bad blocks reported in previous logs?

* At the end of this last boot, Datalight shell is mentionned, and I'm getting something which could look like a prompt, although I'm in the (very buggy) OS, and although I didn't press any special key.


Goplat, Bsl, everybody... At this point, your guess can be as good as mine.
We might succeed at flashing/dumping, but it will be together.

Thanks for reading.

1485
Other Calculators / Re: The 1st step into CAS+ flashing
« on: March 17, 2011, 03:26:50 pm »
The debug interface had allready been unlocked (check HackSpire), but never on a TI-Nspire CAS+ to my knowledge.

As far as I know, this only lets you reflash:
- the OS
- the boot2
- the diags software

It seems boot1 can be reflashed, but only through the diags software.

Pages: 1 ... 97 98 [99] 100 101 ... 137