Yes. That looks to be the case that it crashed after one or two Wire1 commands. Usually on period is printed but sometimes 2. Als the internal I2C does not work is I call M5.begin but it does if I just call Wire.begin.

Hi! I found that there was no useful example so I made one and posted on GitHub, here. https://github.com/teastainGit/Simple-PaHub-example My example was written for M5Stack Basic, so you will have to change that to M5Stamp-C3, and the Stamp C3 won’t work with ENV sensor, but maybe this repository will be on some use. Let me know if you need any help with this! (What is your application?) -Terry

Any idea if the "Factory Test" included in M5Burner is the same as the "FactoryTest" in the Arduino library example?

Hello @digs71 esp_sleep_enable_gpio_wakeup can only be used for light sleep but not for deep sleep. See ESP32 sleep modes. If you want to use deep sleep check out this example. Please also check out this article about different sleep modes. The sleep functions are not M5Core2 specific. They are functions of the ESP32 so it should work on all devices using ESP32. It is normal for them to be found in esp32 related libraries, but not in the M5Core2 library. Both my sleep examples have been tested on an M5Core2 (under ESP32 Arduino framework 2.0.4 and 2.0.5), so I am stumped as to why it fails for you. Could you please post the debug log - hopefully this will shed some light on the reason for the reboot. Thanks Felix

Thanks

same error. Brand new user (just received my M5StickC 7 hours ago) My development environment is freshly minted (3 hours ago) on a USB drive plugged into a Raspberry Pi4B. New OS. New install of Arduino IDE 1.8.19. Add platform "M5Stack Arduino" and Library "M5StackCPlus" by following these instructions. the sketch is very basic ''' void setup() { } void loop() { } ''' the error is: usage: esptool write_flash [-h] [--erase-all] [--flash_freq {keep,40m,26m,20m,80m}] [--flash_mode {keep,qio,qout,dio,dout}] [--flash_size FLASH_SIZE] [--spi-connection SPI_CONNECTION] [--no-progress] [--verify] [--encrypt] [--encrypt-files <address> <filename> [<address> <filename> ...]] [--ignore-flash-encryption-efuse-setting] [--compress | --no-compress] <address> <filename> [<address> <filename> ...] esptool write_flash: error: argument <address> <filename>: Address "{upload.erase_cmd}" must be a number esptool write_flash: error: argument <address> <filename>: Address "{upload.erase_cmd}" must be a number Please assist with getting my shiny new device to work.

Yes if you google "m5stack timer camera examples" there are multiple examples .. I have tried several but so far not able to get good resolution .. i think the software is not referencing the PSRAM corrrectly because the picture save process errors at about 450k. I am going to try this tomorrow .. https://github.com/mumris/M5Stack-Timer-Camera-X

@teastain That was my hope too and I was disappointed to find it controlled by an esp32 but not wifi accessible :(

Hello @Gorilla thank you for reporting back. I am glad you figured it out. And yes, there were some recent changes to the EXTIO2 library regarding I2C so getting the latest is key. Thanks Felix

@ajb2k3 I learned that the browser does connect to the Core2 by WiFi and the IDE connects using USB.

Hello @Marelli7 you are welcome. I sounds like you are having fun. And thanks for reporting back. I am glad to hear you got it working to your liking. Thanks Felix

@felmue: Thanks for your help