« previous next »
Pages: [1]   Go Down

Author Topic: TiLP problem  (Read 6123 times)

0 Members and 1 Guest are viewing this topic.

Offline Deathrider

  • LV1 Newcomer (Next: 20)
  • *
  • Posts: 13
  • Rating: +0/-0
    • View Profile
TiLP problem
« on: March 05, 2013, 09:22:30 am »
Some years ago I have written some programs for the TI-86. They are about Controls Theory and Bode, Nyquist e Nichols diagrams and can be found on my page:
http://digilander.libero.it/deathrider/calcolatrici/ti/ti_86.html

At the time I have trasferred it with TiLP and uploaded on the host ftp. Now I want to transfer them on the TI-86, so I have downloaded them but TiLP refuse to transfer!!!

Is there someone who have idea of the problem?
Is there someone who can try to do the transfer?
Logged

Offline Lionel Debroux

  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2135
  • Rating: +290/-45
    • View Profile
    • TI-Chess Team
Re: TiLP problem
« Reply #1 on: March 05, 2013, 09:31:54 am »
Quote
Is there someone who have idea of the problem?
Well, you forgot to mention all of:
* the computer OS flavor;
* the computer OS version;
* the TILP version;
* the cable model you're using;
* an error message more precise than "TiLP refuse to transfer", if any.
Without such information, even the most hardened TILP users, or the TILP contributors and maintainers, cannot hazard a reasonable guess :)
TIA for providing those pieces of information ;)

Quote
Is there someone who can try to do the transfer?
I can, but not right now.
« Last Edit: March 05, 2013, 09:47:56 am by Lionel Debroux »
Logged
Member of the TI-Chess Team.
Co-maintainer of GCC4TI (GCC4TI online documentation), TILP and TIEmu.
Co-admin of TI-Planet.

Offline Deathrider

  • LV1 Newcomer (Next: 20)
  • *
  • Posts: 13
  • Rating: +0/-0
    • View Profile
Re: TiLP problem
« Reply #2 on: March 05, 2013, 03:51:07 pm »
When I uploaded the files, I was using TiLP under a Linux with a serial RS232 cable. I do not remember the versions. Now I am using Windows7 with the latest TiLP version available for Windows (1.15) and a usb silver link cable. When I try to transfer my files it do not show a message. It simply do nothing. But I have test the transfer with another file: I downloaded "Blinded by the dark" game and it works really nice. I can even take screen captures. I suspect it is a problem in file format due to the transfer to/from the server: i remember that there are some differences between binary transfer and text transfer, ftp protocol and http protocol. I am investigating about this but not really sure.

PS: only now I realized that you are the developer of TiLP!!! Really thanks for your work!!
« Last Edit: March 05, 2013, 03:56:58 pm by Deathrider »
Logged

Offline Lionel Debroux

  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2135
  • Rating: +290/-45
    • View Profile
    • TI-Chess Team
Re: TiLP problem
« Reply #3 on: March 06, 2013, 01:42:44 am »
Quote
Now I am using Windows7 with the latest TiLP version available for Windows (1.15)
The latest release is 1.16, but it's more than a year old, and newer Windows builds with fixes and improvements are available, the newest one being http://ourl.ca/4010/332033 ;)

I haven't tried your files with my 86 (TILP HEAD, under Linux) yet.
Logged
Member of the TI-Chess Team.
Co-maintainer of GCC4TI (GCC4TI online documentation), TILP and TIEmu.
Co-admin of TI-Planet.

Offline Deathrider

  • LV1 Newcomer (Next: 20)
  • *
  • Posts: 13
  • Rating: +0/-0
    • View Profile
Re: TiLP problem
« Reply #4 on: March 06, 2013, 03:09:39 am »
I have upgraded to latest version. There are some problems with menus that do not appear. Not really important, I am able to try the transfer but it do not work. What appens is the same as the previous version: no message, no transfer. At the second or third try, the program will abort.

Logged

Offline Lionel Debroux

  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2135
  • Rating: +290/-45
    • View Profile
    • TI-Chess Team
Re: TiLP problem
« Reply #5 on: March 06, 2013, 05:12:01 am »
Heh, I've been fixing a number of crash-inducing bugs, but seemingly, more occur :)

