arendst / Tasmota

Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
https://tasmota.github.io/docs
GNU General Public License v3.0
22.2k stars 4.81k forks source link

TI cc2538 cc2592 won't start as coordinator with latest firmware from jet-home.ru #14819

Closed m0m4x closed 2 years ago

m0m4x commented 2 years ago

PROBLEM DESCRIPTION

Hi! I have Tasmota 11.0.0.1 running on board d1_mini_pro connected via UART with ti cc2538+cc2592 flashed with firmware revision 20211222 from jet-home.ru I get Abort after "Started as coordinator" (see below).
All works fine with fimware revision 20201010 from same author jet-home. Same problem if i flash older version of tasmota and/or on different boards (example. nodemcu_v2 ) Hardware cc2538 bought from here Aliexpress , flashed with j-link from segger. Thank you!

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

- [ ] If using rules, provide the output of this command: `Backlog Rule1; Rule2; Rule3`:
```lua
  Rules output here:
00:32:03.772 CMD: Backlog Rule1; Rule2; Rule3
00:32:03.775 SRC: WebConsole from 192.168.1.150
00:32:03.778 CMD: Grp 0, Cmnd 'BACKLOG', Idx 1, Len 19, Data 'Rule1; Rule2; Rule3'
00:32:04.088 SRC: Backlog
00:32:04.090 CMD: Grp 0, Cmnd 'RULE', Idx 1, Len 0, Data ''
00:32:04.096 MQT: stat/tasmota_03/RESULT = {"Rule1":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":0,"Free":511,"Rules":""}}
00:32:04.304 SRC: Backlog
00:32:04.306 CMD: Grp 0, Cmnd 'RULE', Idx 2, Len 0, Data ''
00:32:04.311 MQT: stat/tasmota_03/RESULT = {"Rule2":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":0,"Free":511,"Rules":""}}
00:32:04.554 SRC: Backlog
00:32:04.557 CMD: Grp 0, Cmnd 'RULE', Idx 3, Len 0, Data ''
00:32:04.563 MQT: stat/tasmota_03/RESULT = {"Rule3":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":0,"Free":511,"Rules":""}}
- [x] Set `weblog` to 4 and then, when you experience your issue, provide the output of the Console log:
```lua
  Console output here:

