Raspbee firmware update brick

BrianHenryIE · August 19, 2022, 4:23am

I was having trouble with my Raspbee II after moving it to a Pi4, which I think was really down to me using a USB3 SSD with it. Anyway, I thought I’d updated the firmware as an attempt to fix it. It’s in use in Home Assistant.

First I used Raspian to update the firmware but that didn’t work, I got the message repeatedly:

Reboot device RaspBee (RaspBee)

There was no progress bar.

So I used the Phoscon image and things appeared to be more positive, i.e. there was a progress bar, but it ended with a failure message. So I ran it again with verbose logging, and it does look positive to me until the very end.

retry, failed

When I booted again into Home Assistant, all my devices are unavailable.

I’ve cut out the repetitive parts of the log. Any help appreciated!

pi@phoscon:/tmp $ sudo systemctl stop deconz

pi@phoscon:/tmp $ wget https://deconz.dresden-elektronik.de/deconz-firmware/deCONZ_RaspBeeII_0x26780700.bin.GCF
--2022-08-19 04:50:48--  https://deconz.dresden-elektronik.de/deconz-firmware/deCONZ_RaspBeeII_0x26780700.bin.GCF
Resolving deconz.dresden-elektronik.de (deconz.dresden-elektronik.de)... 144.76.96.194
Connecting to deconz.dresden-elektronik.de (deconz.dresden-elektronik.de)|144.76.96.194|:443... 
connected.
HTTP request sent, awaiting response... 200 OK
Length: 163244 (159K) [application/octet-stream]
Saving to: ‘deCONZ_RaspBeeII_0x26780700.bin.GCF’

deCONZ_RaspBeeII_0x26780700.bin.GCF    100%[==========================================================================>] 159.42K   455KB/s    in 0.4s    

2022-08-19 04:50:49 (455 KB/s) - ‘deCONZ_RaspBeeII_0x26780700.bin.GCF’ saved [163244/163244]

pi@phoscon:/tmp $ sudo systemctl stop ModemManager
Failed to stop ModemManager.service: Unit ModemManager.service not loaded.

pi@phoscon:/tmp $ sudo GCFFlasher_internal -t 60 -f deCONZ_RaspBeeII_0x26780700.bin.GCF -x 3
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
04:51:12:575 using firmware file: deCONZ_RaspBeeII_0x26780700.bin.GCF 
04:51:12:660 ls dev: /dev/ttyAMA0 (0x0000/0x0000) sn: 
04:51:12:660 check symlink /dev/ttyAMA0 (/dev/ttyS0)
04:51:12:660 ls dev: /dev/ttyS0 (0x0000/0x0000) sn: 
04:51:12:660 check symlink /dev/ttyS0 (/dev/ttyS0)
04:51:12:660 dev /dev/ttyS0 (/dev/ttyS0)
Reboot device RaspBee (RaspBee)
04:51:12:662 query bootloader v1 ID after 0 ms
04:51:14:164 query bootloader v1 ID after 1501 ms
04:51:14:664 query deCONZ firmware version
04:51:14:672 SLIP RX frame length: 9
deCONZ firmware version 26780700
04:51:14:672 send watchdog reset 2 seconds
04:51:14:672 TX c00b02000c0005002602000000baffc0
04:51:14:812 uart reset failed, try RaspBee reset
action: reset device RaspBee
wiringPi 2.52 initialized
04:51:15:023 query bootloader v1 ID after 0 ms
04:51:15:511 RX 14 bytes ASCII ??? after 488 ms
04:51:15:511 RX c081820300030085a1628fe0fcc0 after 488 ms
04:51:15:511 SLIP RX frame length: 10
04:51:15:511 check magic: 0x81 cmd: 0x82 after 488 ms
Bootloader version 0x00030003, app crc: 0x8F62A185
04:51:15:512 GCF_ResetDeviceDone
04:51:15:513 bootloader v3 update firmware request size: 163230, addr: 0x00005000, type: 31, crc-32: 0xAAAAAAAA
04:51:15:514 TX c081039e7d0200005000001faaaaaaaa48fbc0
04:51:15:521 SLIP RX frame length: 3
flashing 163230 bytes: |=04:51:15:526 SLIP RX frame length: 8
04:51:15:526 updateFirmwareV3DataRsp()
04:51:15:526 bootloader v3 data request, offset: 0, length: 256
04:51:15:526 bootloader v3 send data response, status: 0, offset: 0, length: 256
04:51:15:527 TX c08184000000000000013087c6882eac14f5e1471e1c5f9938057b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af3b66c0
04:51:15:606 SLIP RX frame length: 8

...

