Please read this doc. I updated it just now.
It is better to see once than read 100 times bla-bla-bla
I istalled release, but I guess I find another reason.
In the M5BALA stack there are three IP5306 IC on the 5V BUS.
And one of these IC is controlled by ESP32.
During reboot procedure trouble things occured at 5V bus Brownout
As (thanks to M5 team) we do not still have all fucking schematics, nobody could resolve what is going on there.
Now, the situation looks like the following: one time it could start working normally or another time it could not. Unpredictable.
Well, on my office PC I had to reinstal ESP32 package and I found that your suggestions allready icluded in the new
release. Now, regardless of choosen board( M5-Stack-Core/Fire/ESP32-Dev) I got this stange behaviour.
It looks like very huge negative value(about 30 digits)of measured angle, which begins to rize in positive direction,
until it reach correct value. From this point, the program could or could not continue normal run.
I'll try to roll back the package install to see what happened.
@Kabron I don't have the BALA hardware so cannot test. Can you better explain what you mean by:
it gives wrong M5Bala library operation
Does it work it you use the original (smaller) partition scheme on the Fire? I.e.: do we know it is connected to the partitioning at all? Or could it be some other difference between the Core and the Fire?
Not now, maybe tomorrow.
I also have a question. I got M5Fire in M5Bala set.
Half of USB-C does not work, i.e.: in one position PC does discover device, while in 180 degrees opposite - does not.
Is it a kind of warranty case?
I wrote to official M5Store seller on aliexpress, but got no answer.
Not all is so smooth. Try this sketch. When compiled under Fire it gives wrong M5Bala library operation, resulting at least in wrong angle measurements. With M5stack-Core-ESP32 all OK.
I abandoned this platform for commercial prototypes because of lack of documentation. But at least there are now hints for more info in a new repository.
I took a glance. Monstrous Poverty
Almost total documentation absence is of course a most deepest shame for M5 team.
Now, receiving M5BALA, I try to compensate somehow this frustration.
Here are schematic and inner pictures of the subject.
Hope, other members join to initiative
Please update the Espressif 32 platform to latest version (v1.1.1 at this moment)
That should solve the problem.
I have 1.1.2 installed and do not know how to degrade
platform = email@example.com
and now it works
New version compilation results:
M5StackMod initializing...[E][sd_diskio.cpp:739] sdcard_mount(): f_mount failed 0x(3)
E (705) SPIFFS: mount failed, -10025
[E][SPIFFS.cpp:47] begin(): Mounting SPIFFS failed! Error: -1
[E][Preferences.cpp:330] getUShort(): nvs_get_u16 fail: light NOT_FOUND
and nothing more...
I allowed myself a tiny mod to your App. Now it can be launched from the SD card under SD-Menu from tobozo. https://github.com/tobozo/M5Stack-SD-Updater.
Modification consists in main.c mod and extra libraries. Just unzip Matroska.zip to project folder and build. Resulting firmware.bin in .pioenvs\m5stack-core-esp32
is compatible with tobozo loader.
I just want to note a fundamentally different approach to support from HARDKERNEL and M5Stask teams. ODROID-GO has just been announced but already with full support. M5Stask can not realize it for years. Only children's tweets and sluggish community.
与 M5Stack Community 的连接断开，我们正在尝试重连，请耐心等待