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

    M5Core2 cannot upload failed to write to target RAM

    SOFTWARE
    3
    3
    3.2k
    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.
    • konacurrentsK
      konacurrents
      last edited by

      I just received the beautiful M5 Core2 unit and was trying to get the factory test to upload. Unfortunately I get an error I see in other posts.

      Chip is ESP32-D0WDQ6-V3 (revision 3)
      Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
      WARNING: Detected crystal freq 41.01MHz is quite different to normalized freq 40MHz. Unsupported crystal in use?
      Crystal is 40MHz
      MAC: 78:21:84:93:38:58
      Uploading stub...

      A fatal error occurred: Failed to write to target RAM (result was 01070000: Operation timed out)
      A fatal error occurred: Failed to write to target RAM (result was 01070000: Operation timed out)

      I can upload to all the other M5 devices and ESP-32. This occurs on my Mac with the M1 chip, but also with an older Mac.

      I've tried the USB-C to USB-C as well as USB-A to USB-C. No difference.

      ajb2k3A 1 Reply Last reply Reply Quote 0
      • ajb2k3A
        ajb2k3 @konacurrents
        last edited by

        @konacurrents What OS version are you using as OSX is a pain at the moment.

        UIFlow, so easy an adult can learn it!
        If I don't know it, be patient!
        I've ether not learned it or am too drunk to remember it!
        Author of the WIP UIFlow Handbook!
        M5Black, Go, Stick, Core2, and so much more it cant be fit in here!

        1 Reply Last reply Reply Quote 0
        • V
          Victor1102
          last edited by

          I also encountered the same problem when using M5 core 2. My macOS system version is 10.14.6

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