04:52:06:929 updateFirmwareV3DataRsp()
04:52:06:929 bootloader v3 data request, offset: 163072, length: 158
04:52:06:929 bootloader v3 send data response, status: 0, offset: 163072, length: 158
04:52:06:930 TX c0818400007d02009e007cdc9f7ebb3d63780e92215ad3d71cbae1cbdbdd4d695c98449099d07f513e094826dcf9ace5459007a91c5c9997a1eee63f3fc6d2ba364c507b64084902b644e5990ba33fb4dbdd7a61ddd8a0e6820912f8adef00d1bfb43f353cae1760e2e7c6bf21bd39dbddd21de96be6c5e83139ba4d0d2d288efdf5f0a7902e720cb9b7f275da4e0cc3cc86c4a57453338a9ab65b8141a2dbddc3025f73d3a20100ffc5022ca6acc0
04:52:06:930 bootloader v3 finished all data
|04:52:07:981 verify application is running
04:52:07:982 query deCONZ firmware version
04:52:09:984 failed to query application
04:52:09:985 retry, elapsed 57 seconds
04:52:10:080 parse commands: /usr/bin/GCFFlasher_internal.bin -t 60 -f deCONZ_RaspBeeII_0x26780700.bin.GCF -x 3
04:52:10:081 using firmware file: deCONZ_RaspBeeII_0x26780700.bin.GCF 
04:52:10:175 ls dev: /dev/ttyAMA0 (0x0000/0x0000) sn: 
04:52:10:175 check symlink /dev/ttyAMA0 (/dev/ttyS0)
04:52:10:175 ls dev: /dev/ttyS0 (0x0000/0x0000) sn: 
04:52:10:175 check symlink /dev/ttyS0 (/dev/ttyS0)
04:52:10:176 dev /dev/ttyS0 (/dev/ttyS0)
Reboot device RaspBee (RaspBee)
04:52:10:177 query bootloader v1 ID after 0 ms
04:52:11:679 query bootloader v1 ID after 1501 ms
04:52:12:179 query deCONZ firmware version
04:52:12:186 SLIP RX frame length: 9
deCONZ firmware version 26780700
04:52:12:186 send watchdog reset 2 seconds
04:52:12:186 TX c00b03000c0005002602000000b9ffc0
04:52:12:230 set watchdog ttl status: 0x00
04:52:12:230 wait reboot: 2100 ms
04:52:14:331 query bootloader v1 ID after 0 ms
04:52:15:122 RX 14 bytes ASCII ??? after 791 ms
04:52:15:122 RX c081820300030085a1628fe0fcc0 after 791 ms
04:52:15:122 SLIP RX frame length: 10
04:52:15:122 check magic: 0x81 cmd: 0x82 after 791 ms
Bootloader version 0x00030003, app crc: 0x8F62A185
04:52:15:124 GCF_ResetDeviceDone
04:52:15:125 bootloader v3 update firmware request size: 163230, addr: 0x00005000, type: 31, crc-32: 0xAAAAAAAA
04:52:15:125 TX c081039e7d0200005000001faaaaaaaa48fbc0
04:52:15:132 SLIP RX frame length: 3
flashing 163230 bytes: |=04:52:15:137 SLIP RX frame length: 8
04:52:15:137 updateFirmwareV3DataRsp()
04:52:15:138 bootloader v3 data request, offset: 0, length: 256
04:52:15:138 bootloader v3 send data response, status: 0, offset: 0, length: 256
04:52:15:138 TX c08184000000000000013087c6882eac14f5e1471e1c5f9938057b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af3b66c0
04:52:15:218 SLIP RX frame length: 8

...

04:53:06:493 updateFirmwareV3DataRsp()
04:53:06:493 bootloader v3 data request, offset: 163072, length: 158
04:53:06:493 bootloader v3 send data response, status: 0, offset: 163072, length: 158
04:53:06:493 TX c0818400007d02009e007cdc9f7ebb3d63780e92215ad3d71cbae1cbdbdd4d695c98449099d07f513e094826dcf9ace5459007a91c5c9997a1eee63f3fc6d2ba364c507b64084902b644e5990ba33fb4dbdd7a61ddd8a0e6820912f8adef00d1bfb43f353cae1760e2e7c6bf21bd39dbddd21de96be6c5e83139ba4d0d2d288efdf5f0a7902e720cb9b7f275da4e0cc3cc86c4a57453338a9ab65b8141a2dbddc3025f73d3a20100ffc5022ca6acc0
04:53:06:493 bootloader v3 finished all data
|04:53:07:544 verify application is running
04:53:07:544 query deCONZ firmware version
04:53:09:547 failed to query application
retry, failed

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

BrianHenryIE · August 19, 2022, 4:33am

I just tried a brand new Raspbee II in its place and my devices still appear unavailable, so I’m not sure what’s up now! Maybe that’s because the devices are paired with a different radio MAC?

Mimiix · August 19, 2022, 7:11am

For the brick part, @de_employees need to answer.

For the new one: Did you import a backup when you put the new raspbee in? The backup also contains Network settings for the raspbee. Those are probably not set (comming close to your Mac suggestion indeed).

ChrisHae · August 19, 2022, 7:54am

Hi, in GCFFlasher v3.17 it could happen that it prints “failure” when checking the firmwareversion at the end but the update process was successfull.

best way to check the current installed firmware version is sudo GCFFlasher_internal -r
It prints the firmware version and the bootloader version. If there is no bootloader version then it is really bricked.

Then you could check if the RaspBee2 is connected with deCONZ. If you have installed the Desktop /GUI version of deCONZ you see if it is connected when you see the network map with the raspbee2 as a node with a blue marking.

And if you use a new Raspbee2 in your old network you need the same network settings as in your old network as Mimiix said.
You can import an old backup file in the Phoscon App if you have one or ALT+ right click at the “Advanced” Settings icon of the Gateway Settings page in the Phoscon App. There you can see and restore old network settings.

BrianHenryIE · August 25, 2022, 12:17am

I was able to downgrade to a previous firmware.

I don’t have my house back fully operational, but I do have a few sensors confirmed working.

Thanks for the help.