Closed derbirch closed 6 months ago
Which firmware did you flash?
In anycase if the flash was interrupted, you will need to force a bootloader reset. The code for the ihost to do this isnt merged yet but you can find it here:
https://github.com/NabuCasa/universal-silabs-flasher/pull/51
On the ihost you can do this
wget https://codeload.github.com/NabuCasa/universal-silabs-flasher/legacy.tar.gz/pull/51/head -O flasher.tar.gz
tar -xzvf flasher.tar.gz
cd NabuCasa-universal-silabs-flasher-98dc8da
python -m universal_silabs_flasher --device /dev/ttyS4 --bootloader-reset ihost --probe-method bootloader flash --firmware <<new_firmware.gbl>>
However if you are in ssh terminal (addon) you may need to install dependencies also:
python3 -m venv user
. ./user/bin/activate
pip install --find-links "https://wheels.home-assistant.io/musllinux" --prefer-binary universal-silabs-flasher
Which firmware did you flash?
In anycase if the flash was interrupted, you will need to force a bootloader reset. The code for the ihost to do this isnt merged yet but you can find it here:
NabuCasa/universal-silabs-flasher#51
On the ihost you can do this
wget https://codeload.github.com/NabuCasa/universal-silabs-flasher/legacy.tar.gz/pull/51/head -O flasher.tar.gz tar -xzvf flasher.tar.gz cd NabuCasa-universal-silabs-flasher-98dc8da python -m universal_silabs_flasher --device /dev/ttyS4 --bootloader-reset ihost --probe-method bootloader flash --firmware <<new_firmware.gbl>>
However if you are in ssh terminal (addon) you may need to install dependencies also:
python3 -m venv user . ./user/bin/activate pip install --find-links "https://wheels.home-assistant.io/musllinux" --prefer-binary universal-silabs-flasher
Thankx for the guide!
For your question, I actually forgot which firmware screwed up my setup.
I tried both rcp-uart-802154-v4.3.1-zbdonglee-115200.gbl
and ncp-uart-hw-v7.3.2.0-zbdonglee-115200.gbl
following your guide. And they all seemed to be flashed 100%, but the flash command did not exit itself. When I type ctr+c, it tells me Aborted!
. And I went back to ZHA and Multipotocal addon, they all failed to set up.
Sorry for posting a pic full of text, I can not copy them from WebUI
I think might be a bug in the GPIO PR that my patches depend on. but you can check if it flashed succesfully afterwards. I suspect its just stuck in bootloader mode.
EDIT: Even though it gets stuck at 100% it appears to have completed successfully
python -m universal_silabs_flasher --device /dev/ttyS4 probe
I think might be a bug in the GPIO PR that my patches depend on. but you can check if it flashed succesfully afterwards. I suspect its just stuck in bootloader mode.
EDIT: Even though it gets stuck at 100% it appears to have completed successfully
python -m universal_silabs_flasher --device /dev/ttyS4 probe
Thanks! That little cutie worked like a charm! The thread performance is not that ideal though. I tested some Homekit over Thread devices, the Eve Aqua went offline sometimes, but yeah it worked!
Even though it gets stuck at 100% it appears to have completed successfully
This is just getting stuck waiting for the bootloader menu to reappear after flashing. It has fully completed flashing. I suspect the bootloader on these is buggy and will look at preparing updated bootloader for these.
The flash for on-board zigged chip would fail with the firmware given in the wiki page at some point. My first attempts worked, but when I started to try other options like other series ports as well as firmwares, they all failed. And I could not get back to the version that once worked.
I figured out that the CRC error I mentioned in HA community should be caused by insufficient power supply, but the
Error: Failed to probe running application type
remained still.After the flash, ZHA wizard shows "Failed to connect," when I follow your guide.
Hardware: iHost 2GB version
Here's the log for reference, if you need any further info, I'm glad to help