Navigation

    M5Stack Community

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. ps.oz
    3. Topics
    P
    • Continue chat with ps.oz
    • Start new chat with ps.oz
    • Flag Profile
    • Profile
    • Following
    • Followers
    • Blocks
    • Topics
    • Posts
    • Best
    • Groups

    Topics created by ps.oz

    • P

      CoreS3 not working with UiFlow
      UiFlow 2.0 • • ps.oz

      19
      0
      Votes
      19
      Posts
      3633
      Views

      P

      UIFlow is now working again for me thanks
    • P

      8encoder bug on cores3
      UiFlow 2.0 • cores3 8encoder • • ps.oz

      1
      0
      Votes
      1
      Posts
      572
      Views

      No one has replied

    • P

      i2c bug
      UiFlow 2.0 • • ps.oz

      1
      0
      Votes
      1
      Posts
      494
      Views

      No one has replied

    • P

      Button on CoreS3 not working
      UiFlow 2.0 • • ps.oz

      1
      0
      Votes
      1
      Posts
      465
      Views

      No one has replied

    • P

      textbox on core2
      Bug Report • • ps.oz

      2
      0
      Votes
      2
      Posts
      652
      Views

      @ps-oz what do you mean? You use the label on the core2 like you do on the core.
    • P

      M5 Stack Core 2 AWS bricked and my experiences
      Core 2 • • ps.oz

      3
      0
      Votes
      3
      Posts
      3536
      Views

      X

      I met just the same issues at the begining of use my Core2, but later I figured out that its 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.