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

maybe I broke my Zigbee 3.0 USB Dongle Plus #145

Open
IngiDingi opened this issue Nov 10, 2024 · 3 comments
Open

maybe I broke my Zigbee 3.0 USB Dongle Plus #145

IngiDingi opened this issue Nov 10, 2024 · 3 comments

Comments

@IngiDingi
Copy link

IngiDingi commented Nov 10, 2024

Hi.

Today I tried to use the https://darkxst.github.io/silabs-firmware-builder/ to flash my Zigbee 3.0 USB Dongle Plus to the MulitPAN (RCP).
The deice was recongnized by the browser in COM 6 and I allowed connection.
After choosing the firmware I started the process.
But it was stuck at 0% for 10min so I decided to cancel this process and start from scratch on another PC.

This is now the issue on the other PC:
image
Here is the LOG:
silabs_flasher.log

I tried to recover the original firmware useing SecureCRT but I can not connect to the Zigbee 3.0 USB Dongle Plus at all.
Activating the bootlader in itself is not even possible anymore I guess.
I tried this method:

"Manual mode"
Keep pressing the Boot button, restart the device, and release the Boot button after Dongle
enters the serial port Bootloader

Thisis what I see in Secure CRT when I am connected and try to upload the firmware:

image

@IngiDingi IngiDingi changed the title mayb I broke my Zigbee 3.0 USB Dongle Plus maybe I broke my Zigbee 3.0 USB Dongle Plus Nov 10, 2024
@darkxst
Copy link
Owner

darkxst commented Nov 10, 2024

The only way to brick dongle is to flash incorrect bootloader, in all other cases you should be able to recover using the internal boot button.

@tootla
Copy link

tootla commented Nov 11, 2024

I agreed with darkxst. I thought that ZBDongle didn't enter the bootloader when you manually flashed the firmware, because after entering the bootloader, the menu should have appeared on SecureCRT.

@IngiDingi
Copy link
Author

Hi. Thx for your reply. Today I tried with my old Laptop and with this I was able to flash again. Something which is similar on my PCs is blocking the communication.

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

3 participants