Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[REQUEST] EmberZNet 6.7.10.0 (6.7.10.x) Zigbee Coordinator firmware images? #17

Closed
Hedda opened this issue Nov 26, 2021 · 15 comments
Closed

Comments

@Hedda
Copy link
Contributor

Hedda commented Nov 26, 2021

FYI; Silicon Labs has released Silabs Zigbee EmberZNet SDK 6.7.10 (6.7.10.0 GA) bugfix release including support for older chips:

https://cn.silabs.com/documents/public/release-notes/emberznet-release-notes-6.7.10.0.pdf

zigpy/zigpy#595 (comment)

Note! Should note that there will not ever be any 6.8.x.x or later releases for EM35xx/EM35x as that hardware is now end-of-life.

@grobasoz
Copy link
Owner

Thanks @Hedda - seems like a few important issues have been resolved in this release :) I've been using it for a while and will start updating this repository as time permits. Gary.

@Hedda
Copy link
Contributor Author

Hedda commented Dec 20, 2021

While don't have an EM3581 based adapter myself I would still like to request prioritizing a new 6.7.10.x firmware update for it.

Reason is a lot of people already got Nortek HUSBZB-1 stick who upgrade via -> https://github.com/walthowd/husbzb-firmware

Copy of the same request opened here -> walthowd/husbzb-firmware#36 (the latest release for EM3581 is still EmberZNet 6.7.8)

I did note however that you have a @walthowd folder with specified settings so guess that might need separate releases for him?

https://github.com/grobasoz/zigbee-firmware/tree/master/EM3581/%40walthowd

Specific Settings for this folder

CONFIG_APS_UNICAST_MESSAGE_COUNT: 20
CONFIG_MAX_END_DEVICE_CHILDREN: 32
CONFIG_SOURCE_ROUTE_TABLE_SIZE: 200
CONFIG_ROUTE_TABLE_SIZE: 16
CONFIG_ADDRESS_TABLE_SIZE: 16

@grobasoz
Copy link
Owner

I have updated the EM3581 versions including walthowd's specific release. PC5 is used for TX Active and PC6 for nTX Active.

@sreknob
Copy link

sreknob commented Dec 22, 2021

Thanks a lot Gary for working on this!
I've tried the generic 6710 and the 115K2-W variant without success so far on my HUSBZB-1.
I get the banner back when starting upload.

root@677a98369618:/tmp/silabs# ./ncp.py scan
Connecting to.. /dev/ttyUSB1 115200 True False 
{"ports": [{"port": "/dev/ttyUSB1", "vid": "10C4", "pid": "8A2A", "deviceType": "zigbee", "stackVersion": "6.7.8-373"}]}
root@677a98369618:/tmp/silabs# ./ncp_new.py flash -p /dev/ttyUSB1 -f NCP_USW_EM3581_6710-115k2-W.ebl
Restarting NCP into Bootloader mode...
CEL stick
EM3581 Serial Bootloader v5.4.1.0 b962

Successfully restarted into bootloader mode! Starting upload of NCP image... 
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\r' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\n' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'S' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'e' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'r' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'i' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'a' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'l' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b' ' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'u' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'p' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'l' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'o' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'a' for block 1
ERROR:xmodem.XMODEM:send error: NAK received 17 times, aborting.
NCP upload failed. Please reload a correct NCP image to recover.
Rebooting NCP...

From my recollection, there we comments about this being a bootloader issue last time at 6.7.8. Not sure how it was solved.

I haven't tried minicom directly yet...

EDIT: Found what you thought was the magic sauce in your post here

@grobasoz
Copy link
Owner

I still don't have an EM3581 to test on but the EM3581 code can be flashed into an EM3585 using an Ember ISA3 and works fine. The serial bootloader (eg that ncp uses) checks the chip ID so can't be uploaded to an incorrect chip.

@sreknob
Copy link

sreknob commented Dec 23, 2021

Thanks Gary. Last time there was the same issue with HUSBZB-1 I believe you fixed it using an older compiler.
I'll see if anyone else can get it to work or I'll try XMODEM but that also had the same result before.

@grobasoz
Copy link
Owner

grobasoz commented Dec 23, 2021

@sreknob - Thanks for testing - apologies for it not working. I am confused however. I have tried flashing EM3581 code to my EM3587 test setup and it works there as well. The development system is set to the older IAR compiler so that shouldn't be the issue. I'll see if I can source a HUSBZB-1 for testing.
Edit> Tested EM3581 code on EM3588 module as well - works!

@grobasoz
Copy link
Owner

grobasoz commented Jan 7, 2022

@sreknob - Apologies for the delays getting to this - I was waiting for a HUSBZB-1 to arrive - and sadly I still can't find stock. I have added a new version to the repository recompiled on the latest IAR Compiler to see if that works. If you get a chance please test on your equipment. Thanks Gary.

@sreknob
Copy link

sreknob commented Jan 10, 2022

Hey Gary!
Thanks so much for continuing to work on this. Old defunct hardware is always hard to source :-)

Anyway, whatever it is with your compiler, you have once again found the magic sauce!
Uploaded without problems to my HUSBZB-1.
Just fired Home Assistant up and it's chugging along like usual!

pi@raspberrypi:~/husbzb-firmware $ ./ncp-115k2.py flash -p /dev/ttyUSB1 -f NCP_USW_EM3581_6710.ebl 
Restarting NCP into Bootloader mode...
CEL stick
EM3581 Serial Bootloader v5.4.1.0 b962

Successfully restarted into bootloader mode! Starting upload of NCP image... 
Finished!
Rebooting NCP...
pi@raspberrypi:~/husbzb-firmware $ ./ncp-115k2.py scan
Connecting to.. /dev/ttyUSB1 115200 True False 
Connecting to.. /dev/ttyUSB0 115200 True False 
{"ports": [{"stackVersion": "6.7.10-423", "deviceType": "zigbee", "pid": "8A2A", "port": "/dev/ttyUSB1", "vid": "10C4"}, {"deviceType": "unknown", "pid": "8A2A", "port": "/dev/ttyUSB0", "vid": "10C4"}, {"deviceType": "unknown", "port": "/dev/ttyAMA0"}]}

This is great!!

I know that you compiled specific zigbee settings for @walthowd for his repo. I'm not sure what the zigbee settings were on this latest version but it flashed and is operating at 115K2 no problem on my Home Assistant instance currently.

You're my hero 🥇

Blake

@grobasoz
Copy link
Owner

Thanks for testing and replying Blake - much appreciated :)
I have recompiled the @walthowd versions but as you mentioned my standard version should run OK with his settings.
Gary.

@Mazotis
Copy link

Mazotis commented Jan 15, 2022

Tried flashing the latest version on my HUSBZB-1 and I get the same result as @sreknob earlier

./ncp.py flash -p /dev/ttyUSB1 -f NCP_USW_EM3581_6710.ebl
Restarting NCP into Bootloader mode...
CEL stick
EM3581 Serial Bootloader v5.4.1.0 b962

Successfully restarted into bootloader mode! Starting upload of NCP image... 
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\r' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\n' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'S' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'e' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'r' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'i' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'a' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'l' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b' ' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'u' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'p' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'l' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'o' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'a' for block 1
ERROR:xmodem.XMODEM:send error: NAK received 17 times, aborting.
NCP upload failed. Please reload a correct NCP image to recover.
Rebooting NCP...

Tried with the W variant as well, and tried flashing 6.7.8 115k baud rate before (I was on 57k), no success. Was the file modified since the last comments ?

EDIT - Sorry for the report. Redownloaded the file, rebooted the dongle and retried again - confirmed working.

Connecting to.. /dev/ttyUSB1 115200 True False 
{"ports": [{"port": "/dev/ttyUSB1", "vid": "10C4", "pid": "8A2A", "deviceType": "zigbee", "stackVersion": "6.7.10-423"}]}

Thanks for your work!

@grobasoz
Copy link
Owner

@Mazotis - Thanks for the update - I was worried I had broken something again...

@cvocvo
Copy link

cvocvo commented Sep 24, 2022

I've been attempting to update my HUSBZB-1 and have the same errors as noted above. I tried all 3 6.7.10 images (regular + walthowd 56k + walthowd 115k) and have the same issue. I am doing this on Windows, however, I can flash the 6.7.8 firmware just fine.

