2Gig Firmware Update Issues

I purchased the 2 gig update cable to update my panel from version 1.10.1 to 1.19. I’ve followed the steps outlined in the firmware update video, but I am not able to successfully flash the new firmware.

The first PC I used to attempt the update is running windows 10. I installed the driver, ran the installation tool, found the com port and edited the shortcut. I’m able to initiate the flashing process, but it always gets stuck at the “deleting resource tables step” and ultimately fails.

I then decided to download 1.13, as maybe the issue was trying to update from 1.10.1 to 1.19. When i tried to open the 1.13 flash tool the first PC it will think and ultimately nothing will open.

The next step I took was to use a 2nd PC, also running windows 10, and update from 1.10.1 to 1.13. I followed all the steps on the firmware update video. On this PC I’m able to get the 1.13 update tool to open, but it just sits at the no panel.

I went back to the first PC to confirm the cable was good and the oldest tool I was able to get open was the 1.1401 tool, but the flash ultimately failed. It also was stuck at the deleting resource table step.

Any additional suggestions on where to go from here?

My cell module is inactive, so an OTA update isn’t an option.

It appears the issue was with a loose cable on the 2nd PC. Once the cable was taped in place, the updater was able to ping the control panel. I was then able to flash the firmware from version 1.10.1 to 1.12 successfully. Once that was complete the 1.13.1 update and then 1.19 update both worked.

It appears the issue was with a loose cable on the 2nd PC. Once the cable was taped in place, the updater was able to ping the control panel.

Ah, yes if the software does not detect a panel connected it will simply sit at “No Panel” Typically this is an issue with the cable or comm port number.

Glad you got this resolved!

I was then able to flash the firmware from version 1.10.1 to 1.12 successfully. Once that was complete the 1.13.1 update and then 1.19 update both worked.

2GIG states 1.19 can update 1.9 or later. If you have older than 1.9.6 always update to 1.9.6 first. I don’t think we have an older firmware GC2 to test this with atm though. Incrementally updating is also fine.

Hi Jason,

I am having this very same problem. My system currently has 1.10 so I should be good to update to 1.19.3. I have tried everything it feels like… and still getting the unable to flash message.

Is it possible that its a faulty cable? And that the pins are not seating right? Would you guys be willing to send a new one to try?

Below is the last bit from my log–anything you can glean from this?

01/04/20 00:23:20: ----------------------------------------------------------------------------
01/04/20 00:23:20: Now Connected
01/04/20 00:23:24: Disconnected
01/04/20 00:23:39: CP1 Computed CRC B72E Actual CCCC (-858993460)
01/04/20 00:23:39: CP1 pre18 Computed CRC 1FAE Actual FFFF (-1)
01/04/20 00:23:39: Debug is LOCKED
01/04/20 00:23:39: ----------------------------------------------------------------------------
01/04/20 00:23:39: Target Detected: CP1 (3)
01/04/20 00:23:39: ver_info: 1 0x8100 0x00BF 0x236D 0x007B8000 1 blver 10 restable 0x00008000
01/04/20 00:23:39: Target 3 Bootloader Ver/Size 10 0x00010000
01/04/20 00:23:39: Ram/Flash 01000000/017FFFFF 00000000/007FFFFF Debug ComPort 0
01/04/20 00:23:39: Support Boot Block
01/04/20 00:23:39: Compression is supported.
01/04/20 00:23:39: target_resource_info: 0x3377CC55 0x00005250 0xA1B1 0xFFFF 658 0xFFFF
01/04/20 00:23:51: failed to retrieve the resource table at index 0
01/04/20 00:23:51: downloaded resource info 658 resources
01/04/20 00:23:51: CP1
01/04/20 00:23:51: GoControl (0B 00 03 00 08 01 03 03 00 03 00 00)
01/04/20 00:23:51: Reading 00000004 bytes from memory 0x007F0034
01/04/20 00:24:02: ZWAVE Home ID: CCCCCCCC
01/04/20 00:24:02: Serial Number: 00057135
01/04/20 00:24:02: ----------------------------------------------------------------------------
01/04/20 00:24:02: Hex Target 3 Connected Target 3
01/04/20 00:24:02: Panel Version Bytes: 0 0 0 0
01/04/20 00:24:02: Internal Build Detected – no update
01/04/20 00:24:02: Target Cannot Be Flashed
01/04/20 00:24:02: ----------------------------------------------------------------------------

The log shows that the panel is communicating so I doubt the problem is the update cable but we can certainly try exchanging it to know for sure.

Usually there are 2 reasons why you would see “Target Cannot Be Flashed” when updating the firmware in a GC2.

  1. The firmware version you’re trying to install is already installed. It won’t let you reflash with the same version. If you boot back up regularly, can you confirm you still have 1.10 and it didn’t somehow actually succeed in updating to 1.19 in previous attempts?
  2. The panel hardware is too old to receive the firmware. I think this may be the case for your panel. In a pic you sent the serial number begins with 13 which means it was manufactured in 2013. There have been some reports of panels manufactured back then that can’t receive the firmware update. I hope that’s not the case but it may be.

If you have 1.10, you might try updating to an intermediate version before 1.19 to see if that helps. I’m not sure that will help but it’s worth a shot. Here’s a link to version 1.16.

If that doesn’t work, we’ll have to wait until Monday when I can get additional support to dig in further. We’ll probably either try a new update cable or we may determine the panel can’t be updated and return your switch kit. Hoping for the best!