here the error:

MPY version : v1.25.0-dirty on 2025-12-05
IDF version : v5.4.2-dirty
Machine : M5STACK Tab5 with ESP32P4

Guru Meditation Error: Core 1 panic'ed (Load access fault). Exception was unhandled.

Core 1 register dump:
MEPC : 0x480d1f46 RA : 0x480d1efe SP : 0x4ff3a3e0 GP : 0x4ff1ae00
TP : 0x4ff3a8d0 T0 : 0x4fc1a058 T1 : 0x4ff158d6 T2 : 0x4887d850
S0/FP : 0x4ff3a410 S1 : 0x4887f34c A0 : 0x00000058 A1 : 0x4833c97c
A2 : 0x00000004 A3 : 0x4887d830 A4 : 0x4887f290 A5 : 0x00000009
A6 : 0x00000002 A7 : 0x0000003f S2 : 0x485ce770 S3 : 0x00000000
S4 : 0x4887f348 S5 : 0x4865be0c S6 : 0x00000068 S7 : 0x4ff21000
S8 : 0x4865bfcb S9 : 0x4887f314 S10 : 0x4865bfba S11 : 0x4865bfca
T3 : 0x48862a44 T4 : 0x00000002 T5 : 0x00001f44 T6 : 0x00009caa
MSTATUS : 0x00011880 MTVEC : 0x4ff00003 MCAUSE : 0x00000005 MTVAL : 0x00000009
MHARTID : 0x00000001

Stack memory:
4ff3a3e0: 0x485ce770 0x4887f34c 0x4887f290 0x4887f350 0x485ce770 0x4887f350 0x00000004 0x00000004
4ff3a400: 0x00000068 0x4865be0c 0x4ff3a440 0x480d0602 0x00008502 0x4887f314 0x4887f290 0x4887f350
4ff3a420: 0x4887f290 0x00000004 0x00000009 0x4887f350 0x4ff3a474 0x4887f34c 0x4ff3a470 0x4802d540
4ff3a440: 0x000010a0 0x480d05aa 0x4887f318 0x00000002 0x00000002 0x00000002 0x4887f290 0x4887f350
4ff3a460: 0x4886bfd0 0x000010a0 0x4ff3a4a0 0x48012612 0x4887f318 0x00000000 0x00000002 0x482dddbc
4ff3a480: 0x000010a0 0x4887d850 0x4887f314 0x482dddbc 0x485ce770 0x4887f34c 0x4887f300 0x4ff05f5e
4ff3a4a0: 0x4fc1a048 0x481c40d6 0x0000047c 0x00000000 0x4ff3a8d0 0x4887f340 0x00000020 0x4887e380
4ff3a4c0: 0x4ff3a620 0x00000006 0x4ff058fc 0x4887f300 0x4887f34c 0x00000003 0x00000006 0x4887f348
4ff3a4e0: 0x0000000e 0x00000068 0x4ff21000 0x0000004c 0x48866834 0x48885e79 0x48885eb9 0x4ff3a4a0
4ff3a500: 0x481c3eda 0x481c3e8a 0x4ff3a580 0x48885eb9 0x48885e79 0x48866834 0x0000004c 0x00000038
4ff3a520: 0x4887f300 0x0000000e 0x4887e540 0x00000006 0x00000003 0x4886be70 0x4ff3a570 0x481878dc
4ff3a540: 0x000007d1 0x00000003 0x48885eba 0x4ff21000 0x00000068 0x4887e540 0x4887d874 0x00000038
4ff3a560: 0x00000006 0x00000002 0x4886bf50 0x481c9aea 0x00000068 0x00000004 0x00000000 0x481c3e8a
4ff3a580: 0x00000001 0x4ff3a5c4 0x4886683c 0x00000006 0x00000001 0x4887d870 0x4886683c 0x00000006
4ff3a5a0: 0x00000001 0x4887d850 0x0000003c 0x4818f064 0x4ff21758 0x48886000 0x48866890 0x482ddf30
4ff3a5c0: 0x48885e79 0x4886bf50 0x4887d850 0x4887d850 0x00000011 0x00000000 0x4ff3a5c4 0x00000000
4ff3a5e0: 0x00000068 0x48886000 0x48866890 0x00000000 0x485ce770 0x48866894 0x48866820 0x4ff05f5e
4ff3a600: 0x48863620 0x7f000000 0x00000949 0x00000000 0x00000002 0x48866888 0x00000020 0x48863620
4ff3a620: 0x4ff3a6f0 0x48886000 0x4ff058fc 0x48866820 0x48866894 0x00000000 0x00000000 0x48866890
4ff3a640: 0x00000018 0x00000068 0x4ff21000 0x00000074 0x48863fc8 0x488846cc 0x488846d5 0x4ff3a600
4ff3a660: 0x48884c90 0x48863620 0x00000010 0x488846d5 0x488846cc 0x48863fc8 0x00000074 0x00000060
4ff3a680: 0x48866820 0x00000018 0x48863fcc 0x00000000 0x00000000 0x4ff21758 0x4ff3a6d0 0x481878dc
4ff3a6a0: 0x00000068 0x48886000 0x488846d6 0x4ff21000 0x00000068 0x48886000 0x48863fe4 0x00000000
4ff3a6c0: 0x485ce770 0x48863fe8 0x48863fb0 0x4ff06016 0x00000000 0x4867b3c4 0x48864290 0x00000000
4ff3a6e0: 0x00000000 0x48863fe8 0x0000001f 0x481bcaaa 0x4ff3a7c0 0xffffffff 0x4ff058fc 0x48863fb0
4ff3a700: 0x48863fe8 0x00000000 0x00000000 0x48863fe4 0x00000009 0x00000068 0x4ff21000 0x0000005c
4ff3a720: 0x0000000d 0x48391000 0x48362000 0x4ff3a6d0 0x488844b0 0x48863620 0x00000010 0x48362000
4ff3a740: 0x48391000 0x0000000d 0x0000005c 0x00000048 0x48863fb0 0x00000009 0x00000000 0x00000000
4ff3a760: 0x00000000 0x4ff21758 0x4ff3a7a0 0x481878dc 0x488844b0 0x0000000d 0x48391000 0x48391000
4ff3a780: 0x48391000 0x48362000 0x00000005 0x00000002 0x00000001 0x48863700 0x00000016 0x481d26e2
4ff3a7a0: 0x00000000 0x4ff219d0 0x4ff21984 0x4ff11e92 0x00000000 0x00000001 0x48880394 0x00000000
4ff3a7c0: 0x00000000 0x00000000 0x481d268c 0x00000016 0x4ff3a820 0x00000001 0x00000002 0x00000005

