@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 )
{
    Wire1.beginTransmission(0x34);
    Wire1.write(Addr);
    Wire1.write(Data);
    Wire1.endTransmission();
}

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.

@mdevel1 After your message, I opened my M5Stick-C too, but in my case, the magnets is in a properly slots. I didn't found any problems after a quick look in the board and components.

If anyone have any idea about how to procedure, I'll appreciate!
Thank you in advance and thank you for share with us.

With the intuit to share a little more information, @clive-dent shared a possible solution:

http://community.m5stack.com/topic/1464/m5stickc-screen-don-t-work/18

@m5stack I really believe it will be important to do something like as in MacOS Catalina FTDI Driver, to explain how to solve. A youtube video could be a quickly nice way to propagate that procedure.

Why I'm asking that? For most of us, have no problem of have problems like that (and others of we not facing yet). It is more important for us, find quickly the solution. I know the FAQ have something like that, but It will not show details and the M5Stick-C have a LIPO battery (can explode).

Please, consider this suggestion. Because you have made incredible products and I really like to use them.

@clive-dent How much time have you waited with a jumper between GND and BAT? I'm asking that, because I'm a little afraid about to jumper GND and BAT, specially because it is a LIPO Battery (can explode).

But if it is a solution, I'll do that! If you can tell me the how much time, I really appreciate. Please, let me ask you something, If you could create a Youtube video showing that solution, I belive it will be amazing. Many M5Stick-C buyers will go to face this same problem and now have no reference to follow.

Thank you again by your disposition to share how to solve the problem :)

@m5stack Thank you! The solution 2 (as describe in link) is fully functional.

The solution 2 working perfectly! Not need more a short-circuit between GND+GPIO0.

Not only that, after upload a new sketch the M5Stick-C reset (to start the new sketch) automatically (as their normal operation).

Thank you.

OBS: I'm using MacOS Catalina (10.15.2), via USB-C -> Adapter USB-C to USB 3.0 -> M5-Stick-C USB to USB-C Cable. It is running perfectly.

@m5stack if you can, please give us the link for a new driver to solve that problem....

@lanman1 I suggest you to use PlatformIO IDE -- it is more sophisticated to develop and quickly when you rebuild (because have a nice cache system).

Hi,

I'm facing problems with one of my M5Stick-C. It is not finding the AXP192 I2C controller.

Because of that, the screen is not showing anything.

Can anyone help me, please? I do nothing in this M5Stick-C (except to upload the firmware, using GND+GPIO0 short-circuit).

M5StickC initializing...OK
M5StickC I2C Tester
Millis: 4047 - Scanning Address
Port: 1 - Found: 0x51
Port: 1 - Found: 0x68
Finished, total: 2 devices!


Millis: 10307 - Scanning Address
Port: 1 - Found: 0x51
Port: 1 - Found: 0x68
Finished, total: 2 devices!

The address 0x34 is not found (AXP192). What can I do?

@m5stack, please help me.

Hello for all,

I'm very exciting to present for you friends a framework for watch based on M5Stack, making more easily and feasible to create your own watch interfaces.

During the next days I'll create some videos and tutorials about how to implement new skins and faces. This is developed based on PlatformIO IDE.

To test and because I really loved, I used as 3 first watch faces based on Nixie Tube (from a friend in this group). Now I'm trying to ask for help to develop new interfaces (images and etc.). If you could help, please don't hesitate to contact me!

Any help is wellcome. M5Stick-C is an amazing product and we can do more join forces based on a framework.

https://github.com/nsfilho/OpenWatch