@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?
@kat @Rop you need to create and M5ez project, create a text place holder and set the code to replace the text with the values. Hopefully @Rop will pick up the notification and help you out. My knowledge is more towards Uiflow
Currently there is no support for png images in the micropython port that form the firmware of the m5Stack range.
BMP is its raw uncompressed state is a simple file to translate along with base level jpg (not JPEG!)
Until such time that a codec exist for micropython, we are all stuck with converting graphics into base level formats.
@rob-biernat which M5Stack or Stick are you using?
The M5Stacks and Sticks have an I2C grove port (port A) but this is also a digital I/O port in that it can read or write 0 or 1 values (on or off) I am currently triggering a relay unit from the port.
The M5Go base has has 2 additional port which are multi I/O (port b) and UART (port C) Unlike Arduinos, the esp32 which powers the M5Stack has no set pin functions and all pins can be used for a range of functions.
When using Port A Yellow is SCL (pin 22) and white is SDA (pin 21) and need to be defined.
I have started to document the different functions of the grove connector and you can find them on pg 19 and 20 of my WIP book here https://github.com/Ajb2k3/UIFlowHandbook/blob/master/UIHB1404192.pdf
@brij300 So sorry about that. We haven't tried to connect to AIOT website yet? But some guys make a project about opendimes. You can contact them. Thanks a lot.
I didn't had any errors during burning.
The backlight is lit up.
Since I bought a M5Gray also, I recognisize the sound on the Fire as the sound of the Rock-Paper-Siccors game which is the default app.
I just thought, you were using the ui flow firmware previously right. I think there is an issue if you have flashed one of the micropython firmwares and try to use arduino afterwards without completely wiping the memory. Please try to use the erase tool in the M5 burner tool and then try and flash an arduino sketch again
Well, I have a couple of spots in my project that a button press would make things very easy. For example, I'm using M5ez for my interface, and use Blynk to display events on the M5 screen. I have backlight timeout set to 30 seconds. A new event doesn't turn the backlight back on, but a keypress does. So, in my if (newEvent) loop, I could have a M5.BtnA.press(), that would wake up the screen. Can I go into the M5ez library, figure out what happens after a real button press to wake the screen and replicate that? Yes, of course, and I have certainly tried that, but some of the items that need to be set are private, so calling them from a main loop is problematic. Rewriting that stuff so it's all public might work, but that solves one problem. I'd also like menus to time out - if there's no activity after going into a menu, I'd like it to time out and go back to the main menu. Again, code can certainly make that happen, but a M5.BtnA.press() would be a lot easier to implement... Does this make sense?