ELF file SHA256: 5f70ef1bd

Rebooting...
ESP-ROM:esp32p4-eco2-20240710
Build:Jul 10 2024
rst:0xc (SW_CPU_RESET),boot:0x20c (SPI_FAST_FLASH_BOOT)
Core0 Saved PC:0x4ff0ad14
Core1 Saved PC:0x4ff01060
SPI mode:DIO, clock div:1
load:0x4ff33ce0,len:0xd04
load:0x4ff2abd0,len:0xab4
load:0x4ff2cbd0,len:0x2f94
entry 0x4ff2abd0
sdio_mempool_create free:26797616 min-free:26797616 lfb-def:26214400 lfb-8bit:26214400

I tried a different machine on a different network: same error.

MicroPython v1.24.0-dirty on 2025-04-12; M5STACK PaperS3 with ESP32S3

See also my post about this building experience.

While using the Thonny IDE, in the Shell. I issued the commands:

import hardware
display(hardware)

Nothing happened. I waited some minutes. Then I broke out with a KeyboardInterrrupt (<ctrl>C).

When I issue the command:

dir(hardware.RTC)

this results in:

['__class__', '__name__', '__bases__', '__dict__', 'datetime', 'init', 'local_datetime', 'memory', 'timezone']

when I enter the command "dir(board.sdcard)" this also results in ouput:

>>> dir(hardware.sdcard)
['__class__', '__name__', 'SDCard', '__dict__', '__file__', 'machine', 'os', 'create_sdcard_closure']

See the: screenshot.

Regards,
PaulskPt

Hi everyone,

I'm using an M5Stack camera with the OV3660 sensor, and I'm experiencing an issue where the camera freezes after 5-10 seconds. The serial monitor repeatedly shows:

CAM HAL: EV-EOF-OVF

After resetting, the camera works for a few seconds but then freezes again with the same error.

My Setup:

Camera Module: M5Stack OV3660

Power Supply: Stable 5V, 2.1A

Firmware: camera web server

Frame Size: UXGA (1600x1200), SVGA (800x600), QVGA (320x240)

PSRAM: Enabled

fb_count: 1 / 2

Troubleshooting I've Tried:

✔ Reduced frame size (tried QVGA, SVGA)
✔ Set fb_location = CAMERA_FB_IN_PSRAM
✔ Adjusted jpeg_quality (tried 10, 12, 15)
✔ Increased fb_count to 2

Despite these changes, the CAM HAL: EV-EOF-OVF error still occurs, leading to camera freezes.

Could this be a buffer overflow, PSRAM issue, or something else? Any help would be greatly appreciated!

Thanks in advance.

My code is

display_module_image0 = M5Img(0, 0, "res/image.png", True, type=hdmi)

I am getting the following error
Traceback (most recent call last):
File "<stdin>", line 230, in <module>
TypeError: unexpected keyword argument 'type'

M5Triangle and M5TextBox work fine and show up on external screen so the libraries seem to be loaded ok.

Uiflow V1.14.0 for Core2 does not have display module at all in the list of modules so I have had to use the execute code -block to insert this code.

