I have been able to get it working with the correct wiring using the grove port in a Core Basic Gray unit. No I will start to use the io pins in the bottom of the unit so I can use the grove port for other things. thanks for all your assistance.

Thanks for this, I haven't started on mine as still looking through IOT services

@caccum Well, speaking personally: I believe the BootLoader is deep inside and indestructible. I would use Arduino IDE to upload this basic LCD sketch: https://github.com/m5stack/M5Core2/blob/master/examples/Basics/display/display.ino

@ajb2k3 said in How do I enter BOOT mode on M5Core2: Wrong boot mode detected (0x0)! The chip needs to be in download mode: @themusicman This means that something else in OSX is access the USBport via a terminal preventing M5Burner from being able to access the port. Please make sure only M5Burner is running and that no other terminal software is running. I tried on my MacBookPro (original issue was on iMac) with no other serial terminal software running, exactly the same issues unfortunately. I have now returned the M5Core2 device back to thePiHut and am awaiting a replacement. Thanks for your support though @ajb2k3 - it is much appreciated.

@crami25 That you for these links. I am now working n reading mail. After trying to figure out which mail server works the best with POP3 (was not able to get even contact with the op3 server of Google and Outlook despite the many variations in settings I used), I now found a hosting server. Now fiddling out why the AT-POP3READ command does not give some response that makes sense although all the other POP3 commands return a valid response . Regards

@holofloh Thanks, this is exactly what I was looking for. PD

@kkkkkk Hi, you can click the link to know more about it

@kkkkkk Maybe, you can try M5stickC-plus

Try putting the Wire1.begin(...) in your program loop instead of the setup {}. assigning other pins to the I2C channel; Wire1.begin(32, 33, 100000UL); // for I2C TOF connection .. before reading the TOF, Wire1.begin(21, 22, 100000UL); // for I2C gyro connection .. before reading the gyro.

Reset your web browsers temp files and cache as it could be a cookie or something blocking it

Hello@margel The description in m5-docs is done with setTextColor. https://github.com/m5stack/m5-docs/blob/master/docs/en/api/lcd.md setTextColor( color, backgroundcolor )

@hgi867 Yeh, sorry, I tried looking for the ESP-IDF equiv but not well documented

You can use the "Device File Manager" in UiFlow.

@felmue Thank you very much! It´s very frustrating for me at the moment and I´m not confident to come closer to a solution. What I recognized that the compiling error has nothing to do with the Atom Lite because by just testing very simple other platforms the compiling also does not work. So I´m having a huge problem with my ESPHome environment and not able to fix it. So I used another test environment and there it´s possible to compile this code without errors. But I´m not able to flash this .bin file to my Atom Lite. I used the ESPHome flasher and after flashing it running into some kind of boot loop. 1162-mmu-set-00010000-pos-00010000 etc etc. Google searches leads me to an uncorrect flash access setting but the suggestions for the official ESP32 flasher seems not to solve this issue. Tried to flash at a USB2 or USB3 Port but without any success and it´s getting really annoying. Really looking for a very simple step to start with a success and then move forward step by step. I mean I have a ready .bin file in place and it can´t be so complex to bring it succesfull to a EsP32 Pico D4 like the Atom Lite. Have done it before without such huge problems. Really appreciate your hints. Best regards

Esp32 C3 and C3U is not supported in UIFLOW but is supported by mainstream Micropython. You have to flash the firmware without usb for it to work.

Yes, it worked ;-). I locked myself up in the office for the last 48 hours. And rewrote AsyncWebserver but using Ethernet.h instead of LWiP. All features of AsyncWebserver are available, the only thing you need to take care of is the periodic upkeep (a single line of code in the main loop). I also added an updater for the internal ESP clock (separate) to update over NTP via Ethernet.h. All in all it took the most out of the past 48 hours but for me it was very worthwhile. Consumed progmem is less than half of what is was (total program went down from 1.1MB to 604kB). Static ram usage went down from (critical 90%) to a comfortable 35%. Dynamic Ram usage decreased by a 40%. All of this is probably mostly due to the fact that we can rely on the W5500's internal IP stack instead of LWiP. Another gain for me is that the periodic upkeep is very predictible, making my main control loop (which also runs RS485) more stable and very predictible. Loop time is now (very) stable at under a ms. Wheres with LWiP it would vary a lot under network load. As an embedded system engineer (by background) this is one of the things that pleases me the most. I can serve a 60MB file or even upload a large file (limited only by storage) to the system without noticable impact on the main process. Performance wise it seems to be a tad slower for now than LWiP over WiFi with AsyncWebserver. Serving the webui of around 3MB takes about a second longer at roughly 4 seconds to fully load. But there is plenty room for optimization as i now only use a single socket buffer of 2048kB in the w5500 at a time. So there is about 8 times as much performance available. I'll most likely make a Github page for this if there is any interest from the community. For now i'm going to have a good sleep 😉👍

adding notes : the M5stickc plus uses an AXP192 for power management (including display), all the functions to initialise it are inside the M5StickCPlus but you can't call this library in same time as TFT_eSPI.h. you will have to copy AXP192.h & AXP192.cpp from the M5StickCPlus lib and put it in your project (change the names). If you have a M5 project loaded in your stick and then upload a sketch using TFT_eSPI, it will work the first time as the display is already power on from the previous m5 sketch but the display won't turn back on on the next restart unless you init the AXP192 like explained. hope it helps anyone!

Thanks to both of you who replied, I got it working with your help! The problem was the port I was connecting to. Using a USB-A to USB-C cable, connected to the Mac Mini M1's USB-A port got it to work and the device now shows up as /dev/tty.wchusbserialXXXXX Very happy about this, just in time before the weekend. ;) Thanks again!