I have same issue.

I checked the documentation of the GT911 touch panel and found that the i2c address has two modes, 0x5D or 0x14, depending on the High/Low of INT at boot.

After checking the i2c address with the code below, it is highly possible that the i2c address of the touch panel is different and is not being controlled correctly.

• USB power boot: 0x5D
• Battery power boot: 0x14

from machine import Pin, I2C
i2c = I2C(scl=Pin(22), sda=Pin(21), freq=400000)
i2c.scan()

I think it need to fix initial pin config of M5PAPER touch panel driver or m5paper firmware.

@bigben

You can report bug-report channel.
https://community.m5stack.com/category/8/bug-report

I have same issue.

I checked the documentation of the GT911 touch panel and found that the i2c address has two modes, 0x5D or 0x14, depending on the High/Low of INT at boot.

After checking the i2c address with the code below, it is highly possible that the i2c address of the touch panel is different and is not being controlled correctly.

• USB power boot: 0x5D
• Battery power boot: 0x14

from machine import Pin, I2C
i2c = I2C(scl=Pin(22), sda=Pin(21), freq=400000)
i2c.scan()

I think it need to fix initial pin config of M5PAPER touch panel driver or m5paper firmware.