As noted above and over here: walthowd/husbzb-firmware#36 (comment) there does appear to be some success doing this, but I can't get it to work.

Any ideas?

Here's my log / error data:

PS C:\temp\husbzb-firmware> python .\ncp.py flash -p COM3 -f "C:\temp\zigbee_6.7.10\NCP_USW_EM3581_6710.ebl"
Restarting NCP into Bootloader mode...
CEL stick
EM3581 Serial Bootloader v5.4.1.0 b962

Successfully restarted into bootloader mode! Starting upload of NCP image...
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\r' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\n' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'S' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'e' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'r' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'i' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'a' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'l' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b' ' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'u' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'p' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'l' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'o' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'a' for block 1
ERROR:xmodem.XMODEM:send error: NAK received 17 times, aborting.
NCP upload failed. Please reload a correct NCP image to recover.
Rebooting NCP...
PS C:\temp\husbzb-firmware> python .\ncp.py flash -p COM3 -f "C:\temp\zigbee_6.7.10\NCP_USW_EM3581_6710-57k6-W.ebl"
Restarting NCP into Bootloader mode...
CEL stick
EM3581 Serial Bootloader v5.4.1.0 b962

Successfully restarted into bootloader mode! Starting upload of NCP image...
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\r' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\n' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'S' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'e' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'r' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'i' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'a' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'l' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b' ' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'u' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'p' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'l' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'o' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'a' for block 1
ERROR:xmodem.XMODEM:send error: NAK received 17 times, aborting.
NCP upload failed. Please reload a correct NCP image to recover.
Rebooting NCP...
PS C:\temp\husbzb-firmware> python .\ncp.py flash -p COM3 -f "C:\temp\zigbee_6.7.10\NCP_USW_EM3581_6710-115k2-W.ebl"
Restarting NCP into Bootloader mode...
CEL stick
EM3581 Serial Bootloader v5.4.1.0 b962

Successfully restarted into bootloader mode! Starting upload of NCP image...
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\r' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\n' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'S' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'e' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'r' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'i' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'a' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'l' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b' ' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'u' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'p' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'l' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'o' for block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'a' for block 1
ERROR:xmodem.XMODEM:send error: NAK received 17 times, aborting.
NCP upload failed. Please reload a correct NCP image to recover.
Rebooting NCP...
PS C:\temp\husbzb-firmware> python .\ncp.py scan
Connecting to.. COM3 57600 True False
Exception: <class 'IndexError'> COM1
{"ports": [{"port": "COM3", "vid": "10C4", "pid": "8A2A", "deviceType": "zigbee", "stackVersion": "6.7.8-373"}, {"port": "COM1", "deviceType": "unknown"}]}
PS C:\temp\husbzb-firmware> python .\ncp.py flash -p COM3 -f "C:\temp\husbzb-firmware\ncp-uart-sw-6.7.8.ebl"
Restarting NCP into Bootloader mode...
CEL stick
EM3581 Serial Bootloader v5.4.1.0 b962

Successfully restarted into bootloader mode! Starting upload of NCP image...
Finished!
Rebooting NCP...
PS C:\temp\husbzb-firmware> python .\ncp.py scan
Connecting to.. COM3 57600 True False
Exception: <class 'IndexError'> COM1
{"ports": [{"port": "COM3", "vid": "10C4", "pid": "8A2A", "deviceType": "zigbee", "stackVersion": "6.7.8-373"}, {"port": "COM1", "deviceType": "unknown"}]}
PS C:\temp\husbzb-firmware>

image

@grobasoz
Copy link
Owner

@cvocvo - Sorry I am away for a few days on site - not able to assist you at this stage.

@localboast
Copy link

Man I tried everything to get the upgrade to work with my Nortek husbzb-1. I am able to flash Walt's version to 6.7.8-115k but I'm stuck here. I modified the ncp.py file for 115200 in both spots but no matter what 6.7.10 version in @grobasoz repo I try to load I get the xmodem errors reported above. Bummer.

Happy that other folks were able to get it going, wish I could say the same. I read through the relevant topics here on GitHub numerous times, and think I tried it all (including 57600 variants).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants