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

    new m5stack: Failed to write to target RAM (result was 01070000)

    Bug Report
    13
    22
    55.4k
    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.
    • M
      Mackone @darul75
      last edited by

      @darul75

      Same here - Have You found any solution?

      1 Reply Last reply Reply Quote 0
      • E
        erich
        last edited by

        This was a known issue with Big Sur (something related to the python and / or serial port implementation in Big Sur.
        I did contact M5Stack support but no solution has ever been found.
        I gave up and reverted back to Catalina and it worked fine again.
        Now I just installed the latest Monterey but haven't tested the Core2 yet.
        In the meantime I was also using a windows computer....

        M 1 Reply Last reply Reply Quote 0
        • M
          Mackone @erich
          last edited by

          @erich I'm on Mojave 10.14 and problem still exists :/

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

            I’m actually getting it with Catalina

            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
            • S
              slugs
              last edited by

              Has anyone managed to get the core 2 to work with an M1 mac? I think that you do not need the driver for the m1? With a m5stick C it works fine, but not with the core 2

              1 Reply Last reply Reply Quote 0
              • ExieE
                Exie
                last edited by Exie

                I have the same issue when I use the M5Stack ESP32 Downloader.
                However when I use a simple M5Stack Atom Matrix, its works fine.

                I am on OSX Big Sir.

                I feel like the issue is related to the CH9102 chip on the ESP32 Downloader where the Atom has the CP2104 I think.
                This theory is supported by this article here:
                https://blog.squix.org/2021/08/ch9102-driver-issues-failed-to-write-to-target-ram.html

                Confirmed, installing the driver from this thread here worked for me
                https://github.com/Xinyuan-LilyGO/LilyGo-T-Call-SIM800/issues/139

                E 1 Reply Last reply Reply Quote 0
                • E
                  erich @Exie
                  last edited by

                  @exie said in new m5stack: Failed to write to target RAM (result was 01070000):

                  I have the same issue when I use the M5Stack ESP32 Downloader.
                  However when I use a simple M5Stack Atom Matrix, its works fine.

                  I am on OSX Big Sir.

                  I feel like the issue is related to the CH9102 chip on the ESP32 Downloader where the Atom has the CP2104 I think.
                  This theory is supported by this article here:
                  https://blog.squix.org/2021/08/ch9102-driver-issues-failed-to-write-to-target-ram.html

                  Confirmed, installing the driver from this thread here worked for me
                  https://github.com/Xinyuan-LilyGO/LilyGo-T-Call-SIM800/issues/139

                  I guess you're right as I noticed on banggood/ aliexpress some products using this CH9102 chip are tagged as not Mac compatible.

                  1 Reply Last reply Reply Quote 0
                  • L
                    labixiaoxin8888 @Mackone
                    last edited by

                    @mackone try connecting the downloader's 3V3 to Stamp Pico's 5V

                    1 Reply Last reply Reply Quote 0
                    • P
                      parahooner
                      last edited by

                      I found a solution that works on Montery :-)

                      Make sure you follow the PDF instructions, this works M1 Mac M5 Epaper

                      http://www.wch.cn/downloads/CH34XSER_MAC_ZIP.html

                      B 1 Reply Last reply Reply Quote 2
                      • B
                        Bludotz @parahooner
                        last edited by

                        @parahooner Very many thanks for posting this, it completely resolved the problem.

                        1 Reply Last reply Reply Quote 0
                        • drjakobD
                          drjakob
                          last edited by

                          I still have the same problem with 5 new M5Fire on Big Sur. Two older ones burned succesful.

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

                            @drjakob Check which USB driver is in the new cores as the driver chip was changed due to the part shortage.

                            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
                            • First post
                              Last post