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

    New release New firmware release 1.2.2.b1

    Scheduled Pinned Locked Moved Announcements & News
    36 Posts 10 Posters 13.4k Views 10 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
      last edited by

      As a hint for everyone who is building the image her- or himself:
      Please update the pycom-esp-idf too. Otherwise the build will not run.

      1 Reply Last reply Reply Quote 0
      • J Offline
        jmarcelino
        last edited by

        OK first let me say the new release is a massive improvement, before this same code would crash after only 140 or so Alarm events. However it's still crashing without fail in the 2500-3000 range.

        Note I may well be doing something wrong as I just started with MicroPython this Xmas!

        First the crash:

        [...some output here]
Elapsed 2690 s 
Hourly average 22.84 mAh
Consumed 17.07
Elapsed 2691 s 
Hourly average 22.83 mAh
Consumed 17.07
Elapsed 2692 s 
Hourly average 22.82 mAh
Guru Meditation Error of type InstrFetchProhibited occurred on core  0. Exception was unhandled.
Register dump:
PC      : 0x00692cc0  PS      : 0x00060430  A0      : 0x800ecdd4  A1      : 0x3ffc4bb0  
A2      : 0x3ffc5490  A3      : 0x00000001  A4      : 0x00000000  A5      : 0x3ffc4bd0  
A6      : 0x400dc2cc  A7      : 0x3ffc1340  A8      : 0x800ecd90  A9      : 0x3ffc4b90  
A10     : 0x3ffc5490  A11     : 0x00000001  A12     : 0x00000000  A13     : 0x3ffc4bd0  
A14     : 0xb33fffff  A15     : 0x3ffc4b70  SAR     : 0x0000001c  EXCCAUSE: 0x00000014  
EXCVADDR: 0x00692cc0  LBEG    : 0x4000c2e0  LEND    : 0x4000c2f6  LCOUNT  : 0xffffffff  

Backtrace: 0x00692cc0:0x3ffc4bb0 0x400ecdd4:0x3ffc4bd0 0x400dc2dc:0x3ffc4c00 0x400e0e3e:0x3ffc4c20 0x400d81d8:0x3ffc4ca0

