Author Topic: The 1st step into CAS+ flashing  (Read 29164 times)

0 Members and 9 Guests are viewing this topic.

Offline Goplat

  • LV5 Advanced (Next: 300)
  • *****
  • Posts: 289
  • Rating: +82/-0
    • View Profile
Re: The 1st step into CAS+ flashing
« Reply #15 on: March 17, 2011, 09:10:32 pm »
Actually, this is a command shell bug that shows up even on the production TI-Nspire - directories appear empty even when they're not.

Anyway, check if you can use the TYPE command to dump a file.
« Last Edit: March 17, 2011, 09:11:12 pm by Goplat »
Numquam te deseram; numquam te deficiam; numquam circa curram et te desolabo
Numquam te plorare faciam; numquam valedicam; numquam mendacium dicam et te vulnerabo

Offline bsl

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 157
  • Rating: +14/-0
    • View Profile
Re: The 1st step into CAS+ flashing
« Reply #16 on: March 17, 2011, 09:15:31 pm »
Now extend Goplat's earlier idea:
copy /phoenix/install/TI-Nspire.tnc /phx/documents/examples/OS.tns
and transfer through USB :)

or something similar

Offline critor

  • Editor
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2079
  • Rating: +439/-13
    • View Profile
    • TI-Planet
Re: The 1st step into CAS+ flashing
« Reply #17 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...
TI-Planet co-admin.

Offline JonimusPrime

  • LV6 Super Member (Next: 500)
  • ******
  • Posts: 389
  • Rating: +25/-5
    • View Profile
    • Jonimoose.net
Re: The 1st step into CAS+ flashing
« Reply #18 on: March 17, 2011, 09:17:50 pm »
PK is part of the zip file header so that is expected with a zip.

"Always code as if the person who will maintain your code is a maniac serial killer that knows where you live" -Unknown

"If you've done something right no one will know that you've done anything at all" -Futurama

"Have a nice day, or not, the choice is yours." Tom Steiner

Offline critor

  • Editor
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2079
  • Rating: +439/-13
    • View Profile
    • TI-Planet
Re: The 1st step into CAS+ flashing
« Reply #19 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...)
TI-Planet co-admin.

Offline ztrumpet

  • The Rarely Active One
  • CoT Emeritus
  • LV13 Extreme Addict (Next: 9001)
  • *
  • Posts: 5712
  • Rating: +364/-4
  • If you see this, send me a PM. Just for fun.
    • View Profile
Re: The 1st step into CAS+ flashing
« Reply #20 on: March 17, 2011, 09:25:26 pm »
Oh, this looks cool.  Great job, critor, Goplat, and bsl. :D

Offline critor

  • Editor
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2079
  • Rating: +439/-13
    • View Profile
    • TI-Planet
Re: The 1st step into CAS+ flashing
« Reply #21 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?
« Last Edit: March 17, 2011, 09:32:19 pm by critor »
TI-Planet co-admin.

Offline Goplat

  • LV5 Advanced (Next: 300)
  • *****
  • Posts: 289
  • Rating: +82/-0
    • View Profile
Re: The 1st step into CAS+ flashing
« Reply #22 on: March 17, 2011, 09:46:33 pm »
I just checked out the type command in the current boot2 - it reads 1023 bytes at at a time, and prints using printf, so if the file has any 00 bytes it'll lose data. :(! Stupid Datalight programmers. They didn't even do printf("%s", buffer), they did printf(buffer), so if there are %s's in the file it'll likely crash (this is not exploitable, unfortunately).
Numquam te deseram; numquam te deficiam; numquam circa curram et te desolabo
Numquam te plorare faciam; numquam valedicam; numquam mendacium dicam et te vulnerabo

Offline critor

  • Editor
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2079
  • Rating: +439/-13
    • View Profile
    • TI-Planet
Re: The 1st step into CAS+ flashing
« Reply #23 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+...
TI-Planet co-admin.

Offline bsl

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 157
  • Rating: +14/-0
    • View Profile
Re: The 1st step into CAS+ flashing
« Reply #24 on: March 17, 2011, 10:19:00 pm »
I may be leading you astray
try +++ at the hyperterminal prompt
you might start xmodem transfer.

Offline critor

  • Editor
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2079
  • Rating: +439/-13
    • View Profile
    • TI-Planet
Re: The 1st step into CAS+ flashing
« Reply #25 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... :(
TI-Planet co-admin.

Offline critor

  • Editor
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2079
  • Rating: +439/-13
    • View Profile
    • TI-Planet
Re: The 1st step into CAS+ flashing
« Reply #26 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?
TI-Planet co-admin.

Offline bsl

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 157
  • Rating: +14/-0
    • View Profile
Re: The 1st step into CAS+ flashing
« Reply #27 on: March 17, 2011, 10:42:02 pm »
FlashFxDump of course. :)
Do this first:
FlashFxDump /?
Then go from there
« Last Edit: March 17, 2011, 10:42:23 pm by bsl »

Offline critor

  • Editor
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2079
  • Rating: +439/-13
    • View Profile
    • TI-Planet
Re: The 1st step into CAS+ flashing
« Reply #28 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:/..." ?
« Last Edit: March 18, 2011, 06:13:20 am by critor »
TI-Planet co-admin.

Offline ExtendeD

  • CoT Emeritus
  • LV8 Addict (Next: 1000)
  • *
  • Posts: 825
  • Rating: +167/-2
    • View Profile
Re: The 1st step into CAS+ flashing
« Reply #29 on: March 18, 2011, 08:31:03 am »
Maybe you could try to brute force the interface to find out the different commands.
Scripting this shouldn't be too difficult.
Ndless.me with the finest TI-Nspire programs