00:00:15.075 ZIG: rebooting CC2530 device
00:00:15.203 ZIG: ZbZNPSent 0xFF x 255
00:00:15.205 ZIG: ZbZNPSent 410000
00:00:15.432 APP: Boot Count 19
00:00:15.441 MQT: tele/tasmota_03/STATE = {"Time":"1970-01-01T00:00:15","Uptime":"0T00:00:10","UptimeSec":10,"Heap":21,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":70,"MqttCount":1,"Wifi":{"AP":1,"SSId":"max.net","BSSId":"DC:15:C8:D3:E5:60","Channel":7,"Mode":"11n","RSSI":44,"Signal":-78,"LinkCount":1,"Downtime":"0T00:00:03"}}
00:00:16.348 CFG: Saved to flash at 3FB, Count 31, Bytes 4096
00:00:17.526 ZIG: {"ZbZNPReceived":"4180000202020702"}
00:00:17.530 MQT: tele/tasmota_03/RESULT = {"ZbState":{"Status":1,"Message":"CCxxxx booted","RestartReason":"Power-up","MajorRel":2,"MinorRel":7}}
00:00:17.675 ZIG: checking device configuration
00:00:17.678 ZIG: ZbZNPSent 2102
00:00:17.859 ZIG: {"ZbZNPReceived":"610202020207021666340102FFFFFFFF"}
00:00:17.863 MQT: tele/tasmota_03/RESULT = {"ZbState":{"Status":50,"MajorRel":2,"MinorRel":7,"MaintRel":2,"Revision":20211222}}
00:00:17.866 ZIG: ZbZNPSent 2108600000
00:00:17.920 ZIG: {"ZbZNPReceived":"6108000155"}
00:00:17.923 ZIG: ZbZNPSent 2108870000
00:00:17.971 ZIG: {"ZbZNPReceived":"6108000100"}
00:00:17.973 ZIG: ZbZNPSent 2108830000
00:00:18.021 ZIG: {"ZbZNPReceived":"61080002EC3A"}
00:00:18.024 ZIG: ZbZNPSent 21082D0000
00:00:18.071 ZIG: {"ZbZNPReceived":"61080008ECFABC05CCCCCCCC"}
00:00:18.073 ZIG: ZbZNPSent 2108840000
00:00:18.121 ZIG: {"ZbZNPReceived":"6108000400080000"}
00:00:18.124 ZIG: ZbZNPSent 2108630000
00:00:18.171 ZIG: {"ZbZNPReceived":"6108000100"}
00:00:18.174 ZIG: ZbZNPSent 2108620000
00:00:18.222 ZIG: {"ZbZNPReceived":"610800105E40F67FECFABC055E40F67FECFABC05"}
00:00:18.226 MQT: tele/tasmota_03/RESULT = {"ZbState":{"Status":3,"Message":"Configured, starting coordinator"}}
00:00:18.230 ZIG: ZbZNPSent 25406400
00:00:18.873 ZIG: {"ZbZNPReceived":"654000"}
00:00:18.922 ZIG: {"ZbZNPReceived":"45C009"}
00:00:18.927 MQT: tele/tasmota_03/RESULT = {"ZbState":{"Status":40,"NewState":9,"Message":"Started as coordinator"}}
00:00:18.931 ZIG: ZbZNPSent 2700
00:00:18.974 ZIG: {"ZbZNPReceived":"4F800D0004"}
00:00:19.024 ZIG: {"ZbZNPReceived":"6700008A421E04004B12000000070900"}
00:00:19.028 MQT: tele/tasmota_03/RESULT = {"ZbState":{"Status":51,"IEEEAddr":"0x00124B00041E428A","ShortAddr":"0x0000","DeviceType":7,"DeviceState":9,"NumAssocDevices":0}}
00:00:19.037 ZIG: ZbZNPSent 250200000000
00:00:19.075 ZIG: {"ZbZNPReceived":"650200"}
00:00:19.125 ZIG: {"ZbZNPReceived":"4582000000000000408F000050A0000100A00000"}
00:00:19.128 ZIG: ZbZNPSent 250500000000
00:00:19.175 ZIG: {"ZbZNPReceived":"4F80080200"}
00:00:19.225 ZIG: {"ZbZNPReceived":"650500"}
00:00:19.276 ZIG: {"ZbZNPReceived":"4585000000000001F2"}
00:00:20.233 ZIG: timeout, goto label 99
00:00:20.238 MQT: tele/tasmota_03/RESULT = {"ZbState":{"Status":99,"Message":"Abort"}}
00:00:20.240 ZIG: Abort
00:00:20.241 ZIG: Stopping (99)

TO REPRODUCE

Steps to reproduce the behavior: Flash latest firmware from jet-home.ru on cc2538 antenna.

EXPECTED BEHAVIOUR

A clear and concise description of what you expected to happen. Coordinator started.

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

Add any other context about the problem here. Zigbee started with previous version of firmware: https://github.com/jethome-ru/zigbee-firmware/blob/master/ti/coordinator/cc2538_cc2592/JH_2538_2592_ZNP_UART_20201010.zip

(Please, remember to close the issue when the problem has been addressed)

s-hadinger commented 2 years ago

I looked at the code, Tasmota sends Active EP Request but the MCU returns an error. There's nothing we can do, the firmware does not act as expected.

ascillato2 commented 2 years ago

Closing as jet-home firmware is not supported. Sorry.

s-hadinger commented 2 years ago

I just revisited this, it seems that it should be a non-blocking error. It only indicates that this firmware automatically declares EP 0xF2 locally, which is not a problem. I will change to allow this value.