Rebooting...

        and my code (shortened version I'm using for testing)

        from machine import Pin
from machine import Timer
import micropython 
micropython.alloc_emergency_exception_buf(100)

class LTC4150(object):
    ah_quanta = 0.17067759
    
    def __init__(self):
        self.p_in = Pin('P15', mode=Pin.IN, pull=None)
        self.p_in.callback(Pin.IRQ_FALLING, self.__pin_handler) 
        self.chrono = Timer.Chrono()
        self.chrono.start()
        self.count = 0
        self.time = 0 
        self.lastTime = 0 
        
    def __pin_handler(self, arg):
        self.count = self.count + 1



def periodic_handler(alarm):
    mA = cc.count* cc.ah_quanta
    seconds = cc.chrono.read()
    print("Consumed %.2f" % mA ) 
    print ("Elapsed %d s " % seconds)
    print("Hourly average %.2f mAh" % ((3600*mA)/seconds))


cc = LTC4150()

alarm = Timer.Alarm(periodic_handler, 1, periodic=True)

        If I increase the period say to 10s it still crashes just takes 10x as long, so I think it's more to do with the number of events

        Thanks for the help

        1 Reply Last reply Reply Quote 2
        • D Offline
          daniel
          last edited by

          @jmarcelino thanks for the report, we are investigating why those crashes are occurring. We'll let you know once we discover the root cause.

          Cheers,
          Daniel

          1 Reply Last reply Reply Quote 0
          • P Offline
            pdp8user
            last edited by

            Do we have to call the finalizer explicitly, or is it automatic?

            D 1 Reply Last reply Reply Quote 0
            • M Offline
              mohpor
              last edited by

              @daniel

              Wonderful update I gotta admit. Fixed a lot of memory problems! One problem that has been fixed and I haven't see anybody reporting was that you could run your code 2 times and then it would crash on the 3rd try. It is now fixed and I can upload my code as many time as I want to! Fantastic.

              Cheers,
              M.

              D 1 Reply Last reply Reply Quote 0
              • D Offline
                daniel @mohpor
                last edited by

                @mohpor cool :-) thanks for the feedback!

                Cheers,
                Daniel

                1 Reply Last reply Reply Quote 0
                • D Offline
                  daniel @pdp8user
                  last edited by

                  @pdp8user it's automatic.

                  P 1 Reply Last reply Reply Quote 0
                  • P Offline
                    pdp8user @daniel
                    last edited by

                    @daniel Thanks for that and the prompt reply.

                    Keep up the good work! The memory issues have been frustrating, because as @mohpor says, something would work some times and not others.

                    I'm still having some issues in that respect, which is why the question about the finalizer. I've still to clarify the details, then I'll report it to you.

                    Cheers,
                    Brian

                    D 1 Reply Last reply Reply Quote 0
                    • D Offline
                      daniel @pdp8user
                      last edited by

                      @pdp8user thanks. Yes, please let us know the details about the issues that you are experiencing so that we can analyze the problem.

                      1 Reply Last reply Reply Quote 0
                      • bmarkusB Offline
                        bmarkus
                        last edited by

                        On the download page current firmware version is 1.2.0.b1 see

                        https://www.pycom.io/support/supportdownloads/

                        L 1 Reply Last reply Reply Quote 0
                        • L Offline
                          livius @bmarkus
                          last edited by livius

                          @bmarkus
                          this is only not updated web page label
                          updater tool update to version expected 1.2.2.b1

                          think about people first, then computers

                          1 Reply Last reply Reply Quote 0
                          • M Offline
                            mohpor
                            last edited by

                            @daniel
                            Hi again,
                            Are we still up for today's update? (despite of the early 1.2.2.b1 update)

                            D 1 Reply Last reply Reply Quote 1
                            • D Offline
                              daniel @mohpor
                              last edited by daniel

                              @mohpor the release is going to be out tomorrow (Friday 13), we still need one more day to complete all the features that we are targeting for this next release. Apologies for the delay...

                              Cheers,
                              Daniel

                              L 1 Reply Last reply Reply Quote 0
                              • L Offline
                                livius @daniel
                                last edited by

                                @daniel
                                sorry for spam but good date "Friday 13" :)

                                think about people first, then computers

                                D 1 Reply Last reply Reply Quote 0
                                • D Offline
                                  daniel @livius
                                  last edited by

                                  @livius haha :-)

                                  1 Reply Last reply Reply Quote 0
                                  • M Offline
                                    minkley
                                    last edited by

                                    I think the latest firmware for Linux is borked :) It's my first hands-on with the wipy2 and the upater failed. Digging around I noticed there are no firmware files in the tgz.

                                    There is no firmware directory as per the previous v 0.9.7.. version. I used this link https://software.pycom.io/findupgrade?product=pycom-firmware-updater&type=all&platform=unix&redirect=true

                                    Here are the extracts so you can see what I am talking about.

                                    tar -tvzf pycom_update_1.0.0.b2.tar.gz
                                    -rw-r--r-- abiliojr/staff 247 2016-12-17 04:17 pyupgrade/README
                                    drwxr-xr-x abiliojr/staff 0 2016-12-19 12:38 pyupgrade/bin/
                                    -rw-r--r-- abiliojr/staff 0 2016-12-17 04:17 pyupgrade/bin/init.py
                                    -rw-r--r-- abiliojr/staff 92013 2016-12-17 04:17 pyupgrade/bin/esptool.py
                                    -rwxr-xr-x abiliojr/staff 4046 2016-12-17 04:17 pyupgrade/bin/updater.py
                                    -rw-r--r-- abiliojr/staff 22135 2016-12-17 04:17 pyupgrade/lopyupdate.py
                                    -rw-r--r-- abiliojr/staff 44124 2016-12-17 04:17 pyupgrade/spinner.gif
                                    -rwxr-xr-x abiliojr/staff 7316 2016-12-19 19:14 pyupgrade/update

                                    tar -tvzf pycom_update_0.9.7.b1.tar.gz
                                    drwxr-xr-x abiliojr/staff 0 2016-11-26 08:44 pyupgrade/bin/
                                    -rw-r--r-- abiliojr/staff 0 2016-10-27 20:13 pyupgrade/bin/init.py
                                    -rw-r--r-- abiliojr/staff 92032 2016-11-26 08:19 pyupgrade/bin/esptool.py
                                    -rwxr-xr-x abiliojr/staff 2408 2016-11-26 08:44 pyupgrade/bin/updater.py
                                    -rwxr-xr-x abiliojr/staff 210 2016-12-03 05:12 pyupgrade/._firmware
                                    drwxr-xr-x abiliojr/staff 0 2016-12-03 05:12 pyupgrade/firmware/
                                    -rw-r--r-- abiliojr/staff 210 2016-12-03 04:31 pyupgrade/firmware/._bootloader.bin
                                    -rw-r--r-- abiliojr/staff 5520 2016-12-03 04:31 pyupgrade/firmware/bootloader.bin
                                    -rw-r--r-- abiliojr/staff 210 2016-12-03 04:44 pyupgrade/firmware/._lopy_0.9.7.b1_868.bin
                                    -rw-r--r-- abiliojr/staff 828448 2016-12-03 04:44 pyupgrade/firmware/lopy_0.9.7.b1_868.bin
                                    -rw-r--r-- abiliojr/staff 210 2016-12-03 04:43 pyupgrade/firmware/._lopy_0.9.7.b1_915.bin
                                    -rw-r--r-- abiliojr/staff 828272 2016-12-03 04:43 pyupgrade/firmware/lopy_0.9.7.b1_915.bin
                                    -rw-r--r-- abiliojr/staff 210 2016-12-03 04:32 pyupgrade/firmware/._partitions.bin
                                    -rw-r--r-- abiliojr/staff 3072 2016-12-03 04:32 pyupgrade/firmware/partitions.bin
                                    -rw-r--r-- abiliojr/staff 210 2016-12-03 04:46 pyupgrade/firmware/._wipy_0.9.7.b1.bin
                                    -rw-r--r-- abiliojr/staff 820400 2016-12-03 04:46 pyupgrade/firmware/wipy_0.9.7.b1.bin
                                    -rw-r--r-- abiliojr/staff 14383 2016-11-26 08:43 pyupgrade/lopyupdate.py
                                    -rwxr-xr-x abiliojr/staff 5765 2016-11-06 03:32 pyupgrade/update

                                    Or am I mistaken :)

                                    Thanks guys

                                    D 1 Reply Last reply Reply Quote 0
                                    • D Offline
                                      daniel @minkley
                                      last edited by

                                      @minkley the updater now connects to the internet every time to get the latest files. Normally the updater prints an error message with the reason of the failure. Could you try again and copy paste the message here? Thanks.

                                      M 1 Reply Last reply Reply Quote 0
                                      • M Offline
                                        minkley
                                        last edited by

                                        Traceback (most recent call last):
                                        File "./bin/updater.py", line 3, in <module>
                                        from esptool import ESP32ROM
                                        File "/home/mink/pyupgrade/bin/esptool.py", line 25, in <module>
                                        import serial
                                        ImportError: No module named serial

                                        1 Reply Last reply Reply Quote 0
                                        • D Offline
                                          daniel
                                          last edited by

                                          Ok, it looks like only the Windows and OS X updater tools come with pyserial bundled. Please install pyserial manually and run the updater again:

                                          http://pyserial.readthedocs.io/en/latest/pyserial.html#installation

                                          We will add this to the docs. Thanks.

                                          Cheers,
                                          Daniel

                                          1 Reply Last reply Reply Quote 0
                                          • M Offline
                                            minkley @daniel
                                            last edited by

                                            @daniel
                                            Thanks Daniel
                                            I installed pyserial it's getting past that now but failing with the following message

                                            Namespace(file=None, port='/dev/ttyUSB0', speed=115200, tar='/tmp/tmp.nBBvLQ6mbC/update.tar.gz')
                                            Connecting...
                                            Exception: Failed to connect to ESP32: Timed out waiting for packet header, on line 121
                                            root@pecan:/home/mink/pyupgrade#

                                            So I guess the ESP32 is not live , perhaps you clarify something for about the firmware upgrade process. As I don't have an expansion but am using a USB serial cable, where does wipy2 get it's power from?

                                            As an FYI, I'm using the same USB serial cable I connect to various other devices eg my CubieTruck3, so I know it works

                                            Any guidance would be appreciated.

                                            thanks

                                            M 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
                                            • 2
                                            • 1 / 2
                                            • First post
                                              Last post

                                            Pycom on Twitter

                                            Pycom