Closed m0m4x closed 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.
Closing as jet-home firmware is not supported. Sorry.
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.
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!
Backlog Template; Module; GPIO 255
:Status 0
: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)