dresden-elektronik / gcfflasher Goto Github PK

View Code? Open in Web Editor NEW

33.0 33.0 3.0 425 KB

GCFFlasher is the tool to program the firmware of dresden elektronik's Zigbee products.

License: BSD 3-Clause "New" or "Revised" License

C 97.44% Shell 0.38% CMake 1.92% Dockerfile 0.26%

gcfflasher's People

Contributors

Stargazers

Watchers

Forkers

ebaauw manup senilio

gcfflasher's Issues

use with a macbook "for dummies"

Hello guys,
sorry but I need a help to follow the guide to use GCFFlasher with a Mac.. I have to flash a conbee II (at the moment it isn't recognized by deconx 2.12.06 and i'm really going crazy because I don't know how I can resolve) but i have a lot of trouble to understand how i can follow the steps.... in practice:

Compile the executable with the build script (with Clang)
CC=clang ./build_posix.sh

--> what I should do when i open the terminal?

Run
$ ./GCFFlasher
GCFFlasher v4.0.0 copyright dresden elektronik ingenieurtechnik gmbh
usage: GCFFlasher

how I arrive here, in order to execute this program and flash the firmware? how I have also to download the new firmware and put it somewhere in the mac?
sorry for this elementary questions but I really don't know what I should do (and what I shouldn't do).

thanks a lot

Building on OpenWRT

Fails. Gives the following output:

