When I insert UIblock Hardwares - Speaker - playWav file "" I getting Python error - "unknown attribute rate=" while executing on Core2. M5Flow 1.0.17, UIFlow - 1.7.6 (on Core2).
Posts made by xxxa0c
RE: M5 Stack Core 2 AWS bricked and my experiences
I met just the same issues at the begining of use my Core2, but later I figured out that it
s just a problem of M5Burner and M5Stack project immaturity. Only UIFlow and Core2 factory test apps are compiled properly for Core2, other programs listed in M5Burner compiled for M5Stack Core and incompatible with Core2 (you can recompile they using sources and proper includes). Anyway after "bricking" the Core2 you can easly burn UIFlow or FactoryTest or another manualy compiled program through M5Burner or PlatformIO or standart ESP-IDF toolset from Espressif. Its not a real brick state, but just firmware incompatibility.
OSError: I2C bus error(19)
Today suddenly stoped working I2C devices on port A.
After coding session (Wave file playing from SD, developed on c++), I flashed (M5Burner updated to 2.3.0) the UIFlow 1.7.5core2 with well debuged UI application with ENV2 and SGP30 sensors connected through GROVE HUB. At first I got "ENV2 unit not found" while it was connected. Reconnection and cable exchange gave nothing. Core2 did not see ENV2 sensor plugged in PortA through GROVE Hub or Directly.
Could somebody give any suggestions?