Could you attach the ~/.tilp.log file generated by TILP II 1.16 onwards ? If there's no such file, it might be due to Windows not storing the file upon a crash, so try to exit the program before it crashes. TIA.
(~ refers to your home directory, i.e. probably C:\Users\<your username>).
Logged
Member of the TI-Chess Team.
Co-maintainer of GCC4TI (GCC4TI online documentation), TILP and TIEmu.
Co-admin of TI-Planet.

Offline Deathrider

  • LV1 Newcomer (Next: 20)
  • *
  • Posts: 13
  • Rating: +0/-0
    • View Profile
Re: TiLP problem
« Reply #6 on: March 06, 2013, 05:55:23 am »
Here it is:

TiLP2 - Version 1.17, (C) 1999-2008 Romain Lievin
THIS PROGRAM COMES WITH ABSOLUTELY NO WARRANTY
PLEASE READ THE DOCUMENTATION FOR DETAILS
built on Dec 31 2012 10:55:16
tilp-INFO: setlocale: Italian_Italy.1252
tilp-INFO: bindtextdomain: C:\Program Files (x86)\TiLP\locale\
tilp-INFO: textdomain: tilp2
ticables-INFO: ticables library version 1.3.4
ticables-INFO: setlocale: Italian_Italy.1252
ticables-INFO: bindtextdomain: C:\Program Files (x86)\Common Files\LPG Shared\libs\..\share\locale
ticables-INFO: textdomain: tilp2
tifiles-INFO: tifiles library version 1.1.6
tifiles-INFO: setlocale: Italian_Italy.1252
tifiles-INFO: bindtextdomain: C:\Program Files (x86)\Common Files\LPG Shared\libs\..\share\locale
tifiles-INFO: textdomain: tilp2
ticalcs-INFO: ticalcs library version 1.1.8
ticalcs-INFO: setlocale: Italian_Italy.1252
ticalcs-INFO: bindtextdomain: C:\Program Files (x86)\Common Files\LPG Shared\libs\..\share\locale
ticalcs-INFO: textdomain: tilp2
tilp-INFO: Searching for link cables...
ticables-INFO: Link cable probing:
ticables-INFO:  found TI-GRAPH LINK USB on #1, version <2.08>
tilp-INFO: Searching for handhelds on DirectLink...
ticables-INFO:  found TI-GRAPH LINK USB on #1, version <2.08>
ticables-INFO: found bulk in endpoint 0x81

ticables-INFO: found bulk out endpoint 0x02

ticables-INFO:  found TI-GRAPH LINK USB on #1, version <2.08>
tilp-INFO: Searching for handhelds on SilverLink...
ticables-INFO:  found TI-GRAPH LINK USB on #1, version <2.08>
ticables-INFO: found bulk in endpoint 0x81

ticables-INFO: found bulk out endpoint 0x02

ticalcs-INFO: Check for TIXX...
ticalcs-INFO:  PC->TI: RDY?
ticalcs-INFO:  TI->PC: ACK
ticalcs-INFO:  PC->TI: RDY?
ticalcs-INFO:  TI->PC: ACK
ticalcs-INFO: Check for TI9X...
ticalcs-INFO: Requesting version infos:
ticalcs-INFO:  PC->TI: VER
tilp-INFO: Opening cable SilverLink on port #1 to communicate with calculator TI86
ticables-INFO:  found TI-GRAPH LINK USB on #1, version <2.08>
ticables-INFO: found bulk in endpoint 0x81

ticables-INFO: found bulk out endpoint 0x02

ticables-INFO:  found TI-GRAPH LINK USB on #1, version <2.08>
ticables-INFO: found bulk in endpoint 0x81

ticables-INFO: found bulk out endpoint 0x02

