mercenaruss / zigstar_addons

Home Assistant add-ons for Flashing ZigStar Devices
Apache License 2.0
55 stars 3 forks source link

Fail to flash UZG-01 (CC2652P7) using zigstar-cc2652p7-flasher #29

Closed hilsonp closed 4 months ago

hilsonp commented 4 months ago

Hello,

I try flashing my UZG-01 (CC2652P7) using the zigstar-cc2652p7-flasher (with zigbee2mqtt stopped).

The device shows:

Model: UZG-01 ESP32 Firmware ver: 0.1.5 (2023-09-06 12:01:02.723464) ESP32 version: ESP32-D0WDQ6 ESP32 temperature: 47.56 °C ESP32 frequency: 2 cores @ 240 MHz ESP32 flash size: 4 Mb, external ESP32 Free heap: 189 / 289 KiB CC2652P version: CC2652PP1FRGZR CC2652P flash size: 352 Kb

The addon log show:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service banner: starting

-----------------------------------------------------------
 Add-on: ZigStar TI CC2652P7 FW Flasher
 ZigStar TI CC2652P7 firmware flasher addon for UZG-01
-----------------------------------------------------------
 Add-on version: 0.2.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 12.0  (amd64 / qemux86-64)
 Home Assistant Core: 2024.3.0
 Home Assistant Supervisor: 2024.03.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service cc2652-flasher: starting
[22:24:35] INFO: Triggering Bootloader mode on 192.168.141.160
[22:24:47] INFO: Starting CC2652P7 flasher with socket://192.168.141.160:6638
Setting filename to /root/firmware.hex
Opening port socket://192.168.141.160:6638, baud 500000
Reading data from /root/firmware.hex
Your firmware looks like an Intel Hex file
Connecting to target...
pg_rev = 1, protocols = f, wafer_id = 0xbb77
CC135x PG1.1 (7x7mm): 704KB Flash, 20KB SRAM, CCFG.BL_CONFIG at 0x000AFFD8
Primary IEEE Address: 00:12:4B:00:2A:7B:56:EF
    Performing mass erase
Erasing all main bank flash sectors
    Erase done
Writing 720896 bytes starting at address 0x00000000
 Write 248 bytes at 0x00000000
 Write 248 bytes at 0x000000F8
 Write 248 bytes at 0x000001F0
 Write 248 bytes at 0x000002E8
 Write 248 bytes at 0x000003E0
 Write 248 bytes at 0x000004D8
 Write 248 bytes at 0x000005D0
 Write 248 bytes at 0x000006C8
ERROR: Timeout waiting for ACK/NACK after 'Get Status (0x23)'
[22:24:52] INFO: cc2652p7-flasher-up script exited with code 1
s6-rc: warning: unable to start service cc2652-flasher: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
s6-rc: info: service banner: stopping
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
URL NOT FOUND

I tried several time and it always fail before reaching the end.

The device in on a 1GB Ethernet network.

Any thought ? Anything else to try ? Any log to provide ?

hilsonp commented 4 months ago

I upgraded the ESP32 firmware and then, the Zigbee firmware flash succeeded. I guess this was a problem in the previous ESP32 firmware. Closing the issue.