@derbydeserter said in Adding an app to my App List on v1.5.2 M5Stack Fire:
...can download and run it on the M5Stack Fire
Are you sure you used the Download button within uiFlow and not the Play/Run button?
There is a 1-second timeout after boot up that allows the user to press the App, " : ", and Setup buttons. When you use the Download feature within uiFlow, it will download your app to your device, and then it should show up in the App list. Be sure to rename your Project name from "main" in the upper left of uiFlow so you can distinguish it from other apps. If not, it will overwrite main.py each time.
For deleting apps within the Apps menu, in v1.4.5.x you would hold the ▼/DEL button to delete them. However, I think there is a bug in v1.5.x and there is not an option to delete. You will need to delete them manually from the /flash/apps directory by using ampy, Thonny, etc.
When I try to run the code I have the following message:
Traceback (most recent call last):
File "<stdin>", line 59, in <module>
File "<stdin>", line 32, in MPU6866_init
File "<stdin>", line 28, in write_i2c
OSError: [Errno 5] EIO
Do you know what it could be?
please, could you help me? What is M5.powerOFF() doing inside? I am using the esp-idf for my projects with M5Stack and I want Power off from software, but I can only deinitialize all of my routines and turn off display. And when I want to powr on again after power button, then the device turn off first.
@ckuehnel said in M5stack basic core battery power on issue (ip5306 strange power management):
Here is a working code example:
Test of IP5306 functions
// initialize the M5Stack object
Wire.begin(); // required to access IP5306
M5.Lcd.printf("IP5306 Function Test\r\n");
M5.Lcd.printf("No communication with IP5306 chip");
uint8_t bat = M5.Power.getBatteryLevel();
if (M5.Power.isCharging()) M5.Lcd.printf("Battery is charging\r\n");
else M5.Lcd.printf("Battery is not charging\r\n");
M5.Lcd.printf("Battery Level %d", bat);
M5.Lcd.progressBar(0, 220, 360, 20, bat);
Hi, doesn't compile for me!!!
this is the arduino IDE output:
Arduino: 1.8.7 (Mac OS X), Board: "M5Stack-Core-ESP32, QIO, 80MHz, Default, 921600, None"
Build options changed, rebuilding all
/Users/AD/Documents/Arduino/libraries/M5Stack/src/utility/Power.cpp: In member function 'void POWER::powerOFF()':
/Users/AD/Documents/Arduino/libraries/M5Stack/src/utility/Power.cpp:361:28: error: 'gpio_deep_sleep_hold_dis' was not declared in this scope
Multiple libraries were found for "SPI.h"
Not used: /Users/AD/Documents/Arduino/libraries/SPI
Multiple libraries were found for "SD.h"
Not used: /Users/AD/Documents/Arduino/libraries/SD
Not used: /private/var/folders/f3/0kf10ljj6sj4q4twsw_vtxrw0000gn/T/AppTranslocation/395E70C5-F1F6-4076-AA11-9C132A2C6ACF/d/Arduino 1.8.7.app/Contents/Java/libraries/SD
exit status 1
Error compiling for board M5Stack-Core-ESP32.
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
Hi @heybin !
What do you want to show us with the picture: flickering due to problems with contacts?
Do you know what the meaning is of:
flashing? ( = 1s on > 1s off > 1s on > and so on: charging?)
What I noticed so far:
a) USB charging cable connected to M5GO CHG Base and M5GO CHG Base attached to M5GO Base: LED is flashing and obviously charging
b) M5GO disconnected from M5GO Base: LED = ON for 30 seconds , than OFF, but FIRE is still on and operational (Power from internal Lipo Battery?)
c) M5GO CHG Base attached to M5GO Base, but no power on USB-Cable: same behaviour as item b) above. (Power from internal Lipo battery AND/OR CHG Base Battery?)
For a) and b) so far, I didn't test, for how long the FIRE stays ON.
If it's not connecting to the device, what errors do you see? Paste your command line output here and maybe I can help further.
One other custom I did for ampy... I created the file ~/.ampy with these contents:
# Example .ampy file
# Please fill in your own port, baud rate, and delay
# Fix for macOS users' "Could not enter raw repl"; try 2.0 and lower from there:
If you create that file, you will not have to pass the port and baud rate options when running the ampy command. This is the standard way to run ampy when you don't have the .ampy file created.
world101$ ampy -p /dev/tty.SLAB_USBtoUART -b 115200 ls
Also, I was mistaken on the the v1.2.3 firmware with the beeps disabled by default. I just flashed one of my cores with the M5Burner and the beeps are there. I must have been running a custom firmware before.
How about this example code?