rst:0x3 (SW_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:5216
ho 0 tail 12 room 4
load:0x40078000,len:14052
load:0x40080400,len:3792
entry 0x4008063c
E (1165) esp_image: Image length 3619088 doesn't fit in partition length 3604480
E (1165) boot: Factory app partition is not bootable
E (1167) boot: No bootable app partitions in the partition table
ets Jun 8 2016 00:22:57

The functionality check was using the Servo Kit 360.

It is my assumption that there may be an issue with the "set servo pulse to" block.
fb9b2343-77e5-4150-936d-da117c232dc9-image.png
Specifically, the register addresses for inputting the pulse width (SERVO1_PULSE_ADDR: 0x10, SERVO2_PULSE_ADDR: 0x12) might not be correctly specified.

I hope someone from the development team will review this and make the necessary corrections.

In UIFlow version 1, you can create a program by adding BugC2 to the Hat block.

In this case, "Create new" works without any problems and you can save the project file, but if you try to reload the saved project file in UIFlow1, it fails to load (no error message is displayed and the program display area in the browser remains in its initial state. In addition, the HAT in the block panel becomes "HAT(1)", but the group "BugC2" is not displayed).

I'm using a 16GB SD card formatted with FAT32. The code of the program is the demo code for opening and reading a file, which I've verified exists on the card:

Steps I've tried to troubleshoot include:

• Switching UIFlow firmwares
• Switching microSD cards
• Trying the Arduino library with the Fire board (version 2.1.1) to see if I can open the SD card from this instead; the error I get is "SD Card initialization failed!" so SD.begin() is failing, which seems like the same category of error I saw in UIFlow (ENODEV).

#include <M5Stack.h>
#include <SD.h>
#include <SPI.h>

void setup() {
  // Initialize the M5Stack object
  M5.begin();
  
  // Set up the screen
  M5.Lcd.begin();
  M5.Lcd.setTextSize(2);
  M5.Lcd.setCursor(0, 0);
  M5.Lcd.fillScreen(BLACK);
  M5.Lcd.setTextColor(WHITE);
  
  // Initialize SD card
  if (!SD.begin()) {
    M5.Lcd.println("SD Card initialization failed!");
    return;
  }
  
  M5.Lcd.println("SD Card initialized.");
  
  // Open file
  File file = SD.open("/config.json");
  if (!file) {
    M5.Lcd.println("Failed to open config.json!");
    return;
  }
  
  M5.Lcd.println("config.json contents:");
  
  // Read file and print to screen
  while (file.available()) {
    char c = file.read();
    M5.Lcd.print(c);
  }
  
  // Close file
  file.close();
}

void loop() {
  // Nothing to do here
}

I've tried downloading a 3rd party firmware (the MP3 player in M5Burner, published in 2020) to see if others programs fail to open the SD card and this one failed; telling me to insert the SD card and reboot over and over.

I downloaded a 3rd party firmware published recently (M5Launcher Core 16Mb (Fire, Basic, Gray)) and this one did successfully open the SD card and could see the files on there, which makes me think it's related to firmware or software in some way.

One year ago I bought some other Core FIRE devices and these ones worked with the SD card. The new ones purchased in the last few weeks do not appear to behave the same way; when updating them to the latest UIFlow firmware I've experienced black screens on multiple devices with boot loops. Here's one example from the serial monitor:

Rebooting...
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_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:5228
load:0x40078000,len:13424
load:0x40080400,len:3568
entry 0x4008063c
Guru Meditation Error: Core  0 panic'ed (InstrFetchProhibited). Exception was unhandled.
Core 0 register dump:
PC      : 0x8018b0cc  PS      : 0x00060530  A0      : 0x80098e02  A1      : 0x3ffbbcf0  
A2      : 0x3ffc6c0c  A3      : 0x00000008  A4      : 0x00000001  A5      : 0x00000000  
A6      : 0x00000001  A7      : 0x00060e23  A8      : 0x8018b0cc  A9      : 0x3ffbbcd0  
A10     : 0x00000000  A11     : 0x40093634  A12     : 0x401fedbc  A13     : 0x3f55c2b3  
A14     : 0x00000003  A15     : 0x00060023  SAR     : 0x00000000  EXCCAUSE: 0x00000014  
EXCVADDR: 0x8018b0cc  LBEG    : 0x00000000  LEND    : 0x00000000  LCOUNT  : 0x00000000  

ELF file SHA256: 0000000000000000

Backtrace: 0x4018b0c9:0x3ffbbcf0 0x40098dff:0x3ffbbd10 0x40097949:0x3ffbbd30

I never experienced anything like this on the devices I bought last year; is it possible that the hardware internals have changed in a way that is causing bugs on these new devices that wasn't happening on the older ones?

Any help is greatly appreciated!

I think reading the UUID twice in a short time could be the issue. Try changing below line:

Thanks
Felix