ticalcs-INFO: Checking hand-held status:
ticalcs-INFO: Requesting folder & vars & apps listing:
ticalcs-INFO:  PC->TI: REQ (size=0x0000, id=15, name=)
ticalcs-INFO:  TI->PC: ACK
ticalcs-INFO:  TI->PC: XDP (0003 bytes)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x0002, id=04, name=xStat)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x0002, id=04, name=yStat)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x0002, id=04, name=fStat)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x0006, id=2A, name=y1)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x000A, id=00, name=y)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x000A, id=00, name=x)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x02B4, id=12, name=ROMDump)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x3A2D, id=0C, name=blind)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x5E4E, id=0C, name=blmap)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x1017, id=12, name=bload)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x00CC, id=0C, name=qiksave)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO: Requesting RAM & FLASH free
ticalcs-INFO:  PC->TI: REQ (size=0x0000, id=15, name=)
ticalcs-INFO:  TI->PC: ACK
ticalcs-INFO:  TI->PC: XDP (0003 bytes)
ticalcs-INFO:  PC->TI: EOT
ticalcs-INFO: Checking hand-held status:
ticalcs-INFO: Requesting folder & vars & apps listing:
ticalcs-INFO:  PC->TI: REQ (size=0x0000, id=15, name=)
ticalcs-INFO:  TI->PC: ACK
ticalcs-INFO:  TI->PC: XDP (0003 bytes)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x0002, id=04, name=xStat)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x0002, id=04, name=yStat)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x0002, id=04, name=fStat)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x0006, id=2A, name=y1)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x000A, id=00, name=y)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x000A, id=00, name=x)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x02B4, id=12, name=ROMDump)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x3A2D, id=0C, name=blind)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x5E4E, id=0C, name=blmap)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x1017, id=12, name=bload)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  TI->PC: VAR (size=0x00CC, id=0C, name=qiksave)
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO:  PC->TI: ACK
ticalcs-INFO: Requesting RAM & FLASH free
ticalcs-INFO:  PC->TI: REQ (size=0x0000, id=15, name=)
ticalcs-INFO:  TI->PC: ACK
ticalcs-INFO:  TI->PC: XDP (0003 bytes)
ticalcs-INFO:  PC->TI: EOT
Error 1
+------------------+----------+----+----+----------+----------+
| B. name          | T. name  |Attr|Type| Size     | Folder   |
+------------------+----------+----+----+----------+----------+
| 0000000000000000 |     Func |  0 | 17 | 00000000 |          |
| 0000000000000000 |      Pol |  0 | 18 | 00000000 |          |
| 0000000000000000 |    Param |  0 | 19 | 00000000 |          |
| 0000000000000000 |    DifEq |  0 | 1A | 00000000 |          |
| 0000000000000000 |     ZRCL |  0 | 1B | 00000000 |          |
| 7853746174000000 |    xStat |  0 | 04 | 00000002 |          |
| 7953746174000000 |    yStat |  0 | 04 | 00000002 |          |
| 6653746174000000 |    fStat |  0 | 04 | 00000002 |          |
| 7931000000000000 |       y1 |  0 | 2A | 00000006 |          |
| 7900000000000000 |        y |  0 | 00 | 0000000A |          |
| 7800000000000000 |        x |  0 | 00 | 0000000A |          |
| 524F4D44756D7000 |  ROMDump |  0 | 12 | 000002B4 |          |
| 626C696E64000000 |    blind |  0 | 0C | 00003A2D |          |
| 626C6D6170000000 |    blmap |  0 | 0C | 00005E4E |          |
| 626C6F6164000000 |    bload |  0 | 12 | 00001017 |          |
| 71696B7361766500 |  qiksave |  0 | 0C | 000000CC |          |
+------------------+----------+----+----+----------+----------+
+------------------+----------+----+----+----------+----------+
| B. name          | T. name  |Attr|Type| Size     | Folder   |
+------------------+----------+----+----+----------+----------+
| No applications  |
+------------------+----------+----+----+----------+----------+
+------------------+----------+----+----+----------+----------+
| B. name          | T. name  |Attr|Type| Size     | Folder   |
+------------------+----------+----+----+----------+----------+
| 0000000000000000 |     Func |  0 | 17 | 00000000 |          |
| 0000000000000000 |      Pol |  0 | 18 | 00000000 |          |
| 0000000000000000 |    Param |  0 | 19 | 00000000 |          |
| 0000000000000000 |    DifEq |  0 | 1A | 00000000 |          |
| 0000000000000000 |     ZRCL |  0 | 1B | 00000000 |          |
| 7853746174000000 |    xStat |  0 | 04 | 00000002 |          |
| 7953746174000000 |    yStat |  0 | 04 | 00000002 |          |
| 6653746174000000 |    fStat |  0 | 04 | 00000002 |          |
| 7931000000000000 |       y1 |  0 | 2A | 00000006 |          |
| 7900000000000000 |        y |  0 | 00 | 0000000A |          |
| 7800000000000000 |        x |  0 | 00 | 0000000A |          |
| 524F4D44756D7000 |  ROMDump |  0 | 12 | 000002B4 |          |
| 626C696E64000000 |    blind |  0 | 0C | 00003A2D |          |
| 626C6D6170000000 |    blmap |  0 | 0C | 00005E4E |          |
| 626C6F6164000000 |    bload |  0 | 12 | 00001017 |          |
| 71696B7361766500 |  qiksave |  0 | 0C | 000000CC |          |
+------------------+----------+----+----+----------+----------+
+------------------+----------+----+----+----------+----------+
| B. name          | T. name  |Attr|Type| Size     | Folder   |
+------------------+----------+----+----+----------+----------+
| No applications  |
+------------------+----------+----+----+----------+----------+
Error 1
« Last Edit: March 06, 2013, 06:12:14 am by Deathrider »
Logged

