@ajb2k3 I searched for ""Cold Boot Method" and only found 4 references, the oldest 8 months ago, none were helpful.

I took a guess and cold started my computer, removed the old driver, deleting the driver and then installing the driver installed by UIFlow, CP210xVCPInstaller_x64_v6.7.0.0. That did not fix the problem.

I searched the forum a bit and I think I found your method here; https://community.m5stack.com/topic/2303/solved-arduino-ide-on-windows-won-t-flash

I will try it tomorrow when I am more awake.

Thank you for the link to your WIP book,, I am glad to see you have a section on ESP NOW. Do you cover Deep Sleep and power saving modes (and ULP) ?

Regards.

@mati said in Product failed. Burning, Downloading, finding where to get API get.:

a

Putty doesnt do any good. I did find, by accident, that if i went into monitor, and pressed Reset instead of Send, it would print out this ;

=================
COM8
=================
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:8896
load:0x40080400,len:5816
entry 0x400806ac
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:8896
load:0x40080400,len:5816
entry 0x400806ac
M5Core2 initializing...axp: vbus limit off
axp: gpio1 init
axp: gpio2 init
axp: rtc battery charging enabled
axp: esp32 power voltage was set to 3.35v
axp: lcd backlight voltage was set to 2.80v
axp: lcd logic and sdcard voltage preset to 3.3v
axp: vibrator voltage preset to 2v
[E][sd_diskio.cpp:739] sdcard_mount(): f_mount failed 0x(3)
OK
[E][sd_diskio.cpp:739] sdcard_mount(): f_mount failed 0x(3)
Addr:0x34 - Name:Axp192
I2C Axp192 Found
Addr:0x38 - Name:CST Touch
I2C CST Touch Found
Addr:0x68 - Name:IMU6886
I2C IMU6886 Found
Addr:0x51 - Name:BM8563
I2C BM8563 Found

I'm not sure what to Send, in monitor or Putty. This doesn't show up in Putty, as text or as garbage. There is no SD card inserted and it is at the red "SDCard Find failed" prompt on the Core2.

This is after I shutdown the PC, removed and deleted the driver and installed CP210xVCPInstaller_x64_v6.7.0.0, the same driver installed bu UIflow. M5Burner will still not work. I have not followed the Cold Start Method yet. That will be tomorrow.

Regards.

I had bought the M5Stack Core2 on a whim from Amazon and found out too late it would not work to send it back.

At first, when running UIFlow, I was prompted for an API key. For some reason that stopped. I was never able to find where to get one, but one of the introductory videos hinted at running M5Burner which I did.

I can never get this program to succeed in Erasing or Burning firmware from the Core2. I have the CP210x driver installed from working with Arduino Minis or Micros (or something), but I installed the provided driver just to make sure I was using a current version. In Device Manager the message I see is "Silicon Labs CP210x USB to UART Bridge (COM8)".

When doing an erase i see

=================
Erase now
=================
esptool.py v2.5.0
Serial port COM8
Connecting........_____....._____....._____....._____....._____....._____....._____

A fatal error occurred: Failed to connect to Espressif device: Timed out waiting for packet header
=================
 Erase Failed 
=================

When I do a burn of firmware

=================
Start Burn
=================
--chip esp32 --port COM8 --baud 1500000 --before default_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x7ff000 C:\Users\Owner\Downloads\M5Stack\M5Burner\packages\fw\other\wifi.bin 0x1000 C:\Users\Owner\Downloads\M5Stack\M5Burner\packages\fw\core\UIFlow_Core2-v1.8.4-core2.bin
=================
esptool.py v2.5.0
Serial port COM8
Connecting...
.
.
.
[ I have removed some of the dots and dashes for brevity ]
_
_


A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header
=================
 Burn Failed 
=================

In both cases the Core2 or M5PAPER reboots once the error is complete.

I am a VA with memory damage and had forgotten that I had purchased a M5Core2 and not been able to get it to work after the Amazon return period had passed, I just recently purchased the M5PAPER, a M5 CORE INK and an M5 STICK C PLUS.

I tried downloading to the M5 STICK C PLUS and it worked fine, giving me the API key, then i downloaded one of the demos and it worked fine.

The M5 CORE INK failed in the same manner as the other two.

So, any ideas ? Which straw do I grasp at first ?

Regards, mark.