-
Notifications
You must be signed in to change notification settings - Fork 41
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
Starts bootloader but doesn't recognize success? #51
Comments
I have the same issue. I assume it has also something todo with the "Scan", because when i do a scan first, i have also to break it. CMD: ./ncp.py scan |
Are you trying to scan for the zwave tty or am I misunderstanding? I do not believe this script is supposed to be able to upgrade the zwave firmware--only zigbee. |
I am having a similar issue. It simply hangs at the bootloader screen. Then I CTRL-C it after a few minutes.
|
Referring to this issue resolved my issue |
I'm having the same issue as #50 (but I'm posting a new issue because the Cyrillic topic probably isn't helpful to most users, no offense intended).
I'm trying to flash ncp-uart-6.7.8-115k.ebl on nortek husbzb-1 with 5.4.1-194 (brand new device) using the docker image. After 'CEL stick' I get 'EM3581 Serial Bootloader v.5.4.1.0 b962' followed by a newline and then the script hangs (and I have to kill it). Good news is no damage done to the device, but other than than nothing seems to happen.
I initiatized my device in minicom and it reacts as expected (both from the README and how the script works), and a string of 'C's were received. However, for some reason we don't get to L364 ('Successfully restarted ...') in ncp.py. Looking for suggestions.
husbzb-firmware/ncp.py
Lines 343 to 364 in d6a512c
The text was updated successfully, but these errors were encountered: