Firmware Update loop Raspbee 1

deCONZ General Support
1

Hi, i’m trying to update my old Raspbee 1 to the newest available version and followed the guide on github.

For the installation i use a fresh install of the Rasbian Buster Headless image from phoscon: Linux phoscon 5.10.63-v7+ #1496 SMP Wed Dec 1 15:58:11 GMT 2021 armv7l GNU/Linux on a Raspberry Pi 3b. I installed all updates with apt update && apt upgrade and started to follow the guidline. I download the version deCONZ_Rpi_0x26400500.bin.GCF and stop the deconz service.

Now i try to flash the firmware using the command from the guidline and got the following loop:

GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
11:11:11:807 using firmware file: deCONZ_Rpi_0x26400500.bin.GCF 
11:11:11:873 ls dev: /dev/ttyAMA0 (0x0000/0x0000) sn: 
11:11:11:874 ls dev: /dev/ttyS0 (0x0000/0x0000) sn: 
11:11:11:875 dev /dev/ttyS0
Reboot device /dev/ttyS0 (RaspBee)
11:11:11:881 query bootloader v1 ID after 0 ms
11:11:13:383 query bootloader v1 ID after 1501 ms
11:11:13:883 query deCONZ firmware version
11:11:15:886 uart reset failed, try RaspBee reset
action: reset device RaspBee
wiringPi 2.52 initialized
11:11:16:116 query bootloader v1 ID after 0 ms
11:11:17:617 query bootloader v3 ID after 1502 ms
11:11:17:618 TX c081027dffc0
11:11:18:119 retry, elapsed 6 seconds
11:11:18:214 parse commands: /usr/bin/GCFFlasher_internal.bin -d /dev/ttyS0 -t 60 -R 3 -f deCONZ_Rpi_0x26400500.bin.GCF -x 3

i searching but there are no solutions in the forum only users with the same problems.

More Informations:

root@phoscon:/home/pi# uname -a
Linux phoscon 5.10.63-v7+ #1496 SMP Wed Dec 1 15:58:11 GMT 2021 armv7l GNU/Linux

root@phoscon:/home/pi# GCFFlasher_internal -l
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Path             | Vendor | Product | Serial     | Type
-----------------+--------+---------+------------+-------
/dev/ttyS0       | 0x0000 | 0x0000  |            | RaspB

root@phoscon:/home/pi# systemctl status deconz
● deconz.service - deCONZ: ZigBee gateway -- REST API
   Loaded: loaded (/lib/systemd/system/deconz.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2022-03-07 10:23:39 GMT; 1h 3min ago
 Main PID: 413 (code=exited, status=143)

Mär 07 10:21:08 phoscon systemd[1]: Started deCONZ: ZigBee gateway -- REST API.
Mär 07 10:21:10 phoscon deCONZ[413]: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-pi'
Mär 07 10:21:10 phoscon deCONZ[413]: libpng warning: iCCP: known incorrect sRGB profile
Mär 07 10:21:11 phoscon deCONZ[413]: This plugin does not support propagateSizeHints()
Mär 07 10:21:11 phoscon deCONZ[413]: This plugin does not support propagateSizeHints()
Mär 07 10:23:38 phoscon systemd[1]: Stopping deCONZ: ZigBee gateway -- REST API...
Mär 07 10:23:39 phoscon systemd[1]: deconz.service: Main process exited, code=exited, status=143/n/a
Mär 07 10:23:39 phoscon systemd[1]: deconz.service: Failed with result 'exit-code'.
Mär 07 10:23:39 phoscon systemd[1]: Stopped deCONZ: ZigBee gateway -- REST API.

root@phoscon:/home/pi# systemctl status deconz-gui
● deconz-gui.service - deCONZ: ZigBee gateway -- GUI/REST API
   Loaded: loaded (/lib/systemd/system/deconz-gui.service; disabled; vendor preset: enabled)
   Active: inactive (dead)

Mär 07 11:28:08 phoscon systemd[1]: /lib/systemd/system/deconz-gui.service:10: Unknown lvalue 'StartLimitIntervalSec' in section 'Service', ignoring
2

@de_employees

3

Is the RaspBee I getting very hot?

What are the RaspBee’s LEDs showing?

It the RaspBee I put at the left end of the GPIO port?

Can you try using the user pi and sudo (instead root).

What is the answer after:
sudo GCFFlasher_internal -r

You can try this (again):
Configure user access rights of the serial interface
sudo raspi-config
Interfacing Options → Serial

  • Would you like a login shell accessible over serial? → No
  • Would you like the serial port hardware to be enabled? → Yes
    Note: Changes to access rights only become active after a restart.
4

Not realy

The LED is constantly red and blinking green when the device is restarting.

Off course, i use the RaspBee for serveral years now. Actually i use it with RaspberryPi 4 CM and HassOS but i have some problems with the Lidl motion sensor that disconnects after a few days and need to be reset and new connected to work again… So i hope a firmware update will fix this problems. I don’t know when i update the RaspBee the last time…

pi@phoscon:~ $ sudo GCFFlasher_internal -r
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device RaspBee (RaspBee)
action: reset device RaspBee
wiringPi 2.52 initialized

LED red → LED fast blinking green 3 ore more times… → LED red

sudo doesn’t change anything:

pi@phoscon:~ $ sudo GCFFlasher_internal -t 60 -f firmware/deCONZ_Rpi_0x26400500.bin.GCF -x 3
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
22:10:14:350 using firmware file: firmware/deCONZ_Rpi_0x26400500.bin.GCF 
22:10:14:415 ls dev: /dev/ttyAMA0 (0x0000/0x0000) sn: 
22:10:14:416 check symlink /dev/ttyAMA0 (/dev/ttyS0)
22:10:14:416 ls dev: /dev/ttyS0 (0x0000/0x0000) sn: 
22:10:14:416 check symlink /dev/ttyS0 (/dev/ttyS0)
22:10:14:416 dev /dev/ttyS0 (/dev/ttyS0)
Reboot device RaspBee (RaspBee)
22:10:14:417 query bootloader v1 ID after 0 ms
22:10:15:919 query bootloader v1 ID after 1501 ms
22:10:16:420 query deCONZ firmware version
22:10:18:423 uart reset failed, try RaspBee reset
action: reset device RaspBee
wiringPi 2.52 initialized
22:10:18:625 query bootloader v1 ID after 0 ms
22:10:20:127 query bootloader v3 ID after 1502 ms
22:10:20:127 TX c081027dffc0
22:10:20:629 retry, elapsed 6 seconds
22:10:20:734 parse commands: /usr/bin/GCFFlasher_internal.bin -t 60 -f firmware/deCONZ_Rpi_0x26400500.bin.GCF -x 3

Didn’t change anything.

5

Found the Problem… On my Pi3 i use a cooling case and a pin header to extend the pins over the case. I started to flash the firmware using sudo GCFFlasher_internal -t 60 -f firmware/deCONZ_Rpi_0x26400500.bin.GCF -x 3 and than slowly move the RaspBee on the pin header. The Output on the console changed and the flasshing starts, i hold the RaspBee in place until SUCCESS.

The Problem was the Connection on the GPIO Header pins! I hope this information helps someone else.

1 Like