Offline Deathrider

  • LV1 Newcomer (Next: 20)
  • *
  • Posts: 13
  • Rating: +0/-0
    • View Profile
Re: TiLP problem
« Reply #7 on: March 06, 2013, 11:52:12 am »
I made this:

1) Downloaded from calculator the file ROMDump.86p.
2) Opened my file CA86.86p with a hex editor.
3) Opened file ROMDump.86p with a hex editor.
4) Copied first 61 bytes (from offset 0x00 to 0x3C included) from ROMDump.86p to CA86.86p.
5) Transferred CA86.86p to calculator.

Coping the "header" of a file makes the transfer possible but executing the program on the calculator produces only errors. Probably the problem is related to compatibility with older versions of TiLP??
Logged

Offline Lionel Debroux

  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2135
  • Rating: +290/-45
    • View Profile
    • TI-Chess Team
Re: TiLP problem
« Reply #8 on: March 06, 2013, 02:06:54 pm »
The random crash is fixed. It stems from the fact that libtifiles HEAD does, indeed, not understand the CA86.86p file (so it won't be transferred), which is not fixed yet - and in the error path, the content was freed a second time.

Thanks for the report :)

EDIT, EDIT2: so... the CA86.86p file is broken because the first packet has a size 0x0C, which indicates a padded file name... but no padding was generated. Modern versions of ti8x_file_write_regular() in libtifiles produce 86 files with proper space padding.

There are at least two ways to solve your immediate problem by fixing the broken CA86.86p file:
* add the appropriate number of padding bytes after the file name (making the file a more proper .86p file):
... F9 13 0C (should stay as is) 00 E9 13 12 04 43 41 38 36 20 20 20 20 (should be added) E9 13 E7 13 57 6E 58 ...
* change the packet size, and therefore the total data size, to exercise another code path that copes with non-padded filenames:
... F5 (change LSB of total data size) 13 08 (change LSB of packet size) 00 E9 13 12 04 43 41 38 36 E9 13 E7 13 57 6E 58 ...

While I'm at it, I'm adding several traces, reformatting the code and fixing more NULL dereferences, but I won't finish tonight.
« Last Edit: March 06, 2013, 04:03:50 pm by Lionel Debroux »
Logged
Member of the TI-Chess Team.
Co-maintainer of GCC4TI (GCC4TI online documentation), TILP and TIEmu.
Co-admin of TI-Planet.

Offline Deathrider

  • LV1 Newcomer (Next: 20)
  • *
  • Posts: 13
  • Rating: +0/-0
    • View Profile
Re: TiLP problem
« Reply #9 on: March 07, 2013, 11:58:35 am »
Really really thank you!!!!  :thumbsup:
Logged
Pages: [1]   Go Up
« previous next »