I've now flashed it with esphome, blinking gone, so i'm fine

Hi @felmue Followed your advice and got it to work. Thanks very much!

Hello @moccow starting with v2.7 there is a battery power switch at the bottom. See here. To run from battery (or to charge it) the switch needs to be in the on position. Thanks Felix

@mtylerjr I get some of mine from twitter, others I get direct

Hi guys Here is an explanation as to why it may take some time to fix: M5CoreS3 uses the SPI bus in a special way to control the LCD: MISO (normally an input) is reconfigured to be an output and is used as DC line (instead of a dedicated GPIO for DC). Unfortunately to access the SD card (which shares the SPI bus with the LCD) MISO needs to be an input. In case you might be interested. I found a way to do this switching back and forth between input and output for Arduino. Thanks Felix

Yes I did press the reset button. I can even measure 5V at the USB Port when the power supply is connected to 5V/GND pins. I can also measure continuity between the USB 5V pin and the other 5V pins... I guess it's a software issue... I'll try upload another program Thanks for the help! edit: PlatformIO doesn't find the device... it's not at /dev/ttyUSB* like the m5Stick edit2: I didn't read this before I ordered... Note: The newly updated C3U shares the same features as C3, but the difference is that M5Stamp C3U without the USB download chip and the program download method is different (The C3U uses the ESP32-C3's built-in USB Serial for program download) So I have to figure out how to make that work... edit3: OK I figured it out, I think. You have to hold the G9 button while the chip powers on (push reset or plug in power) to enter USB CDC mode. Then this platformio.ini worked for me: [env:m5stack-stamps3] platform = espressif32 board = esp32-c3-devkitm-1 framework = arduino upload_port = /dev/ttyACM0 monitor_speed = 460800 build_flags = -D ARDUINO_USB_MODE=1 -D ARDUINO_USB_CDC_ON_BOOT=1 After uploading once, because of the "CDC_ON_BOOT" option, it goes into the CDC mode automatically without holding the button.

@fonix232 said in Core Ink screen fades on reset: basically, dump that 200x200 4b array onto the flash EDIT: Found out the "Set Screen HV 0" must be set to "0" I thought "1" means "on" but My screen doesnt fade when set to "0". Looks much better now : ) == Hi there, I have exact the same "Screen Fading" Problem (out of the Box). Thank you guys for your insight on this topic. I am new and try to set up the "M5 CORE INK". I try to implement suggestions on this thread. In UI flow I place the "Set Screen HV 1" as @ajb2k3 suggested. I would apprechiate it alot If you (or any one who knows) could tell me how to implement "Screen Dump" in UI flow. This method anyways will be usefull. I might work with Json Data further in my project anyways. Thank you all all lot for pointing me in the right direction. cheers EBK #M5CoreInk #ScreenFading #SetScreenHV # ScreenDump #Json

According to the information I got from the Japanese M5Stack forum, it seems that the MAC addresses of some M5Stamp pico's are not registered on the UIflow server. I contacted support and asked them to register the MAC address of my M5Stamp pico on their server. It now works this way. I would like this information to be made public by support. Also, all MAC addresses of shipped products should be registered on the server.

@felmue Hi Felix, Thank you for pointing me the discussion. It does provide valuable information, however, it doesn't discuss about the orientation of the antenna. I am curious that in your applications, how do you usually position the 3D antenna? My WiFi router has three whip antennas all positioned vertically, is putting Atom-lite LED/button up (3D antenna facing down) a good practice? Paul

Hello @luisgcu you are correct the GPIO choice is a bit unfortunate. That said it helps if you want to debug what's going on on the Modbus connection by using a Modbus sniffer. I've found this one and it decodes the RTU data nicely. See below: captured packet 1: length = 8, CRC: 6F8C = 6F8C [OK] DUMP: 04 05 00 00 FF 00 8C 6F As for ESP32 debug output. You can always setup Serial to output debug onto a different GPIO. Thanks Felix

@bouvin said in Cores3 uiflow: I, too, have received a CoreS3. I have flashed many Core2s before, but this does not seem to work? From the M5Burner application, I can select the Alpha13 UIFlow 2.0 firmware, successfully burn it to the CoreS3, but it starts up regardless in the demo application…. Are others seeing the same? The S3 generation is flashed differently to previous generations, you have to manually put the S3 devices into boot mode by holding down the reset button to get a green light to get them to flash. I have a video about it going live on Saturday on Youtube.