I am proud to announce I have updated my TI-Tools+libti rom dumping program to support the TI-84Plus C Silver Edition.

The rom dumper makes use of the I/O link's memory dump commands which as of the TiLP 2 1.17 release are exported from the libticalcs2 library.

Since it does make use of this I/O protocol only feature it sadly requires the use of a SilverLink, BlackLink or GrayLink cables. The DirectLink USB cable can never support this rom dump method so don't ask. I may add support for TILP's standard rom dumping method once Color support is added to it.

The other side effect of this using the I/O port protocol is that it is slow. It is very slow, it takes close to 30 minutes to dump the 4MB TI-84 Plus C Silver Edition ROM. I suggest having the USB cable plugged into the charger while doing the rom dump to avoid running out of battery while dumping. Having it plugged into one of the computers other USB ports can cause issues with libti grabbing the wrong one and thus the dump failing.

Keep in mind that since this uses libticalcs you will need to have either the standard TiLP libusb0 driver or the libusb0.1 filter driver installed. (The filter driver is what Kerm suggested to be used with gCn.)

The source can be found in my romdump-test branch of TITools.
I have uploaded a windows build that is bundled with the libti* .dll's from the recent 1.17 TiLP release at http://jonimoose.net/calcstuff/tilp/TITools-romdumper.zip

To use just run tidump in a terminal or console. On windows assuming your calc is on and TILP is able to communicate with it via silverlink double clicking the tidump.exe should suffice. tidump -h will list full command line arguments if you wish to manually point it at your silverlink or other cables.

Please post here with questions or comments and success stories.

Good

That's the first application of the libticalcs API expansion through exporting functions which were previously hidden - and in fact, the motivation for exporting them.
Jonimus' commit from a year ago, https://github.com/Jonimoose/TITools/commit/f7b12b6fee3cff3e23d87e29148cbcdfb65ad67a , opened my eyes about the necessity of exporting more functions to the public libticalcs API: in order to implement 83+ family DBUS memory page dump commands (and the ROM dumping wrapper on top of it), he had to copy & paste 2000+ lines of code (out of 2232 !) from libticalcs to tidump...

Oooh, this is great. Can't wait to dump my rom when I get home using this It seems like a pretty straight-forward process, which is good.

Definitely going to have to try this when I get home

I can't be much easier than double clicking an .exe, waiting 26 minutes, and uploading the resultant TI84+.rom to jsTIfied.

And yes it really does take 26 minutes, I timed it on my final testing run last night before uploading.

Great news, TheStorm! I updated our TI-84 Plus C Silver Edition reference page to refer to this topic for ROM dumping. It's less than ideal that it's SilverLink-only, but I understand the technical limitations, and this is still a huge step forward.

Sadly I can't seem to use this, because my TiLP install only detects my 84+CSE via DirectUSB, not SilverLink. I get this error:

EDIT: Nevermind, the connection issue earlier, I restarted a virtual machine from scratch (Windows XP) and it works fine. However Now this is what happens when trying to get a ROM dump:

C:\Documents and Settings\XPMUser\Desktop\TITools-romdumper>tidump

Code:


On my 2nd attempt I got this:

Code:


On 3rd attempt I got the same thing, even with timeout set at 15000ms (after page 4 it just hung there then failed)

4th attempt with verbose stuff:


Code:


It just seems to randomly stop...

EDIT Attempt 5: This time I setup tidump process priority to real time and I reached page 1C out of FF before it failed. It seems that even just moving the mouse by 1 pixel is enough to make it fail because it's so sensitive. Is there an solution to the sensitivity issue? I had similar problems with VTI ROM dumper.

There is most likely just too much latency between the OS and the IO link cable when talking though a virtual machine. My suggestion would be to try the using the libusb0 filter driver with the silverlink and running it natively rather than in a virtual machine.

Most likely it'll work fine for smaller variables but unless you have a beefy CPU and basically nothing going on getting a long enough period where the USB code involved is not interrupted is going to be difficult.

My problem is that the only computer I have right now has TI-Connect installed and I don't want to have to uninstall TI-Connect nor risk messing its install up with TiLP, hence why I was using a virtual machine.

I have a first-gen Intel Core i7 by the way.

*Bump*

Does anyone know a place where I can download a legit libglib-2.0-0.dll ?

For instance, it's part of the GTK+-win32 runtime (which the TILP installer can automatically download, http://gtk-win.sf.net ).
I can also find references to Win32 Glib at e.g. http://www.gtk.org/download/win32.php

I got all required dll's now. I ran it using this command:
tidump.exe -m auto --cable=blacklink:1

It said the DhaHelper driver and/or library was not found. What is this driver?

DhaHelper is a special driver used on 32-bit Windows for serial and parallel links. Unless you have a BlackLink / $4 cable, or ParallelLink ("$5 cable"), you don't need it (it doesn't matter if it doesn't work).

I got the black graphlink serial cable. I also have a usb cable. Can I use that with the program?

Edit: I checked if usb would work, but it says there was no directlink cable detected.

Which version and type (32-bit, 64-bit) of Windows are you using ?

And try using the TILP beta build from the beta-testing topic on Cemetech, it's more recent than TILP II 1.17.

Using win-32 Windows 7 professional.
I tried this:"
tidump.exe -m auto --cable=usb:1
It told me I needed libusb-win32
I downloaded it and I am in the process of installing the driver. Such a convoluted installation process

Well, the TILP installer automatically installs the driver, and it can download the appropriate GTK+ runtime (which contains libglib-2.0-0.dll). Replicating steps in a fully manual way is indeed cumbersome, there's a reason there's an automated installer

Where can I find this installer?
edit: never mind. found it on sourceforge. Thanks for the help!

Use the build from http://tiplanet.org/beta/setup.exe instead, as described in the beta-testing topic I mentioned above ( http://www.cemetech.net/forum/viewtopic.php?p=208470#208470 ): it's newer than TILP II 1.17.

The memory dump command leveraged by this dumper is supported only through legacy I/O, BTW. Without a SilverLink, use the DirectLink dumper built into libticalcs.

I just get so many link errors timeout errors and so forth. What does this suggest?

Edit: running it as administrator helped!