Description
Discussed in #6356
Originally posted by barbudor February 27, 2022
Hi
I can't report this as an issue because I unfortunately can't provide more qualified information but I'm facing a problem with Tasmota on ESP32-PICO-V3.
I'm using Tasmota with a driver for the french national electricity meter called Linky. The driver is meant to receive frames on a UART, decode them and feed the energy information to Tasmota's internals for publication.
The driver has been unchanged for months and until recently my Tasmota build with this driver was working fine on either ESP32-D0WDQ6 (mini-D1-ESP32) and on ESP32-PICO-V2.
The last version that was working fine on the PICO was using what @Jason2866 is calling Core/SDK 2_0_2_2/v4.4-3-g6afb23d90a. This frozen Core/SDK was in Tasmota since early February.
2 days ago, Jason's upgraded the Tasmota Core/SDK to 2_0_2_3/v4.4-2.0.2-420-g4ff9ceb19a which he describe as "based on latest IDF44 commit and latest commit of Arduino branch esp32-s3-support".
The problem occurs as soon as I enable the Teleinfo driver which uses either UART1 or UART2 and the ESP crash with a Guru Meditation, Load Prohibited.
It doesn't seem to matter which GPIO are used for the UART. It doesn't even need to actually receive serial data.
The same binary works fine on ESP32-D0WDQ6.
Previous binaries were working well on both boards.
I tested a few other drivers that are using serial and they don't create such problem.
I'm sorry for not being able to provide more details but I thought it was worth to drop a note there.
Thanks for the hard work.