search

Koenkk / Z-Stack-firmware

Compilation instructions and hex files for Z-Stack firmwares
MIT License
2.33k stars 643 forks source link

Sonoff Zigbee 3 Dongle not recognised anymore after flashing #391

Closed s-elsheikh closed 1 year ago

s-elsheikh commented 2 years ago

Hello, I just flashed my CC2652PLF sonoff Zigbee dongle using this hex file: https://github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_coordinator_20220219.zip

I used hardware methoid to enter bootloader. After flashing I got success message from flash programmer 2.

Afterwards I removed the dongle. Upon reeinserting it I noticed the dongle heating up (can barely hold it in my hand) and it is not recognised in device manager anymore in the Windows machine, where I flashed the firmware.

I cant seem to find a mistake I did while flashing. Did anyone else encounter such a problem?

Thanks Samer

lklimek commented 1 year ago

I also have this problem. 

Zigbee2MQTT:error 2022-09-24 10:56:59: TypeError: Cannot read properties of null (reading 'length')

Flashed with 

 docker run --rm --device /dev/ttyUSB0:/dev/ttyUSB0 -e FIRMWARE_URL=https://raw.githubusercontent.com/Koenkk/Z-Stack-firmware/master/coordinator/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_coordinator_20220219.zip ckware/ti-cc-tool -ewv -p /dev/ttyUSB0 --bootloader-sonoff-usb

Also tried with 20220726, didn't help :(

lklimek commented 1 year ago

I managed to fix this.

  1. I started bootloader with uartLog from https://sonoff.tech/wp-content/uploads/2022/08/uartLog.zip - not sure if it's needed.
  2. I used the following command to install firmware: 
    docker run --rm --device /dev/ttyUSB0:/dev/ttyUSB0 -e FIRMWARE_URL=https://raw.githubusercontent.com/Koenkk/Z-Stack-firmware/master/coordinator/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_coordinator_20220219.zip ckware/ti-cc-tool -ewv -p /dev/ttyUSB0 --bootloader-sonoff-usb -b 115200

Note the -b 115200 - this sets baud rate to 115200. I think this is what was needed.

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days