@徐锦哲2013
上传了什么代码？把问题说明白

Hi @felmue @Physalice
This issue seems to be related to any unit with a screen. Anyway, we have fixed it!

Hello @Physalice

this is strange indeed. Unfortunately I have no idea why this only happens when using M5NanoC6, sorry.

Thanks
Felix

Hello @Physalice

hmm, works for me. Make sure you are logged into your account before attempting to save your work into the cloud.

I created a small test - you could try to see if that loads the blocks for you. You can find it in the Project Zone called: M5NanoC6_RGB_LED_Blink_Test_UIFlow2.3.7

Thanks
Felix

Hello @Bat21

hmm, not completely sure what the issue is. I am running your example code in UIFlow2 v2.3.7 and when I press BtnA it cycles through Frwd, Rvrs and Stop just fine.

An attached battery seems to show the correct battery state as well.

Could you please cut down your example to the minimum showing the issue you are describing?

Thanks
Felix

Hello @clarksn

hmm, this sounds a lot like a polarity issue with the battery cables. Unfortunately there is no standard for this particular battery connector about which pin to be plus and minus. I've seen both variants in the wild.

My M5Tough, powered via internal battery connector, takes about 68 mA @ 4 V when running UIFlow2.

Thanks
Felix

Hello @RubberDuck

I can confirm the shark fin like signals on my M5CoreS3. I am no I2C expert, but I think they might be marginal and so maybe just barely working on one M5CoreS3 but not on the other when talking to AXP2101. Maybe a stronger pull-up resistor might help?

BTW: I checked the I2C SCL line on an M5Core2 and it is much more rectangular, e.g. much more like I would expect it.

Thanks
Felix

Hello @RubberDuck

just curious, any particular reason you did not read out register 0x22? It is my understanding that this register determines whether the system powers off or does a reset when writing 0x01 to register 0x10.

Also curious, when the issue happens, is the battery full or close to be fully discharged?

The register values of the bad AXP2101 seem to be random. Have you tried to lower the I2C bus speed?

In my experience seemingly random issues often stem from bad / not sufficient power supply. Is the battery in good shape?

Thanks
Felix

Hello @scroggyg

I modified my test program to use internal I2C, did a i2c scan w/o ExtIO2 connected and with it - there seems to be no i2c address conflict.

For me ExtIO2 works either connected to port A or to internal. What I noticed though is that I need to wait (after powering up M5Tab5) for the UIFlow2 screen fully being loaded before running the program.

If I do not wait long enough I occasionally see a crash too.

Thanks
Felix

Hello @scroggyg

here are the result of my tests with various firmware versions:
v2.3.5 : running program -> crash
v2.3.6 : running program -> crash
v2.3.6 hotfix : running program -> ok
v2.3.6 hotfix2 : running program -> ok

Note:

• I had no issue burning an running any of the above firmware versions.
• I run all my tests with no battery attached.

You can find the program I used in the UIFlow Project Zone: M5Tab5_ExtIO2_Test_UIFlow2.3.6

Thanks
Felix