Can not write IEEE to zb-gw04 v1.2

[0xphk]

Hi, some background:

I migrated this ZHA EZSP radio to SLZB and want to use it as a router.

As the SLZB copied the IEEE addr, I seem not to be able to use the old dongle with Nerivec's router firmware as both devices now share the same IEEE.

The SLZB has an option to change it but I migrated 60+ devices without repairing, so this is not an option for me.

When probing, it just returns:

$ universal-silabs-flasher --device /dev/ttyUSB0 probe
2025-12-14 17:02:49.810 ark universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2025-12-14 17:02:49.880 ark universal_silabs_flasher.flasher INFO Detected bootloader version '3.1.2'
2025-12-14 17:02:49.881 ark universal_silabs_flasher.flasher INFO Detected ApplicationType.GECKO_BOOTLOADER, version '3.1.2' at 115200 baudrate (bootloader baudrate 115200)

when trying to write the IEEE addr it gives a similar error

$ universal-silabs-flasher -vv --device /dev/ttyUSB0 write-ieee --ieee 00124b002a7b0dae
2025-12-14 16:55:46.995 ark asyncio DEBUG Using selector: EpollSelector
2025-12-14 16:55:46.995 ark universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2025-12-14 16:55:46.995 ark zigpy.serial DEBUG Opening a serial connection to '/dev/ttyUSB0' (baudrate=115200, xonxoff=False, rtscts=False)
2025-12-14 16:55:47.050 ark zigpy.serial DEBUG Connection made: SerialTransport(<_UnixSelectorEventLoop running=True closed=False debug=False>, <universal_silabs_flasher.gecko_bootloader.GeckoBootloaderProtocol object at 0x7a93201b5550>, Serial<id=0x7a932017e1d0, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=0, xonxoff=False, rtscts=False, dsrdtr=False))
2025-12-14 16:55:47.051 ark universal_silabs_flasher.gecko_bootloader DEBUG Sending data b'\n'
2025-12-14 16:55:47.052 ark universal_silabs_flasher.gecko_bootloader DEBUG Sending data GeckoBootloaderOption.EBL_INFO
2025-12-14 16:55:47.055 ark universal_silabs_flasher.gecko_bootloader DEBUG Parsing State.WAITING_FOR_MENU: bytearray(b'\r\nGecko Bootloader v3.01.02\r\n1. ')
2025-12-14 16:55:47.058 ark universal_silabs_flasher.gecko_bootloader DEBUG Parsing State.WAITING_FOR_MENU: bytearray(b'\r\nGecko Bootloader v3.01.02\r\n1. upload gbl\r\n2. run\r\n3. ebl info\r')
2025-12-14 16:55:47.060 ark universal_silabs_flasher.gecko_bootloader DEBUG Parsing State.WAITING_FOR_MENU: bytearray(b'\r\nGecko Bootloader v3.01.02\r\n1. upload gbl\r\n2. run\r\n3. ebl info\r\nBL > \x00\r\nGecko Bootloader v3.01.')
2025-12-14 16:55:47.061 ark universal_silabs_flasher.gecko_bootloader DEBUG Detected version string '3.01.02'
2025-12-14 16:55:47.061 ark zigpy.serial DEBUG Waiting for serial port to close
2025-12-14 16:55:47.069 ark zigpy.serial DEBUG Connection lost: None
2025-12-14 16:55:47.069 ark universal_silabs_flasher.flasher DEBUG Probe result: ProbeResult(version='3.1.2', continue_probing=[], baudrate=115200)
2025-12-14 16:55:47.070 ark universal_silabs_flasher.flasher INFO Detected bootloader version '3.1.2'
2025-12-14 16:55:47.070 ark universal_silabs_flasher.flasher INFO Detected ApplicationType.GECKO_BOOTLOADER, version '3.1.2' at 115200 baudrate (bootloader baudrate 115200)
Error: Device is not running EmberZNet: ApplicationType.GECKO_BOOTLOADER

I did upgrade the old 1.9.2 bootloader to 3.1.2 from Nerivec's repo, maybe this causes the issue?

Can you please advice?

[puddly]

Unplug it and plug it back in. If it still shows the bootloader prompt, it's likely that upgrading the bootloader erased the application so your device has no firmware. You should install the correct firmware to it in that case.

[0xphk]

I tried this several times and when this was shown, different firmware versions were tested (ncp,rcp)

Is the older bootloader 1.9.2 available somewhere and should I try to downgrade it again then?

[puddly]

You generally can't downgrade or re-install the bootloader itself, I'm afraid, last I checked the bootloader only allows you to upgrade.

The bootloader however shouldn't be playing a role here, it doesn't really do much. Did you install Zigbee firmware? The EUI64 address can only be written from there.