@mdevel1 the problem is AXP Address 0x34 is not responding. Because of that, M5.Axp interface can't connect (and can't power-up screen).
M5.Axp use Wire1 as I2C to communicate on ports 21 and 22, as described in https://github.com/m5stack/M5StickC/blob/master/src/AXP192.cpp.
Because of that, any commands as Wire1.beginTransmission, result in error. The M5.Axp, use Write1Byte to send information (and is not validating if was successful, because of that, I haven't any log).
void AXP192::Write1Byte( uint8_t Addr , uint8_t Data )
The I2C Axp Address (0x34) isn't ready in one of my M5Stick-C. If you have any idea, please let me know -- I'm really trying anything to get AXP fully functional again, because I can't see anything (in display) without Axp.
In my code above, you will see a test in endTransmission as mencioned to test the result.
Thank you by all your attention. Please let me know if you have any idea.
I just experimented with how to solve the problem.
(1) I disconnect the base of M5Stack Fire (it is labeled M5GO) and uploaded the same program many times (until the Fire became "hot condition"). It seemed OK.
(2) I docked the Fire to the original base and uploaded the same program many times and again the issue appeared.
At least in this stage, I can conclude (without knowing the reason) that the base of the M5Stack Fire (M5GO) may be the cause of the problem. The other possibility is that by disconnecting the base, no power is supplied to the core so that everything is reset and things go to normal. I do not know.
@ajb2k3 Thanks a lot !
@cepics "A custom ESP-WROOM-32 build without any flash chip added, so the existing GPIO6, GPIO7, GPIO8, GPIO9, GPIO10 and GPIO11 pins can be used to allow us to add a GD25Q127C (or similar) on our external circuit."
@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.
What some people dont know is that the esp32 is not like an arduino.
the esp32 has 3 cores, 2 primary and 1 Ultra Low power.
In true deep sleep, the primary core are deactivated and the basic "Upkeep" code is off loaded to the ULP.
Because the M5Stack is based on the ESP32 and not much is understood about the ULP, very little progress has been made on deep sleep.
In theory, from what I have read the ULP could maintain a low power screen for a Like (to use your example) and then wake up the core to take the sensor measurements before storing them (for the ulp to recall and display) putting the cores back to sleep.
If you are interested in leaning more, look into the ESP32's ULP (Ultra Low Power core)
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.