Deconz-rest-plugin: Bricked ConBee II after firmware update timeout

Created on 26 Feb 2020  ·  5Comments  ·  Source: dresden-elektronik/deconz-rest-plugin

after I tried to update with wget http://deconz.dresden-elektronik.de/deconz-firmware/deCONZ_ConBeeII_0x264a0700.bin.GCF following happend:

$ sudo GCFFlasher_internal -d /dev/ttyACM0 -f deCONZ_ConBeeII_0x264a0700.bin.GCF  

GCFFlasher V3_13 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device /dev/ttyACM0 (ConBee II)
deCONZ firmware version 264A0700
R21B18 Bootloader
Vers: 2.07
build: Jun 17 2019
flashing 158985 bytes: |==============error: timeout flashing firmware after 3007 ms

now I insert the ConBee II and it disconnects/connects after some seconds on Debian and Windows

Most helpful comment

Can you please try with the following call:

sudo GCFFlasher_internal -d /dev/ttyACM0 -t 60  -f /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x264a0700.bin.GCF

with -t parameter fixed it!

I got following Output:

GCFFlasher V3_13 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device /dev/ttyACM0 (ConBee II)
R21B18 Bootloader
Vers: 2.07
build: Jun 17 2019
unlock!  (148 ms)
flashing 158985 bytes: |=======error: timeout flashing firmware after 3003 ms
Reboot device /dev/ttyACM0 (ConBee II)
Reboot device /dev/ttyACM0 (ConBee II)
Reboot device /dev/ttyACM0 (ConBee II)
R21B18 Bootloader
Vers: 2.07
build: Jun 17 2019
flashing 158985 bytes: |==============================|
verify: .
SUCCESS
Wait 10 seconds until application starts

Thanks!

All 5 comments

The device can't be bricked, since the bootloader is static.

Can you please try with the following call:

sudo GCFFlasher_internal -d /dev/ttyACM0 -t 60  -f /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x264a0700.bin.GCF

Thanks for that quick reply. I will try to flash it during the "conneted" state.

Maybe I misunderstood / explained it bad. The problem is on both my linux (debian), that I can see the device /dev/ttyACM0 and then it disappears:
I connect the device and spammed:

$ ls /dev/ttyA*
/dev/ttyACM0
$ ls /dev/ttyA*
ls: cannot access '/dev/ttyA*': No such file or directory
$ ls /dev/ttyA*
ls: cannot access '/dev/ttyA*': No such file or directory
$ ls /dev/ttyA*
ls: cannot access '/dev/ttyA*': No such file or directory
$ ls /dev/ttyA*
/dev/ttyACM0

etc... In windows I have the same issue. Device Manager keeps refreshing every couple seconds, additionally to connect/disconnect notification sounds.

Edit: Adding Info: I connect it on an Raspberry Pi 4 and have the same experience.
Listing $ lsusb will output Bus 001 Device 004: ID 1cf1:0030 Dresden Elektronik and after some short time frame $ lsusb will not output the device.

hmm on Linux, can you please try to:

  • Unplug the ConBee II
  • Start the above command (with -t parameter)
  • Plugin the ConBee II again

Are there any other USB devices connected (on Linux)?

Can you please try with the following call:

sudo GCFFlasher_internal -d /dev/ttyACM0 -t 60  -f /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x264a0700.bin.GCF

with -t parameter fixed it!

I got following Output:

GCFFlasher V3_13 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device /dev/ttyACM0 (ConBee II)
R21B18 Bootloader
Vers: 2.07
build: Jun 17 2019
unlock!  (148 ms)
flashing 158985 bytes: |=======error: timeout flashing firmware after 3003 ms
Reboot device /dev/ttyACM0 (ConBee II)
Reboot device /dev/ttyACM0 (ConBee II)
Reboot device /dev/ttyACM0 (ConBee II)
R21B18 Bootloader
Vers: 2.07
build: Jun 17 2019
flashing 158985 bytes: |==============================|
verify: .
SUCCESS
Wait 10 seconds until application starts

Thanks!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

wizkidorg picture wizkidorg  ·  3Comments

tenholde picture tenholde  ·  3Comments

stevenwfoley picture stevenwfoley  ·  3Comments

lynix picture lynix  ·  4Comments

philko123 picture philko123  ·  3Comments