root@APU3D4:~/gcfflasher# ./build_posix.sh 
Package libgpiod was not found in the pkg-config search path.
Perhaps you should add the directory containing `libgpiod.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libgpiod' found
libgpiod-dev not found, building without
gcc -Wall -DPL_LINUX -O2 -DNDEBUG

Looking for libbpiod:

root@APU3D4:~/gcfflasher# locate libgpiod
/root/gcfflasher/linux_libgpiod_reset.c
/usr/lib/libgpiod.so.2
/usr/lib/libgpiod.so.2.2.2
/usr/lib/opkg/info/libgpiod.control
/usr/lib/opkg/info/libgpiod.list
/usr/lib/opkg/info/libgpiod.postinst
/usr/lib/opkg/info/libgpiod.prerm

Unable to compile on Ubuntu 18.04 (undefined reference 'dlclose')

I'm trying to compile on Ubuntu 18.04, and I'm getting this error message:

$ ./build_posix.sh
gcc -Wall -DPL_LINUX -DHAS_LIBGPIOD -ldl -O2 -DNDEBUG
/tmp/ccynS9Kw.o: In function `plUnloadLibGpiod':
main_posix.c:(.text+0x15): undefined reference to `dlclose'
/tmp/ccynS9Kw.o: In function `plLoadLibGpiod':
main_posix.c:(.text+0x25b): undefined reference to `dlopen'
main_posix.c:(.text+0x27d): undefined reference to `dlsym'
main_posix.c:(.text+0x298): undefined reference to `dlsym'
main_posix.c:(.text+0x2b3): undefined reference to `dlsym'
main_posix.c:(.text+0x2ce): undefined reference to `dlsym'
main_posix.c:(.text+0x2e8): undefined reference to `dlsym'
/tmp/ccynS9Kw.o:main_posix.c:(.text+0x301): more undefined references to `dlsym' follow
collect2: error: ld returned 1 exit status

Distro details:

$ uname -a
Linux core 4.15.0-147-generic #151-Ubuntu SMP Fri Jun 18 19:21:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.5 LTS
Release:        18.04
Codename:       bionic

I've got gpiod and libc headers and build-essential installed:

$ dpkg -l | grep gpio
ii  libgpiod-dev                           1.0-1                                            amd64        C library for interacting with Linux GPIO device - static libraries and headers
ii  libgpiod1:amd64                        1.0-1                                            amd64        C library for interacting with Linux GPIO device - shared libraries

$ dpkg -l | grep libc6-dev
ii  libc6-dev:amd64                        2.27-3ubuntu1.4                                  amd64        GNU C Library: Development Libraries and Header Files
ii  libc6-dev-i386                         2.27-3ubuntu1.4                                  amd64        GNU C Library: 32-bit development libraries for AMD64
ii  libc6-dev-x32                          2.27-3ubuntu1.4                                  amd64        GNU C Library: X32 ABI Development Libraries for AMD64

I feel I'm missing something obvious here...

Raspbee working but firmware upgrade problem on RPi4

Describe the bug

I have an old RaspBee with 26050500 and am trying to upgrade to 26400500
The RaspBee is otherwise working fine and controls my lights/switches using the app (latest beta)

Steps to reproduce the behavior

# systemctl stop deconz
# GCFFlasher_internal -t 60 -x 3 -f deCONZ_Rpi_0x26400500.bin.GCF
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
18:06:15:742 using firmware file: deCONZ_Rpi_0x26400500.bin.GCF 
18:06:15:817 ls dev: /dev/ttyAMA0 (0x0000/0x0000) sn: 
18:06:15:817 check symlink /dev/ttyAMA0 (/dev/ttyAMA0)
18:06:15:817 dev /dev/ttyAMA0 (/dev/ttyAMA0)
Reboot device RaspBee (RaspBee)
18:06:15:819 query bootloader v1 ID after 0 ms
18:06:17:321 query bootloader v1 ID after 1501 ms
18:06:17:822 query deCONZ firmware version
18:06:17:830 SLIP RX frame length: 9
deCONZ firmware version 26050500
18:06:17:831 send watchdog reset 2 seconds
18:06:17:831 TX c00b02000c0005002602000000baffc0
18:06:17:840 set watchdog ttl status: 0x04
18:06:17:840 uart reset failed, try RaspBee reset
action: reset device RaspBee
wiringPi 2.52 initialized
18:06:18:046 query bootloader v1 ID after 1 ms
18:06:19:548 query bootloader v3 ID after 1503 ms
18:06:19:548 TX c081027dffc0
18:06:20:050 retry, elapsed 4 seconds
18:06:20:155 parse commands: /usr/bin/GCFFlasher_internal.bin -t 60 -x 3 -f deCONZ_Rpi_0x26400500.bin.GCF

[This repeats several times until the timeout]

# GCFFlasher_internal -l
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Path             | Vendor | Product | Serial     | Type
-----------------+--------+---------+------------+-------
/dev/ttyAMA0     | 0x0000 | 0x0000  |            | RaspBee 

# GCFFlasher_internal -r
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device RaspBee (RaspBee)
deCONZ firmware version 26050500
action: reset device RaspBee
wiringPi 2.52 initialized
# [Red light doesn't flash]

# md5sum deCONZ_Rpi_0x26400500.bin.GCF
71a750b778a2f6995a26589c45ff87b7  deCONZ_Rpi_0x26400500.bin.GCF
# cat deCONZ_Rpi_0x26400500.bin.GCF.md5 
71a750b778a2f6995a26589c45ff87b7  deCONZ_Rpi_0x26400500.bin.GCF

Environment

Host system: Raspberry Pi 4
Running method: Raspbian Headless
Firmware version: 26050500
deCONZ version: (2.xx.yy)
Device: RaspBee I
Do you use an USB extension cable: (yes / no) -- n/a
Is there any other USB or serial devices connected to the host system? No

GCFFlasher_internal causes USB serial device to be unregistered and fails

I connect ConBee stick and see this in kernel log:

[ 4749.160117] usb 1-3: new full-speed USB device number 8 using xhci_hcd
[ 4749.316628] usb 1-3: New USB device found, idVendor=0403, idProduct=6015, bcdDevice=10.00
[ 4749.316637] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4749.316641] usb 1-3: Product: FT230X Basic UART
[ 4749.316645] usb 1-3: Manufacturer: FTDI
[ 4749.316649] usb 1-3: SerialNumber: DJ00QDS1
[ 4749.346114] usbcore: registered new interface driver usbserial_generic
[ 4749.346138] usbserial: USB Serial support registered for generic
[ 4749.348573] usbcore: registered new interface driver ftdi_sio
[ 4749.348583] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 4749.348632] ftdi_sio 1-3:1.0: FTDI USB Serial Device converter detected
[ 4749.348661] usb 1-3: Detected FT-X
[ 4749.349085] usb 1-3: FTDI USB Serial Device converter now attached to ttyUSB0

I run GCFFlasher_internal -l:

GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Path             | Vendor | Product | Serial     | Type
-----------------+--------+---------+------------+-------
/dev/ttyUSB0     | 0x0403 | 0x6015  | DJ00QDS1   | ConBee

I try to update firmware by running

GCFFlasher_internal -t 60 -d /dev/ttyUSB0 -f deCONZ_Rpi_0x26400500.bin.GCF -sn DJ00QDS1 -x 3

GCFFlasher_internal outputs this in a loop for 60 seconds then gives up:

10:06:21:928 using firmware file: deCONZ_Rpi_0x26400500.bin.GCF 
10:06:21:975 ls dev: /dev/ttyACM0 (0x0658/0x0200) sn: 
10:06:21:975 device /dev/ttyUSB0 not found
10:06:21:975 retry, elapsed 0 seconds
10:06:22:070 parse commands: /usr/bin/GCFFlasher_internal.bin -t 60 -d /dev/ttyUSB0 -f deCONZ_Rpi_0x26400500.bin.GCF -sn DJ00QDS1 -x 3

At the same time, I see this in kernel log:

[ 4788.425720] usbserial: USB Serial deregistering driver FTDI USB Serial Device
[ 4788.426059] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 4788.426081] usbcore: deregistering interface driver ftdi_sio
[ 4788.426110] ftdi_sio 1-3:1.0: device disconnected
[ 4788.451842] usbserial: USB Serial deregistering driver generic
[ 4788.451925] usbcore: deregistering interface driver usbserial_generic

The /dev/ttyUSB0 device is now gone from the file system. It appears that running GCFFlasher_internal immediately causes the /dev/ttyUSB0 device to unregister and then it can't find it.

How do I make this work so I can update firmware on my ConBee stick?

Refuses to flash zshark firmware

The filename version check fails for the zshark firmware unless it is renamed to ./zshark_conbee2_v1_0.0x0.bin.GCF to contain 0x0. Works just fine after renaming.

unclear if update succeed

used GCFlasher on cli to update the firmware. Process run trough and GCFlasher reported successful update.

However - zigbee2mqtt still shows the initial firmware version. Unfortunately GCFlasher does not show which firmware is actually on the stick.

How can I test which firmware is really installed on stick?

Conbee2 initial: 0x26720700
Firmware download: deCONZ_ConBeeII_0x26780700.bin.GCF

GCFFlasher v4.0.3-beta

Firmware update unsuccesful

Hi,

I have a Conbee 2 device running version: "deCONZ firmware version 26660700"
I'm trying to update to latest or next version (i have tried both). And in both cases i'm getting error:
"query bootloader failed"
With Older version of flasher
"could not sync with bootloader"

Command i'm running :
/GCFFlasher -l
1 devices found
DEV [0]: name: ConBee_II (DE2420389),path: /dev/ttyACM0 --> /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2420389-if00

/GCFFlasher -t 10 -d /dev/ttyACM0 -f ../deCONZ_ConBeeII_0x26720700.bin.GCF
read file success: ../deCONZ_ConBeeII_0x26720700.bin.GCF (164241 bytes)
flash firmware
query bootloader id
query bootloader id
bootloader detected (60)
failed to sync bootloader (0)

I have tried with longer timeout same result.
I disconnected all other devices from usb ports. I'm running on Ubuntu and i have an extension cable.
Any suggestions ? I was able to work with current version but it's started to loose devices and i trying to update fw it's not working at all any more.

Thanks,
Ilya.

Retry connect bootloader

Hello, I'm having issues flashing the firmware to my ConBee II stick:

> ls /dev | grep ttyAC
ttyACM0

./GCFFlasher -f deCONZ_RaspBeeII_0x26720700.bin.GCF -t 60 -d /dev/ttyACM0
read file success: deCONZ_RaspBeeII_0x26720700.bin.GCF (164241 bytes)
flash firmware
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
retry connect bootloader /dev/ttyACM0
^C
> ./GCFFlasher -r -d /dev/ttyACM0
>

After a few reboots and mounting the stick into a virtual machine, it becomes available:

> GCFFlasher -l                                                          
1 devices found
DEV [0]: name: ConBee_II (DE2485204),path: /dev/ttyACM0 --> /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2485204-if00
> GCFFlasher -r -d /dev/ttyACM0
>

I'm not entirely sure how I can continue - the firmware flasher doesn't really seem to be able to communicate with the USB stick. I've been using it successfully with the Docker container for over a year and was noticing some sluggishness communicating with some sensors recently, which I figured I might be able to address with a firmware update. This is the first time I've attempted to update the firmware.

In the docker image:

╰─ kubectl logs deployments/deconz -f
Found 7 pods, using pod/deconz-d65d5df4f-zx579
[deconzcommunity/deconz] Starting deCONZ...
[deconzcommunity/deconz] Current deCONZ version: 2.21.02
[deconzcommunity/deconz] Web UI port: 8081
[deconzcommunity/deconz] Websockets port: 8443
[deconzcommunity/deconz] Using options --auto-connect=1 --appdata=/opt/deCONZ --dbg-info=1 --dbg-aps=0 --dbg-zcl=0 --dbg-ddf=0 --dbg-dev=0 --dbg-zdp=0 --dbg-ota=0 --dbg-error=0 --dbg-http=0 --http-port=8081 --ws-port=8443
[deconzcommunity/deconz] Modifying user and group ID
[deconzcommunity/deconz] Checking device group ID
[deconzcommunity/deconz] VNC Disabled
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-deconz'
libpng warning: iCCP: known incorrect sRGB profile
This plugin does not support propagateSizeHints()
This plugin does not support propagateSizeHints()
23:53:24:922 HTTP Server listen on address 0.0.0.0, port: 8081, root: /usr/share/deCONZ/webapp/
23:53:24:926 Warning: /opt/deCONZ/config.ini doesn't exists
23:53:24:926 Warning: /opt/deCONZ/zll.db doesn't exists
23:53:24:968 COM: /dev/ttyACM0 / serialno: , ConBee II
23:53:24:968 ZCLDB init file /opt/deCONZ/zcldb.txt
23:53:25:032 DDF enabled for Gold status
23:53:25:216 gw run mode: normal
23:53:25:216 GW sd-card image version file does not exist: /opt/deCONZ/gw-version
23:53:25:217 Started websocket server on 0.0.0.0, port: 8443
23:53:25:218 create default username and password
23:53:25:218 [INFO] - Found file containing button maps. Parsing data...
23:53:25:225 [INFO] - Button maps loaded.
23:53:25:225 found node plugin: libde_rest_plugin.so - REST API Plugin
23:53:25:226 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
23:53:25:230 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
23:53:25:248 dlg action: Read binding table
23:53:25:001 New websocket 192.168.3.251:53222 (state: 3) 
23:53:26:256 COM: /dev/ttyACM0 / serialno: , ConBee II
This plugin does not support propagateSizeHints()
23:53:27:767 Device firmware version 0x26580700 ConBee II
23:53:27:772 unlocked max nodes: 512
23:53:27:772 Device protocol version: 0x010B
23:53:27:799 new node - ext: 0x00212effff080803, nwk: 0x0000
23:53:27:993 Current channel 15
23:53:28:076 CTRL ANT_CTRL 0x03
23:53:28:242 APS-DATA.indication from unknown node 0x0923
23:53:28:269 unknown node 0x00124B00246ED331 (0x0923), lqi: 223
23:53:28:269 APS-DATA.indication from unknown node 0x00124B00246ED331
23:53:30:470 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26720700.bin.GCF
23:53:30:470 GW firmware version shall be updated to: 0x26720700
23:53:31:261 Announced to internet https://phoscon.de/discover
23:53:33:618 DEV Tick.Init: booted after 8000 seconds
23:53:39:718 saved node state in 0 ms
23:53:39:718 sync() in 0 ms
23:53:40:603 new node - ext: 0x00124b00246ed331, nwk: 0x0923
23:53:42:578 ZDP get node descriptor for 0x0923
23:53:42:625 ZDP get active endpoints for 0x0923
23:53:42:678 ZDP get simple descriptor 0x01 for 0x0923
23:53:42:727 ZDP get simple descriptor 0x02 for 0x0923
23:53:42:859 DEV no DDF for 0x00124B00246ED331, modelId: ZB-SW02
23:53:42:859 DEV create on-the-fly DDF for 0x00124B00246ED331
23:53:45:219 Set bridgeid to 00212EFFFF080803
23:53:52:719 saved node state in 0 ms
23:53:52:719 sync() in 0 ms

Is this stick unable to be updated?

flashing ... retry, failed

I seem to have a disagreement with GCFFlasher when it comes to flashing RaspBee II firmware. It reports "failed" where it has obviously done a good job. Further, it seems to do the job twice, dunno if that's okay.

I followed this procedure: https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually#update-in-raspbian

On shell, i see:
pi@rpi4:/tmp $ sudo GCFFlasher_internal -t 60 -f deCONZ_RaspBeeII_0x26720700.bin.GCF
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device RaspBee (RaspBee)
deCONZ firmware version 26610700
Bootloader version 0x00030003, app crc: 0x769F0F78
flashing 164227 bytes: |================|Reboot device RaspBee (RaspBee)
deCONZ firmware version 26720700
Bootloader version 0x00030003, app crc: 0x01BB96DC
flashing 164227 bytes: |================|retry, failed

In Phoscon web app, it shows the new firmware version correctly, so I assume the process was successful.

In the deconz-rest-plugin repo, there seems to be a report with kinda same experience, @Mimiix gave the request to use this repo instead for reporting.

I use a Rpi4 with RaspBee II and tried to flash firmware deCONZ_RaspBeeII_0x26720700.bin.GCF

Let me know if you need something.

GCFFLASHER - Reboot the key

Hello,

I have Xiaomi buttons that disconnect, to reconnect them I have to reboot the conbee II key on deconz.
I would like to industrialize this, do you have a specific command or other to restart the key without affecting the configuration ?

Does the "-r" command of GCFFLASHER do what I'm looking for without affecting the configuration of my key ?

Thanks.

GDFFlasher -l list devices on MacOS

Hello,

My conbee 2 is connected on Mac0S and the command
./GCFFlasher -l
0 devices found

i have to install a driver on macOS ?
Thanks

Get current firmware version

Hello and thanks you for this! It would be great if GCFFlasher can give use more details about the adapter, such as the current firmware version running.

Windows Powershell not responding to Options

Hi, trying to update a Conbee II USB-stick with GCFflasher 3.17 for windows. Not sure if I'm on the right place to get some help about this but let's try - please refer me to the right place otherwise... :-)

Starting a Powershell window where the GCFFlasher folder is according to instructions found here, by the Windows section for PCs without deCONZ software:
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually

In the Powershell window I get this:

PS C:\..\GCFFlasher_V3_17> .\GCFFlasher 
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
usage: GCFFlasher <options>
options:
-r              force device reset without programming
-f <firmware>   flash firmware file
-d <device>     device number or com port to use, e.g. 0 or COM37
-s <serial>     serial number to use
-t <timeout>    retry until timeout (seconds) is reached
-R <retries>    max. retries
-B <baudrate>   custom baudrate
-l              list devices
-x <loglevel>   debug log level 0, 1, 3
-j <test>       runs a test 1
-h -?           print this help

And no matter what I write as options after .\GCFFlasher, I Get this answer. It does not respont to chosen option... Why? What can I do about this? Am I an idiot? Please be honest. I can take it.

Thank you. ;-)