Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

M5Unified and Arduino 3.0 on Core2 #119

Open
nuno636 opened this issue Jul 25, 2024 · 2 comments
Open

M5Unified and Arduino 3.0 on Core2 #119

nuno636 opened this issue Jul 25, 2024 · 2 comments

Comments

@nuno636
Copy link

nuno636 commented Jul 25, 2024

Hello,
after running a few tests I realized that the M5Unified library is not compatible with Arduino 3.0 and IDF 5.1
I took the display example (https://github.com/m5stack/M5Unified/tree/master/examples/Basic/Displays), run it WITHOUT Arduino as a component and it works perfectly.
I then added Arduino and it stopped working:
Backtrace: 0x400d73f5:0x3ffb92f0 0x400e12e2:0x3ffb9360 0x40089ada:0x3ffb9380
0x400d73f5: lgfx::v1::LGFXBase::width() const at /esp/test/components/M5GFX/src/lgfx/v1/LGFXBase.hpp:311
(inlined by) setup() at /esp/test/main/test.cpp:233
0x400e12e2: loopTask(void*) at /esp/test/components/arduino/cores/esp32/main.cpp:59
0x40089ada: vPortTaskWrapper at /esp/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:162

I tried to disable as many Arduino libraries as possible (SPI, Ethernet, SD, SPIFFS, OTA, WifiProv and so on) but the result is the same. Any operation on the display leads to a crash.

Does anybody have the same problem or any idea to where to start to inspect this problem?

Thank you

@mhaberler
Copy link

mhaberler commented Jul 27, 2024

same as #89

see also #90

currently M5Unified is Arduino2 AFAICT

I'm dropping M5Unified wherever I do not absolutely need it for this reason

@nuno636
Copy link
Author

nuno636 commented Jul 29, 2024

I wouldn't say it's the same as #89 and #90, maybe it's another issue to be put on the same line. At least the other 2 issues throw an error (and the #89 is quite easy to fix on a Core2, not sure about other devices). Mine shows absolutely nothing, I managed to make the firmware run, no errors and no display, so I'm going blindly here.

Truth be told, I was fine with the Core2 library and IDF 3.4.x. I just wanted to test the latest library with the latest IDF but I see it's a bit too early.

I'd gladly fix it, if only I could find where to start from.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants