<![CDATA[Core 2 Touchscreen Issues]]>I just received my Core2, I played with some Arduino Examples, and the touch screen won't respond. I tried to use the M5 Burner to restore the factory firmware, and it will upload but not run (screen stays black).

Here is the code from the upload of the Core2FactoryTest v1.3.1:

--chip esp32 --port COM10 --baud 1500000 --before default_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x000 C:\Users\bridg\Desktop\packages\firmware\9ba4fa2baa3d86fa6c62d7ace46ea584.bin
esptool.py v4.1
Serial port COM10
Connecting...
.

Chip is ESP32-D0WDQ6-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 78:21:84:93:54:0c
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 1500000
Changed.
Configuring flash size...
Auto-detected Flash size: 16MB
Flash will be erased from 0x00000000 to 0x0017cfff...
Compressed 1560496 bytes to 916442...
Writing at 0x00000000... (1 %)
Writing at 0x00011fc0... (3 %)
Writing at 0x0001a7b5... (5 %)
Writing at 0x0001ee9b... (7 %)
Writing at 0x0002389f... (8 %)
Writing at 0x00028553... (10 %)
Writing at 0x0002f742... (12 %)
Writing at 0x0003614b... (14 %)
Writing at 0x0003df98... (16 %)
Writing at 0x00045c8a... (17 %)
Writing at 0x00051d5d... (19 %)
Writing at 0x0005f53d... (21 %)
Writing at 0x000669ba... (23 %)
Writing at 0x0006b252... (25 %)
Writing at 0x0006f66e... (26 %)
Writing at 0x00073bc5... (28 %)
Writing at 0x0007c0ed... (30 %)
Writing at 0x00086d06... (32 %)
Writing at 0x0008cd9b... (33 %)
Writing at 0x00094f97... (35 %)
Writing at 0x000a238f... (37 %)
Writing at 0x000ad126... (39 %)
Writing at 0x000bd87a... (41 %)
Writing at 0x000c39e3... (42 %)
Writing at 0x000c970d... (44 %)
Writing at 0x000ceb9b... (46 %)
Writing at 0x000d43bb... (48 %)
Writing at 0x000d9d96... (50 %)
Writing at 0x000dfad3... (51 %)
Writing at 0x000e53d0... (53 %)
Writing at 0x000eadd0... (55 %)
Writing at 0x000effa2... (57 %)
Writing at 0x000f5396... (58 %)
Writing at 0x000fa4c6... (60 %)
Writing at 0x000ffbba... (62 %)
Writing at 0x001051cc... (64 %)
Writing at 0x0010a89c... (66 %)
Writing at 0x0010fa27... (67 %)
Writing at 0x00114ddf... (69 %)
Writing at 0x0011a1d0... (71 %)
Writing at 0x0011f862... (73 %)
Writing at 0x00124b55... (75 %)
Writing at 0x00129f85... (76 %)
Writing at 0x0012f109... (78 %)
Writing at 0x001347c9... (80 %)
Writing at 0x00139f26... (82 %)
Writing at 0x0013fb53... (83 %)
Writing at 0x00145641... (85 %)
Writing at 0x0014af50... (87 %)
Writing at 0x001528e7... (89 %)
Writing at 0x0015bab5... (91 %)
Writing at 0x00161dd7... (92 %)
Writing at 0x0016709c... (94 %)
Writing at 0x0016cb43... (96 %)
Writing at 0x00172327... (98 %)
Writing at 0x0017784e... (100 %)
Wrote 1560496 bytes (916442 compressed) at 0x00000000 in 14.7 seconds (effective 847.0 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
]]>https://community.m5stack.com/topic/4512/core-2-touchscreen-issuesRSS for NodeTue, 12 May 2026 03:29:43 GMTTue, 09 Aug 2022 04:42:11 GMT60<![CDATA[Reply to Core 2 Touchscreen Issues on Tue, 06 Sep 2022 18:09:04 GMT]]>@awoodbridge
hello
i am also facing same issue. did you get the solution ?

]]>https://community.m5stack.com/post/18570https://community.m5stack.com/post/18570Tue, 06 Sep 2022 18:09:04 GMT<![CDATA[Reply to Core 2 Touchscreen Issues on Wed, 10 Aug 2022 07:11:41 GMT]]>Hello @awoodbridge

hmm is there anything in the debug log output indicating an issue with touch?

Thanks
Felix

]]>https://community.m5stack.com/post/18269https://community.m5stack.com/post/18269Wed, 10 Aug 2022 07:11:41 GMT<![CDATA[Reply to Core 2 Touchscreen Issues on Wed, 10 Aug 2022 01:34:32 GMT]]>I tried that program. The screen shows up, but the screen doesn't respond to touch.

]]>https://community.m5stack.com/post/18262https://community.m5stack.com/post/18262Wed, 10 Aug 2022 01:34:32 GMT<![CDATA[Reply to Core 2 Touchscreen Issues on Tue, 09 Aug 2022 10:20:55 GMT]]>Hello @awoodbridge

I get the same result - blank screen. The issue is that the command to download Core2FactoryTest v1.3.1 in M5Burner is not correct for this particular binary. It loads the code to the incorrect address 0x000 - the correct address is 0x1000.

I suggest you try Core2_Tools v1.0.1 - that binary and download command work for me.

Thanks
Felix

]]>https://community.m5stack.com/post/18255https://community.m5stack.com/post/18255Tue, 09 Aug 2022 10:20:55 GMT