Not able to upgrade to latest FW | Raspbee2

Hi all,

unfortunately I am not able to migrate to the latest firmware at all.

GCFFlasher -l returns:

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

Upgrading the FW with sudo GCFFlasher_internal -t 60 -d /dev/ttyS0 -f ./deCONZ_RaspBeeII_0x26720700.bin.GCF -x 3 returns with:

10:24:15:010 using firmware file: ./deCONZ_RaspBeeII_0x26720700.bin.GCF
10:24:15:128 ls dev: /dev/ttyAMA0 (0x0000/0x0000) sn:
10:24:15:128 ls dev: /dev/ttyS0 (0x0000/0x0000) sn:
10:24:15:128 dev /dev/ttyS0
Reboot device /dev/ttyS0 (RaspBee)
10:24:15:130 query bootloader v1 ID after 0 ms
10:24:16:631 query bootloader v1 ID after 1501 ms
10:24:17:132 query deCONZ firmware version
10:24:19:135 uart reset failed, try RaspBee reset
action: reset device RaspBee
10:24:19:337 query bootloader v1 ID after 1 ms
10:24:19:830 RX 9 bytes ASCII X� after 493 ms
10:24:19:830 RX 588a0001f2d143cdf8 after 493 ms
10:24:20:832 query bootloader v1 ID after 1495 ms
10:24:22:333 query bootloader v3 ID after 2996 ms
10:24:22:333 TX c081027dffc0
10:24:22:346 RX 14 bytes ASCII ��� after 3009 ms
10:24:22:346 RX c0818203000300dc96bb01c9fcc0 after 3009 ms
10:24:22:346 SLIP RX frame length: 10
10:24:22:346 check magic: 0x81 cmd: 0x82 after 3009 ms
Bootloader version 0x00030003, app crc: 0x01BB96DC
10:24:22:347 GCF_ResetDeviceDone
10:24:22:348 bootloader v3 update firmware request size: 164227, addr: 0x00005000, type: 31, crc-32: 0xAAAAAAAA
10:24:22:348 TX c0810383810200005000001faaaaaaaa5ffbc0
10:24:22:355 SLIP RX frame length: 3
flashing 164227 bytes: |=10:24:22:361 SLIP RX frame length: 8
10:24:22:361 updateFirmwareV3DataRsp()
10:24:22:361 bootloader v3 data request, offset: 0, length: 256
10:24:22:361 bootloader v3 send data response, status: 0, offset: 0, length: 256
10:24:22:361 TX c0818400000000000001357f42de8176ae00f0199006e51deb6a7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af7b7ad7c401eab6af4b65c0
retry, failed

The UI tells me that the Firmware is not connected. Any help would appreciated!!
Thanks!

Hi @janbrodhaecker ,

What is your environment? Is it native, docker or other vm?

Hi @TheNON75,

sorry - I forgot to mention - its on Raspberry Pi 3 Model B Plus Rev 1.3, running Raspbian 10 (Buster).

Hope this answers your question :slight_smile:

@janbrodhaecker
Maybe you find the answer there:
https://forum.phoscon.de/t/trying-to-get-deconz-2-13-0-but-not-available