CC2652P won't pair after firmware update
blacknell opened this issue · 6 comments
I've just updated a brand new Sonoff Zigbee 3.0 USB Dongle Plus to CC1352P2_CC2652P_launchpad_router_20221102 and that worked fine. It immediately paired with the coordinator and all is good.
So I moved to my older one (about a year) and although the flashing went fine, it won't pair. It was paired just fine and I needed to update it.
Looking at the flashing output I see this difference
Older dongle
Opening port /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_865e08dede12ec119b8321c7bd930c07-if00-port0, baud 500000
Reading data from ../CC1352P2_CC2652P_launchpad_router_20221102.hex
Firmware file: Intel Hex
Connecting to target...
CC1350 PG2.0 (7x7mm): 352KB Flash, 20KB SRAM, CCFG.BL_CONFIG at 0x00057FD8
Primary IEEE Address: 00:12:4B:00:24:C7:C6:89
Performing mass erase
Erasing all main bank flash sectors
Erase done
Writing 360448 bytes starting at address 0x00000000
Write 104 bytes at 0x00057F988
Write done
Verifying by comparing CRC32 calculations.
Verified (match: 0x9877ee56)
New dongle
Opening port /dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0, baud 500000
Reading data from ../CC1352P2_CC2652P_launchpad_router_20221102.hex
Firmware file: Intel Hex
Connecting to target...
CC1350 PG2.1 (7x7mm): 352KB Flash, 20KB SRAM, CCFG.BL_CONFIG at 0x00057FD8
Primary IEEE Address: 00:12:4B:00:29:E8:4B:54
Performing mass erase
Erasing all main bank flash sectors
Erase done
Writing 360448 bytes starting at address 0x00000000
Write 104 bytes at 0x00057F988
Write done
Verifying by comparing CRC32 calculations.
Verified (match: 0x9877ee56)
The only difference seems to be that rev number (?) CC1350 PG2.0
is older.
Any ideas?
I've also since tried deleting the router from the network (forced but allow rejoin) but there is still no attempt to pair
It turns out you have to open the case and click RESET after powering up so it starts to re-pair.
I have two spare sonoff CC2652P Sonoff ZIgbee Plus sticks that I would like to use as routers. I am in the same situation but even with multiple times trying to pair after pressing the reset OR boot button nothing comes up in zigbee2mqtt (in devices or logs).
I have tried flashing CC1352P2_CC2652P_launchpad_router_20220125.zip with https://github.com/JelmerT/cc2538-bsl, https://github.com/git-developer/ti-cc-tool and ZigStar. All indicate that the process has completed successfully, but I can't get my two spare sticks to do anything in zigbee2mqtt.
Is there someway I can see what is actually happening? Perhaps the sticks are both kaput. One was previously working as a router, but I had never updated it so I wanted to do that. The other I couldn't get to pair after updating in April 2022, I guess with the previous router firmware version.
I found I had to repair the router after flashing. You need to unscrew the screws at one end. Take out the Board attach aerial. Power up. Then press the tiny reset button for a few seconds and you will see it join. Then power off and reassemble.
And 20221102 version
Ok I have one key working again now, indeed 20221102 fixed the issue. One still won't join but I had trouble with that one before when I tried all this stuff so I assume it is a dud stick.
Thanks for prompting me to check the firmware version! I was sure I had the latest but as 20220125 is sort of similar to 20221102 I had number blindness! Doh!