Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    FiPy Core Dump

    Scheduled Pinned Locked Moved FiPy
    fipycore dump
    16 Posts 4 Posters 2.9k Views 4 Watching
    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.
    • robert-hhR Offline
      robert-hh @adrien3d
      last edited by

      @adrien3d It used to be an option to erase flash and then reload the formware. I'm not using the standard firmware loader, so I do not know whether this method is avalable, and erasing the whole flash also erases the registration information for the communication modules. May @seb could shed some light on that.

      sebS 1 Reply Last reply Reply Quote 0
      • sebS Offline
        seb
        last edited by

        Hey,

        We are aware of this bug, it seems to be a race condition in the firmware. The next firmware release will have this bug fixed.

        A S 2 Replies Last reply Reply Quote 1
        • sebS Offline
          seb @robert-hh
          last edited by

          @robert-hh
          Erasing the flash does not erase the registration details, these are kept in a database on our end and the firmware updater will automatically add them in with each update. If there is an issue with registration details we recommend customers email support@pycom.io and we will be able to reset the info in our database.

          1 Reply Last reply Reply Quote 0
          • A Offline
            adrien3d @seb
            last edited by

            @seb Do you have any ETA for a firmware release that will fix this bug?

            sebS 1 Reply Last reply Reply Quote 0
            • sebS Offline
              seb @adrien3d
              last edited by

              @adrien3d
              I can't provide an exact date but it will be included with the next firmware version which will be released within the next two weeks

              1 Reply Last reply Reply Quote 0
              • S Offline
                ssmith @seb
                last edited by

                @seb Can you provide some more details on this? We've been fighting a crash like this for the past week on the LoPy4.

                Thanks,
                Steve

                sebS 1 Reply Last reply Reply Quote 0
                • sebS Offline
                  seb @ssmith
                  last edited by

                  @ssmith
                  Hi,
                  I've been informed it is caused by a race condition that occurs early in the boot process, I'm afraid that's all I know. It is actively being worked on as we speak and a fix will be released along with our next firmware update.

                  1 Reply Last reply Reply Quote 0
                  • A Offline
                    adrien3d
                    last edited by

                    Does the 1.16.0b1 firmware solves the problem ?

                    sebS 1 Reply Last reply Reply Quote 0
                    • sebS Offline
                      seb @adrien3d
                      last edited by

                      @adrien3d
                      Hi,

                      Unfortunately this issue is proving more elusive than we previously thought. It is being actively investigated, I will keep you updated with the progress.

                      1 Reply Last reply Reply Quote 0
                      • sebS Offline
                        seb
                        last edited by

                        Can you please try the new firmware and report if this fixes the issue you are experiencing?

                        A 1 Reply Last reply Reply Quote 0
                        • A Offline
                          adrien3d @seb
                          last edited by

                          @seb Not fixing anything :/

                          sebS 1 Reply Last reply Reply Quote 0
                          • sebS Offline
                            seb @adrien3d
                            last edited by

                            @adrien3d

                            If you can share the complete back trace generated by the latest firmware, I'll pass this on to the firmware team to look over again. With the back trace they can pinpoint where the error occurs.

                            A 1 Reply Last reply Reply Quote 0
                            • A Offline
                              adrien3d @seb
                              last edited by adrien3d

                              I've merged what was comprehensible:

                              ets Jun  8 2016 00:22:57
                              
                              rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
                              coUMP END =================
                              Rebootin0,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
                              mx17 (SPI_FAST_FLASH_BOOT)
                              configsip: 0, SPIWP:0xee
                              clk_drv:0x0:1060
                              load:0x4009fa00,len:0
                              ho 12 tail 0 room 4
                              load:0x4009fode:DIO, clock div:1
                              load:0x3fff9028,len:8
                              load:0x3fff9030,lenabort() was called at PC 0x4008dbb4 on core 1
                              
                              Backtrace: 0x4a00,len:14096
                              entry 0x400a05e0
                              x40083c16:0x3ffd42f0 0x40083cb3:0x3ffd4320 0x4015ea88:0x3ffd437008e05f:0x3ffd4280 0x4008e090:0x3ffd42a0 0x4008dbb4:0x3ffd42c0 03f0 0x400dce42:0x3ffd4430
                              
                              ================= CORE DUMP START 0 0x4015d95b:0x3ffd4390 0x4014d4d1:0x3ffd43d0 0x400e8a2c:0x3ffd4T+JBAAALFP8PyxT/D+8RP0/JFP8PxQAAAAAAAAAAAAAALxE/T8AAAAA
                              BQAAAL=================
                              
                              Connecting on /dev/cu.usbmodemPy343431...
                              /Users/danicampora/Code/Espressif/IDF/esp-idf-20180112/componena00,len:14096
                              entry 0x400a05e0
                              bort() was callea at PC 0xs008aaa8 on cor0x00
                              
                              Backtrace: 0x40ts/freertos/./queue.c:718 (xQueueGenericSend)- assert failed!
                              a4015d282:0x3ffd3bb0 0x4015d41a:0x3ffd3bd0 0x40155916:0x3ffd3c00 0x4014e3ec:0x3ffd3c20
                              
                              ====x3ffd3b50 0x4008aaa8:0x3ffd3b70 0x=============
                              HC0AAA4AAABsAQAA
                              BFP9P3A6/T+wPP0/
                              oDn9P1A8/T+N 0x4014e3ec:0x3ffd3c20
                              
                              ================= CORE DUMP END =================
                              Rebooting...
                              ets Jun  8 2016 00:22:57
                              
                              rst:0xc (SW_CPU_RESET),boot:0x12 (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:0x3fff9028,len:8
                              load:0x3fff9030,len:1060
                              load:0x4009fa00,len:0
                              ho 12 tail 0 room 4
                              load:0x4009fa00,len:14096
                              entry 0x400a05e0
                              abort() was called at PC 0x4008dbb4 on core 1
                              
                              Backtrace: 0x4008e05f:0x3ffd4280 0x4008e090:0x3ffd42a0 0x4008dbb4:0x3ffd42c0 0x40083c16:0x3ffd42f0 0x40083cb3:0x3ffd4320 0x4015ea88:0x3ffd4370 0x4015d95b:0x3ffd4390 0x4014d4d1:0x3ffd43d0 0x400e8a2c:0x3ffd43f0 0x400dce42:0x3ffd4430
                              
                              ================= CORE DUMP START =================
                              

                              Looks like this line will provide you more infos:

                              Backtrace: 0x40ts/freertos/./queue.c:718 (xQueueGenericSend)- assert failed!
                              
                              1 Reply Last reply Reply Quote 0

                              Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                              Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                              With your input, this post could be even better 💗

                              Register Login
                              • 1 / 1
                              • First post
                                Last post

                              Pycom on Twitter

                              Pycom