search

Elelabs / elelabs-zigbee-ezsp-utility

Elelabs Zigbee EZSP Utility to perform firmware update on a range of Elelabs EZSP products as well as other generic EZSP adapters.
Apache License 2.0
137 stars 27 forks source link

Couldn't communicate with the adapter #38

Open aamiel1 opened 1 year ago

aamiel1 commented 1 year ago

After update [TYZS13] (see log) I couldn't communicate with the adapter in Zigbee...

Elelabs_EzspFwUtility.py flash -f efr32mg13p-v8-6910-57600.gbl -p COM13 Elelabs_EzspFwUtility: Generic Zigbee EZSP adapter detected: Elelabs_EzspFwUtility: Firmware: 6.5.0-188 Elelabs_EzspFwUtility: EZSP v7 Elelabs_EzspFwUtility: Launch in bootloader mode Elelabs_EzspFwUtility: EZSP adapter in bootloader mode detected: Elelabs_EzspFwUtility: Gecko Bootloader v1.8.0 Elelabs_EzspFwUtility: Successfully restarted into X-MODEM mode! Starting upload of the new firmware... DO NOT INTERRUPT(!) ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... .. Elelabs_EzspFwUtility: Firmware upload complete Elelabs_EzspFwUtility: Rebooting NCP... Elelabs_EzspFwUtility: Couldn't communicate with the adapter in Zigbee (EZSP) mode, Thread (Spinel) mode or bootloader mode

I try to run: Elelabs_EzspFwUtility.py restart -m btl -p COM13 Response: Elelabs_EzspFwUtility: Couldn't communicate with the adapter in Zigbee (EZSP) mode, Thread (Spinel) mode or bootloader mode

Also I try to run: Elelabs_EzspFwUtility.py restart -m nrml -p COM13 Response: Elelabs_EzspFwUtility: Couldn't communicate with the adapter in Zigbee (EZSP) mode, Thread (Spinel) mode or bootloader mode

Any other idea?

NilsBohr commented 1 year ago

based on the filename 57600.gbl Your new firmware is using 57600 baudrate. The default baudrate used by the utility is 115200.

try specifying the baudrate manually -b 57600

P.S. if that works I recommend you to find a fimrware with 115200 baudrate, as it's a more common one

aamiel1 commented 1 year ago

Thanks,

Now if I run the command: Elelabs_EzspFwUtility.py restart -m nrml -p COM13 -b 57600 It work OK... Elelabs_EzspFwUtility: Generic Zigbee EZSP adapter detected: Elelabs_EzspFwUtility: Firmware: 6.9.1-214 Elelabs_EzspFwUtility: EZSP v8 Elelabs_EzspFwUtility: Allready in normal mode. No need to restart

but if I run the command: Elelabs_EzspFwUtility.py restart -m btl -p COM13 -b 57600 I couldn't reset into bootloader mode... Elelabs_EzspFwUtility: Generic Zigbee EZSP adapter detected: Elelabs_EzspFwUtility: Firmware: 6.9.1-214 Elelabs_EzspFwUtility: EZSP v8 Elelabs_EzspFwUtility: Launch in bootloader mode Elelabs_EzspFwUtility: Couldn't communicate with the adapter in Zigbee (EZSP) mode, Thread (Spinel) mode or bootloader mode

OR Elelabs_EzspFwUtility.py restart -m btl -p COM13 -b 57600 -d RAW Elelabs_EzspFwUtility: RESET FRAME Elelabs_EzspFwUtility: [ ASH REQUEST ] 1a c0 38 bc 7e Elelabs_EzspFwUtility: [ SPINEL REQUEST ]: 80 01 Elelabs_EzspFwUtility: [ HDLC REQUEST ]: 7e 80 01 02 92 7e Elelabs_EzspFwUtility: [ HDLC RESPONSE ]: 7e 00 7e Elelabs_EzspFwUtility: Couldn't communicate with the adapter in Zigbee (EZSP) mode, Thread (Spinel) mode or bootloader mode

and if I couldn't reset into bootloader mode I cannot flash the adapter

Any idea what the problem?

NilsBohr commented 1 year ago

I think your current bootloader is also 57600. Our utility is right now hardcoded to talk to the bootloader using 115200 baudrate.

Try using 3rd party utility like TeraTerm to talk to it and send your new file using TeraTerm XMODEM send. Or you can wait when we add 57600 baudrate for the bootloader communication, but, that won't happen any time soon.

Or you can modify the Python utility to talk to the bootloader using 57600

aamiel1 commented 1 year ago

Hi,

I tried all the options you mentioned, the problem seems to be that the adapter cannot be put into bootloader mode after I update it to efr32mg13p-v8-6910-57600.gbl firmware...

Maybe you have more ideas?