HP 15c Collector's Edition save/restore does not work

[fossy]

Hello

Could anybody get this to work?

I have a HP 15c_CE with new firmware (HP_IAR_USB 120ms.bin - checksum 0A0Ah - 2024-06-03) and the VoyagerSave.exe from https://hpcalcs.com/download.

As mentioned in https://hpcalcs.com/downloads/apps/Voyag...ctions.pdf the calculator should go into HID mode after pressing [ON]/[f]&[ENTER] - and leave it with a hit on [ON].

Even this is not true for me. The calculator keeps only in the HID mode while I keep holding [f]&[ENTER]. When I release [f]&[ENTER] the calculator is switched on in normal operation and HID mode is off.

I cannot imagine that the holding from [f]&[ENTER] is the "plan" to save and restore calculators memory.

When I hold the calculator in HID mode with my left hand and key in with my right hand on the PC

Code:

VoyagerSave.exe -s memory

I get a file memory with exactly 0 Bytes. Even this does not work.

Does this work (and if how) for anybody?

[Divasson]

Hi,

It works for me.

While the calculator is off, press [f]+[ENTER], hold them pressed, and then press and release [on] (nothing happens yet), THEN release [f]+[ENTER] and the calculator switches on in HID mode.

The back-up file has always 2048 bytes - no matter the memory size mode we're in.

If you do not get a permanent HID link then we have a problem...I'd reload the firmware and check that it is the same using the SAM-BA check button.

[ijabbott]

My symptoms are slightly different. In Windows 11, I get a HID device called "HID-compliant vendor-defined device". When I run `VoyagerSave.exe -s filename`, it seems to hang there. I can Ctrl-C back to the CMD prompt, but no file has been created.

(I re-flashed the firmware and verified it just to make sure it was running the correct firmware, but it made no difference.)

Then I tried it in a different USB port and it worked!

The non-working USB device has a path like the following, and is a USB 2.0 port:

Code:

computer
 + ACPI x64-based PC
    + Microsoft ACPI-Compliant System
       + PCI Express Root Complex
          + PCI-to-PCI Bridge
             + AMD USB 3.10 eXtensible Host Controller - 1.10 (Microsoft)
                + USB Root Hub (USB 3.0)
                   + Generic USB Hub
                      + Generic USB Hub
                         + USB Input Device
                            + HID-compliant vendor-defined device

A working device in a USB 2.0 port has a path like the following:

Code:

computer
 + ACPI x64-based PC
    + Microsoft ACPI-Compliant System
       + PCI Express Root Complex
          + PCI-to-PCI Bridge
             + AMD USB 3.10 eXtensible Host Controller - 1.10 (Microsoft)
                + USB Root Hub (USB 3.0)
                   + Generic USB Hub
                      + USB Input Device
                         + HID-compliant vendor-defined device

It has one fewer levels of USB hubs than the non-working device.

Here is another working device in a USB 3.0 port on the same XHCI controller:

Code:

computer
 + ACPI x64-based PC
    + Microsoft ACPI-Compliant System
       + PCI Express Root Complex
          + PCI-to-PCI Bridge
             + AMD USB 3.10 eXtensible Host Controller - 1.10 (Microsoft)
                + USB Root Hub (USB 3.0)
                   + USB Input Device
                      + HID-compliant vendor-defined device

Here is another working device in a USB 3.0 port on a different XHCI controller:

Code:

computer
 + ACPI x64-based PC
    + Microsoft ACPI-Compliant System
       + PCI Express Root Complex
          + PCI-to-PCI Bridge
             + Renasas USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
                + USB Root Hub (USB 3.0)
                   + USB Input Device
                      + HID-compliant vendor-defined device

So it seems to be sensitive to the number of USB hubs in the chain, or at least the number of USB 2.0 hubs.

[fossy]

Thanks ijabbott!

I had to change the USB-Port. Now it work's.
For me it works with USB2 and USB3. It did not work with a long cable. But firmware flashing worked with the long cable.