New release New firmware release 1.2.2.b1

  • Nano Gateway example doesn't work anymore

    It seems that calling lora_sock.recv(256) after lora_sock.send(pkg) is blocking the lora_sock.send function. The package is only send after the receive function is timed out. This kind of defeats the purpose of sending an ACK package. Does anyone have a solution?

    Keep up the good work!

  • administrators

    @minkley have a look here:

    You should connect 5V from the USB and GND. You also need to connect Rx and Tx on the program port. Don't forget to wire P2 to GND and reset to enter flashing mode as instructed by the updater tool.


  • @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')
    Exception: Failed to connect to ESP32: Timed out waiting for packet header, on line 121

    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.


  • administrators

    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:

    We will add this to the docs. Thanks.


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

  • administrators

    @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.

  • 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

    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/
    -rw-r--r-- abiliojr/staff 92013 2016-12-17 04:17 pyupgrade/bin/
    -rwxr-xr-x abiliojr/staff 4046 2016-12-17 04:17 pyupgrade/bin/
    -rw-r--r-- abiliojr/staff 22135 2016-12-17 04:17 pyupgrade/
    -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/
    -rw-r--r-- abiliojr/staff 92032 2016-11-26 08:19 pyupgrade/bin/
    -rwxr-xr-x abiliojr/staff 2408 2016-11-26 08:44 pyupgrade/bin/
    -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/
    -rwxr-xr-x abiliojr/staff 5765 2016-11-06 03:32 pyupgrade/update

    Or am I mistaken :)

    Thanks guys

  • administrators

    @livius haha :-)

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

  • administrators

    @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...


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

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

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

  • administrators

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

  • @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.


  • administrators

    @pdp8user it's automatic.

  • administrators

    @mohpor cool :-) thanks for the feedback!


  • @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.


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

  • administrators

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


Log in to reply

Pycom on Twitter

Looks like your connection to Pycom Forum was lost, please wait while we try to reconnect.