🤖Have you ever tried Chat.M5Stack.com before asking??😎
    M5Stack Community
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Official "OpenAI Vision For AtomS3R-CAM" Firmware Crashes After OpenAI Response (Guru Meditation Error)

    Atom
    1
    1
    24
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      paul9001
      last edited by

      Hi all,

      I’m having repeated Guru Meditation Errors and reboots with my ATOMS3R-CAM AI Chatbot Kit (8MB PSRAM) using the official firmware.

      My setup:

      • Device: ATOMS3R-CAM AI Chatbot Kit (AtomS3R-CAM+Atomic Echo Base)
      • Serial monitor: 115200 baud, macOS, arduino-cli
      • Firmware: OpenAI Vision For AtomS3R-CAM v1.0 from M5burner

      Behavior:

      • Boot sequence completes, WiFi connects, camera detected, OpenAI API key and WiFi SSID/Password read from NVS.
      • Camera takes a snapshot, sends it to OpenAI, receives a valid chat_response describing the image.
      • Immediately after printing the chat_response, the ESP32 crashes (Guru Meditation Error: Core 0 panic'ed (InstrFetchProhibited)) and reboots.
      • This process repeats endlessly.

      Example OpenAI response lines before crash:

      chat_response: The image appears to show a room with a laptop on a table.
      Guru Meditation Error: Core  0 panic'ed (InstrFetchProhibited). Exception was unhandled.
      

      Core 0 register dump and Backtrace

      Core  0 register dump:
      PC      : 0x00000000  PS      : 0x00060630  A0      : 0x8200e0fe  A1      : 0x3fcb09f0  
      A2      : 0x3fca6a84  A3      : 0x00000000  A4      : 0x3fcd30d8  A5      : 0x3c1f3d14  
      A6      : 0x3fcd0a38  A7      : 0x3fcd2448  A8      : 0x8200e0a8  A9      : 0x3fcb09b0  
      A10     : 0x3fcd0b0c  A11     : 0x3fcd2448  A12     : 0x4200bd28  A13     : 0x00000087  
      A14     : 0x000000f0  A15     : 0x3fcb0a00  SAR     : 0x00000004  EXCCAUSE: 0x00000014  
      EXCVADDR: 0x00000000  LBEG    : 0x40056f08  LEND    : 0x40056f12  LCOUNT  : 0x00000000  
      
      
      Backtrace: 0xfffffffd:0x3fcb09f0 0x4200e0fb:0x3fcb0bc0 0x420d2673:0x3fcb0be0
      
      

      Is this a known bug?
      Thanks in advance!

      1 Reply Last reply Reply Quote 0
      • First post
        Last post