Open brodock opened 6 months ago
Hmm yeh the webflasher doesnt probe 230400. but you can use universal-silabs-flasher directly
universal-silabs-flasher --device /dev/ttyACM0 --ezsp-baudrate 230400 probe
Assume the reason why this is the same is that Nabu Casa themselves have so far only released builds using 115200 and 460800?
https://github.com/NabuCasa/silabs-firmware
Could the webflasher be extended to also probe 230400 and 57600 baud rate speeds?
FYI, I believe that some radio libraries for zigpy tries to probe the most common baud rates in sequence.
i.e. 57600 -> 115200 > 230400 -> 460800 -> 576000 -> 921600
PS: There are at least other community firmware builders that have release firmware builds that uses 57600 and 230400.
It can be configured but each extra probe takes extra time. NCP 230400 is not really popular and so I mainly target the baudrates used by the webflasher provided firmware. I suppose i didnt account for people using the custom url option though!
I have fallen into the same trap. I programmed ncp-uart-hw-v7.3.2.0-zbdonglee-230400 into a Sonoff Dongle E. It's working fine in z2m but I can no longer access the dongle from your webflasher. I have installed universal-silabs-flasher into my desktop Linux mint but I can't get it to run so I am stuck. Wish I looked here before I did it!
I managed to sort out the privileges in Mint and installed ncp-uart-hw-v7.3.2.0-zbdonglee-115200 and it's visible in the webflasher again. It is time to buy a backup dongle just in case I brick it next time ...
I managed to sort out the privileges
make sure your user is part of the dialout
group, which gives access to all USB serial devices!
I managed to sort out the privileges
make sure your user is part of the
dialout
group, which gives access to all USB serial devices!
Yes thanks that was the problem.
230400 is not really popular and so I mainly target the baudrates used by the webflasher provided firmware
FYI, Nabu Casa actually started with 230400 at one point but reverted to 115200 for simplicity -> https://github.com/NabuCasa/silabs-firmware/issues/19
Given the 230400 baud is not supported by the webflasher. Can I ask why there is no 460800 version for the pure zigbee ncp-uart-hw? Providing it might stop people falling foul to this issue as I would have gone for the fastest version and skipped the 230400 version entirely.
Can I ask why there is no 460800
Thats not probed either for NCP.
Generally 115200 is sufficient for NCP, as only limited commands and data is passing over the serial most of the processing is done inside the dongle. Multipan and Openthread RCP firmwares need higher baudrates as the entire 250kbps from zigbee (or thread) channel is passing over the serial link to the host. The host is now doing all the processing.
Hello, I've a Skyconnect key on Linux Mint and I can't use the webupdater for same reasons. @iotola is there a tutorial somewhere to follow your steps ? described at https://github.com/darkxst/silabs-firmware-builder/issues/34#issuecomment-1904274210
Hello, I've a Skyconnect key on Linux Mint and I can't use the webupdater for same reasons. @iotola is there a tutorial somewhere to follow your steps ? described at #34 (comment)
If you are getting issues with running the flasher under Linux you need to ensure the user you are running it under is part of the "dialout" security group. I can probably look up the steps under Linux Mint once I am home from work, although I think i did this via the GUI rather than the terminal.
Thank you @iotola it worked. I had to go to the "users & groups" Minux Mimnt setting and check the "Dialout" group on my user and close/open my user session. Thank you
It seems the webflasher goes from 115Kbps to 468Kbps instead of also trying 230Kbps
See the log below: