I think I bricked my aeotec-zga008 with the wrong baudrate firmware, any suggestions whether it might be recoverable?

[rik-c]

Hello, I tried to flash one of the images here but I think bricked my aeotec-zga008. I used the Nabucasa Universal Silabs flasher (https://github.com/NabuCasa/universal-silabs-flasher) with the most recent ncp-uar-hw 230400 baud image (https://github.com/darkxst/silabs-firmware-builder/raw/main/firmware_builds/aeotec-zga008/ncp-uart-hw-v7.4.3.0-aeotec-zga008-230400.gbl).

Don't know if this place is only for dev questions? But if this type of query is OK than any help would be appreciated.

This is log from the universal SiLabs flasher:

rik@orangepizero2:~/flasher/bin$ rik@orangepizero2:~/flasher/bin$ sudo ./universal-silabs-flasher --device /dev/ttyUSB0 flash --firmware ncp-uart-hw-v7.4.3.0-aeotec-zga008-230400.gbl 2024-08-20 21:30:07.669 orangepizero2 universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.4.3', ezsp_version='7.4.3.0', ot_rcp_version=None, cpc_version=None, fw_type=<FirmwareImageType.NCP_UART_HW: 'ncp-uart-hw'>, baudrate=230400) 2024-08-20 21:30:07.670 orangepizero2 universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud 2024-08-20 21:30:09.693 orangepizero2 universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 230400 baud 2024-08-20 21:30:14.725 orangepizero2 universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 115200 baud 2024-08-20 21:30:16.085 orangepizero2 universal_silabs_flasher.flasher INFO Detected ApplicationType.EZSP, version '6.10.9.0 build 464' (6.10.9.0.464) at 115200 baudrate (bootloader baudrate None) 2024-08-20 21:30:16.086 orangepizero2 universal_silabs_flasher.flash INFO Firmware baudrate 115200 differs from expected baudrate 230400 2024-08-20 21:30:22.425 orangepizero2 universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud 2024-08-20 21:30:23.459 orangepizero2 universal_silabs_flasher.flasher INFO Detected bootloader version '1.12.10' 2024-08-20 21:30:23.460 orangepizero2 universal_silabs_flasher.flasher INFO Detected ApplicationType.GECKO_BOOTLOADER, version '1.12.10' at 115200 baudrate (bootloader baudrate 115200) ncp-uart-hw-v7.4.3.0-aeotec-zga008-230400.gbl [####################################] 100%
The message stating that the firmware baudrate was different from the expected baudrade already made me a little nervous. And indeed after a probe nothing was detected.:

rik@orangepizero2:~/flasher/bin$ sudo ./universal-silabs-flasher --device /dev/ttyUSB0 probe 2024-08-20 21:31:38.960 orangepizero2 universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud 2024-08-20 21:31:40.983 orangepizero2 universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud 2024-08-20 21:31:45.333 orangepizero2 universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 115200 baud 2024-08-20 21:31:49.682 orangepizero2 universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 230400 baud 2024-08-20 21:31:54.031 orangepizero2 universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 115200 baud 2024-08-20 21:31:59.069 orangepizero2 universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud Error: Failed to probe running application type

Just to be sure I then tried to flash the 1152000 baud FW but that doesn't work if the running application type cannot be probed.

After that saw that I read over the message in the original probe that I did before flashing stating the baudrate. So I guess I flashed the incorrect baudrate firmware...

rik@orangepizero2:~/flasher/bin$ sudo ./universal-silabs-flasher --device /dev/ttyUSB0 probe 2024-08-20 21:16:15.286 orangepizero2 universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud 2024-08-20 21:16:17.316 orangepizero2 universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud 2024-08-20 21:16:21.659 orangepizero2 universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 115200 baud 2024-08-20 21:16:26.008 orangepizero2 universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 230400 baud 2024-08-20 21:16:30.357 orangepizero2 universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 115200 baud 2024-08-20 21:16:31.728 orangepizero2 universal_silabs_flasher.flasher INFO Detected ApplicationType.EZSP, version '6.10.9.0 build 464' (6.10.9.0.464) at 115200 baudrate (bootloader baudrate None) 2024-08-20 21:16:31.729 orangepizero2 universal_silabs_flasher.flash INFO Dumping EmberZNet Config CONFIG_PACKET_BUFFER_COUNT=75 CONFIG_NEIGHBOR_TABLE_SIZE=26 CONFIG_APS_UNICAST_MESSAGE_COUNT=10 CONFIG_BINDING_TABLE_SIZE=32 CONFIG_ADDRESS_TABLE_SIZE=8 CONFIG_MULTICAST_TABLE_SIZE=8 CONFIG_ROUTE_TABLE_SIZE=16 CONFIG_DISCOVERY_TABLE_SIZE=8 CONFIG_STACK_PROFILE=0 CONFIG_SECURITY_LEVEL=5 CONFIG_MAX_HOPS=30 CONFIG_MAX_END_DEVICE_CHILDREN=32 CONFIG_INDIRECT_TRANSMISSION_TIMEOUT=3000 CONFIG_END_DEVICE_POLL_TIMEOUT=8 CONFIG_TX_POWER_MODE=0 CONFIG_DISABLE_RELAY=0 CONFIG_TRUST_CENTER_ADDRESS_CACHE_SIZE=0 CONFIG_SOURCE_ROUTE_TABLE_SIZE=7 CONFIG_FRAGMENT_WINDOW_SIZE=1 CONFIG_FRAGMENT_DELAY_MS=0 CONFIG_KEY_TABLE_SIZE=12 CONFIG_APS_ACK_TIMEOUT=1600 CONFIG_ACTIVE_SCAN_DURATION=3 CONFIG_END_DEVICE_BIND_TIMEOUT=60 CONFIG_PAN_ID_CONFLICT_REPORT_THRESHOLD=2 CONFIG_REQUEST_KEY_TIMEOUT=0 CONFIG_CERTIFICATE_TABLE_SIZE=0 CONFIG_APPLICATION_ZDO_FLAGS=0 CONFIG_BROADCAST_TABLE_SIZE=15 CONFIG_MAC_FILTER_TABLE_SIZE=0 CONFIG_SUPPORTED_NETWORKS=1 CONFIG_SEND_MULTICASTS_TO_SLEEPY_ADDRESS=0 CONFIG_ZLL_GROUP_ADDRESSES=1 CONFIG_ZLL_RSSI_THRESHOLD=128 CONFIG_MTORR_FLOW_CONTROL=1 CONFIG_RETRY_QUEUE_SIZE=16 CONFIG_NEW_BROADCAST_ENTRY_THRESHOLD=9 CONFIG_TRANSIENT_KEY_TIMEOUT_S=300 CONFIG_BROADCAST_MIN_ACKS_NEEDED=255 CONFIG_TC_REJOINS_USING_WELL_KNOWN_KEY_TIMEOUT_S=300 CONFIG_CTUNE_VALUE=140 CONFIG_ASSUME_TC_CONCENTRATOR_TYPE=1
After this I tried the 'Elelabs' flashing tool provided by the manufacturer: https://aeotec.freshdesk.com/support/solutions/articles/6000270951-update-zi-stick-to-thread-or-zigbee-with-python-3-9-and-windows

On my Windows computer the device is seen as USB to serial device (CH340) but the Elelabs flashing tool cannot communicate with the device. Interestingly the Elelabs tool than states that rebooting into the X-MODEM mode worked. But it then fails to load the bootloader.

I've tried flashing the provided images by AEOTEC as well as the 7.4.3.0 115200 baud firmware.

C:\Lokaal\elelabs-zigbee-ezsp-utility-master>python Elelabs_EzspFwUtility.py flash -f ncp-uart-hw-v7.4.3.0-aeotec-zga008-115200.gbl -p COM5 2024/08/20 22:11:33 Elelabs_EzspFwUtility: Couldn't communicate with the adapter in Zigbee (EZSP) mode, Thread (Spinel) mode or bootloader mode 2024/08/20 22:11:40 Elelabs_EzspFwUtility: Successfully restarted into X-MODEM mode! Starting upload of the new firmware... DO NOT INTERRUPT(!) 2024/08/20 22:11:52 Elelabs_EzspFwUtility: Failed to restart into bootloader mode. Please see users guide.

(The user guide offers nothing particulary helpful)

I suppose that I've thouroughly bricked my Zi-Stick. But if anyone might have some further suggestions that would be greatly appreciated.

And no wories, I also have a Sonoff Dongle-E lying around. But I wanted to avoid having to re-pair all my Zigbee wall switches ;-)

[darkxst]

for 230400 you need to specify baudrate as parameter, as its not probed by default.

universal-silabs-flasher --device /dev/ttyUSB0 --ezsp-baudrate 2300400 probe

[rik-c]

Ok, I've tried that, makes sense.

I'm also not getting any running application type probed at 230400 baud.

This is what I get from the verbose log for the EZSP probing:

2024-08-21 08:05:44.563 orangepizero2 universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 2300400 baud 2024-08-21 08:05:44.568 orangepizero2 zigpy.serial DEBUG Opening a serial connection to '/dev/ttyUSB0' (baudrate=2300400, xonxoff=True, rtscts=False) 2024-08-21 08:05:44.598 orangepizero2 bellows.ezsp DEBUG Resetting EZSP 2024-08-21 08:05:44.599 orangepizero2 bellows.uart DEBUG Resetting ASH 2024-08-21 08:05:44.600 orangepizero2 bellows.ash DEBUG Sending frame CANCEL + RstFrame() + FLAG 2024-08-21 08:05:44.602 orangepizero2 bellows.ash DEBUG Sending data 1ac038bc7e

[darkxst]

does the dongle work in ZHA or Z2M if you set baudrate to 230400?

[rik-c]

Just tried running Z2M with 'ember' as adapter setting and baudrate 230400 an it works! Great, thanks! Just wondering now why probing at that baudrate with the universal-silabs-flasher didn't work. And I'm wondering whether there is a way to flash it to the 115200 baud versions of the fw or a future fw releases if both flashing tools that I tried currently don't detect the adapter.

[darkxst]

given it works in Z2M, it should be possible to get it flashed back to 115200. Perhaps check that no other app has the serial port opened when you run universal-silabs-flasher.

[rik-c]

Alright, I was able to to flash the 115200 version of the ncp-uart-hw-v7.4.3.0-aeotec-zga008 fw with the option --ezsp-baudrate 230400 during flashing.

It appears the reason is pretty trivial why it didn't work initially: I copied the command from your first reaction. However, I now see it has a typo in the baudrate: 2300400 instead of 230400.

Thanks for helping me out!