1. Home
  2. Announcements & News
  3. New firmware release, version 1.5.1.b1 (supporting the SiPy)

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

New firmware release, version 1.5.1.b1 (supporting the SiPy)

  • D

    Hello everyone,

    We just made available a new firmware version 1.5.1.b1. The changes from the latest one are not many as we have been focusing on releasing the SiPy. The change log is a follows:

    • Reduce servers cycle time and ftp buffer size to solve the issue with corrupted files.
    • Compile with -O2 optimisation as required by the SiPy in order to meet Sigfox modulation timing.
    • Integrate Sigfox libraries and add the SiPy board specification.
    • Enable Bluetooth on the SiPy.

    If you don't have the new updater, make sure to get it from here:
    https://www.pycom.io/supportdownloads

    We are still busy working on the Linux tool for the SiPy, and we hope to release it tomorrow.

    Cheers,
    Daniel

    0 livius W C 4 Replies
  • C

    @daniel Marvelous News, thanks

    0
  • D

    @cvp we are working on it, we just need to enable exFAT support in FatFs.

    0
  • C

    @daniel Do you think you will soon support SD card of 64GB?
    I had asked that via a mail to Pycom support and the answer had be yes, some time ago, before I buy the Wipy2.

    And thanks for the future FTP support of spaces and accents in files and folders names

    0 D 1 Reply
  • livius

    @daniel
    i try diagnose problems with wifi in the current firmware
    and i have question:

    I (539229) wifi: station: 7c:dd:90:4c:b5:9f leave, AID = 1
I (539229) wifi: n:6 0, o:6 1, ap:6 1, sta:255 255, prof:6
I (539260) wifi: max connection already. unexpected aid!
I (539262) wifi: n:6 1, o:6 0, ap:6 1, sta:255 255, prof:6
I (539263) wifi: station: 7c:dd:90:4c:b5:9f join, AID = 1, n, 40U
ets Jun  8 2016 00:22:57

    what is unexpected aid! ?
    maybe it is not releated (because first is max connections) but..

    UPDATE
    Can someone tell me if also have some problem with wifi in current firmware?
    Or i am only one?
    I have downgraded firmware and all work ok - if i flash it back to 1.5.1 problem appear

    0
  • D

    @cvp It is possible, we will include that on the next release.

    0
  • D

    @crankshaft yes we are working on disabling those messages.

    0
  • C

    @daniel Is it possible to modify the FTP server to support file or folder names containing spaces or accents. The OS supports this kind of files/folders because I can create them in REPL, thus it should be possible because any server program uses the same instructions to create a file or a folder.
    Thanks

    0
  • C

    @daniel - is it possible to disable these wlan debug messages as it is making it very difficult for me to read my own debug data:

    W (366925) wifi: post pm rx bcn failed
W (366925) wifi: post pm rx bcn failed
W (366925) wifi: post pm rx bcn failed
W (366925) wifi: post pm rx bcn failed
W (366928) wifi: post pm rx bcn failed
W (366931) wifi: post pm rx bcn failed

    Thanks

    0
  • D

    @Wembly this weekend we'll be releasing new firmware with an option to disable power saving.

    We have been late on releasing new firmware the last couple of weeks due to the recent Sigfox activities, but things we'll get back to normal next week.

    0 C 1 Reply
  • W

    @daniel Still getting alot of these:

    W (158381) wifi: post pm rx bcn failed
    W (158382) wifi: post pm rx bcn failed
    W (158382) wifi: post pm rx bcn failed
    W (158382) wifi: post pm rx bcn failed
    W (158384) wifi: post pm rx bcn failed
    W (158388) wifi: post pm rx bcn failed
    W (158391) wifi: post pm rx bcn failed
    W (158395) wifi: post pm rx bcn failed
    W (158398) wifi: post pm rx bcn failed

    Actually worse than before. I can only have a socket open for a couple of minutes, and then its getting silently dropped. Also, because of another issue reported here, it is not possible to connect again after a socket failure.

    Is there a way to disable power save in this release ?

    0
  • P

    @Meirssv Don't confuse the version of the updater tool with the version of the firmware you will be installing. They are two different things, albeit the values of both are currently rather similar.

    The main updater linked in this thread downloads the latest firmware file automatically. However, I found that it doesn't work for me (different error to you, though :-) ). Have a look for my recent thread about firmware updates and the uart - I'm on my phone right now and finding a link is too hard. In that thread we found a solution that should work for you too.

    Pete

    0
  • M

    @TravisT Thanks!

    Issue is resolved. Indeed, it is quite confusing the version number on the download page. However, my mac refused to run the app because it wasn't trusted. I just clicked away the message without reading it... duh! Managed to start it now

    It's upgraded to 1.5.1.b1 successfully now.

    0
  • T

    @Meirssv

    I might be able to help because I had a similar issue.

    The updater software version and the latest firmware version are two different things. It confused me for a bit as well to see the version of the file being dowloaded not match. You do not need to download the updater every new firmware version. When you download and able to connect to your device the updated software gets the latest firmware and puts it on your device.

    I had trouble on my mac and it was related to macports being installed. I was not using macports anymore so I just removed it.

    https://forum.pycom.io/topic/357/pymakr-on-mac/7

    0 M 1 Reply
  • M

    Hello,

    I'm already stuck on the firmware update step...

    1. I cannot find this updater 1.5.1.b1. The link in your description (https://www.pycom.io/supportdownloads) points to a download page where I can only find a file "pycom_firmware_update_1.1.1.b1.exe or on mac pycom_update_1.1.1.b1.dmg)

    2. This application does absolutely nothing, not on my mac (10.11.6) and not on windows. I do not get any application window...

    Please advice on what I should do.

    0 T P 2 Replies
  • L

    @daniel, do you know when the deepsleep feature will be added?

    2
  • livius

    @daniel

    i have upgraded to 1.5.1 from 1.5.0

    >>> os.uname()
(sysname='WiPy', nodename='WiPy', release='1.5.1.b1', version='v1.8.6-422-g516b861 on 2017-02-07', machine='WiPy with ESP32')
>>>

    and now i have problem with ftp by wifi
    it disconnect me every few seconds (telnet work ok)

    rst:0x1 (POWERON_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:QIO, clock div:2
load:0x3fff9010,len:8
load:0x3fff9018,len:268
ho 0 tail 12 room 4
load:0x40078000,len:2656
load:0x4009f000,len:2040
entry 0x4009f12c
tcpip_task_hdlxxx : 3ffd4530, prio:18,stack:2048
I (2274) wifi: frc2_timer_task_hdl:3ffd7b48, prio:22, stack:2048
I (2279) wifi: pp_task_hdl : 3ffda3f8, prio:23, stack:8192
I (2280) wifi: sleep disable
I (3254) wifi: mode : softAP (24:0a:c4:00:6e:c3)
dhcp server start:(ip: 192.168.4.1, mask: 255.255.255.0, gw: 192.168.4.1)
16.58942 102146.0 130.268
wifi_ap
MicroPython v1.8.6-422-g516b861 on 2017-02-07; WiPy with ESP32
Type "help()" for more information.
>>> I (4752) wifi: n:6 0, o:6 0, ap:6 1, sta:255 255, prof:6
I (4752) wifi: station: 00:0c:f1:00:48:6b join, AID = 1, b, 20
I (11263) wifi: n:6 1, o:6 0, ap:6 1, sta:255 255, prof:6
I (11264) wifi: station: 7c:dd:90:4c:b5:9f join, AID = 2, n, 40U
I (30080) wifi: station: 7c:dd:90:4c:b5:9f leave, AID = 2
I (30080) wifi: n:6 0, o:6 1, ap:6 1, sta:255 255, prof:6
I (31040) wifi: n:6 1, o:6 0, ap:6 1, sta:255 255, prof:6
I (31041) wifi: station: 7c:dd:90:4c:b5:9f join, AID = 2, n, 40U
I (57272) wifi: station: 7c:dd:90:4c:b5:9f leave, AID = 2
I (57273) wifi: n:6 0, o:6 1, ap:6 1, sta:255 255, prof:6
I (58136) wifi: n:6 1, o:6 0, ap:6 1, sta:255 255, prof:6
I (58137) wifi: station: 7c:dd:90:4c:b5:9f join, AID = 2, n, 40U
I (105199) wifi: station: 7c:dd:90:4c:b5:9f leave, AID = 2
I (105200) wifi: n:6 0, o:6 1, ap:6 1, sta:255 255, prof:6
I (106060) wifi: n:6 1, o:6 0, ap:6 1, sta:255 255, prof:6
I (106060) wifi: station: 7c:dd:90:4c:b5:9f join, AID = 2, n, 40U
I (247788) wifi: station: 7c:dd:90:4c:b5:9f leave, AID = 2
I (247789) wifi: n:6 0, o:6 1, ap:6 1, sta:255 255, prof:6
I (248651) wifi: n:6 1, o:6 0, ap:6 1, sta:255 255, prof:6
I (248651) wifi: station: 7c:dd:90:4c:b5:9f join, AID = 2, n, 40U
I (331797) wifi: station: 7c:dd:90:4c:b5:9f leave, AID = 2
I (331797) wifi: n:6 0, o:6 1, ap:6 1, sta:255 255, prof:6
I (332548) wifi: n:6 1, o:6 0, ap:6 1, sta:255 255, prof:6
I (332549) wifi: station: 7c:dd:90:4c:b5:9f join, AID = 2, n, 40U

    UPDATE
    it looks strange - after "join" i can ping
    but every few ping there is really long ping and back short ping

    Pinging 192.168.4.1 with 32 bytes of data:
Reply from 192.168.4.1: bytes=32 time=3ms TTL=255
Reply from 192.168.4.1: bytes=32 time=7ms TTL=255
Reply from 192.168.4.1: bytes=32 time=8ms TTL=255
Reply from 192.168.4.1: bytes=32 time=4ms TTL=255
Reply from 192.168.4.1: bytes=32 time<1ms TTL=255
**Reply from 192.168.4.1: bytes=32 time=1585ms TTL=255**
Reply from 192.168.4.1: bytes=32 time<1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=5ms TTL=255
Reply from 192.168.4.1: bytes=32 time=2ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=2ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=65ms TTL=255
Reply from 192.168.4.1: bytes=32 time=79ms TTL=255
Reply from 192.168.4.1: bytes=32 time=87ms TTL=255
**Request timed out.
Reply from 192.168.4.1: bytes=32 time=1253ms TTL=255
Reply from 192.168.4.1: bytes=32 time=612ms TTL=255
Reply from 192.168.4.1: bytes=32 time=116ms TTL=255**
Reply from 192.168.4.1: bytes=32 time=2ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=3ms TTL=255
Reply from 192.168.4.1: bytes=32 time=2ms TTL=255
Reply from 192.168.4.1: bytes=32 time<1ms TTL=255
**Reply from 192.168.4.1: bytes=32 time=1082ms TTL=255**
Reply from 192.168.4.1: bytes=32 time=5ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
Reply from 192.168.4.1: bytes=32 time<1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=4ms TTL=255
Reply from 192.168.4.1: bytes=32 time=12ms TTL=255
Reply from 192.168.4.1: bytes=32 time=3ms TTL=255
Reply from 192.168.4.1: bytes=32 time=11ms TTL=255
Reply from 192.168.4.1: bytes=32 time=3ms TTL=255
Reply from 192.168.4.1: bytes=32 time=5ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
**Reply from 192.168.4.1: bytes=32 time=1795ms TTL=255**
Reply from 192.168.4.1: bytes=32 time<1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=16ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=6ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=4ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=2ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
**Reply from 192.168.4.1: bytes=32 time=1715ms TTL=255**
Reply from 192.168.4.1: bytes=32 time<1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=5ms TTL=255
Reply from 192.168.4.1: bytes=32 time=8ms TTL=255
Reply from 192.168.4.1: bytes=32 time=6ms TTL=255
Reply from 192.168.4.1: bytes=32 time=5ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=6ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
**Reply from 192.168.4.1: bytes=32 time=1710ms TTL=255**
Reply from 192.168.4.1: bytes=32 time=32ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
Reply from 192.168.4.1: bytes=32 time<1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=1ms TTL=255
Reply from 192.168.4.1: bytes=32 time=6ms TTL=255
Reply from 192.168.4.1: bytes=32 time=7ms TTL=255
Reply from 192.168.4.1: bytes=32 time=7ms TTL=255
Reply from 192.168.4.1: bytes=32 time=8ms TTL=255
Reply from 192.168.4.1: bytes=32 time=4ms TTL=255

    i mark lines with stars

    UPDATE 2
    i forgot to say that this is only in AP mode, STA mode work ok

    0
  • D

    Hello everyone,

    JSON problem is fixed (no need to download a new tool), just try to update again. Thanks.

    Cheers,
    Daniel

    0
  • D

    We are currently checking this JSON error. We'll update you shortly.

    Cheers,
    Daniel

    0
  • Z

    Unable to upgrade.
    Connecting.....................................
    Failure!

    Previous version upgrades no problem, so pins are properly bridged

    0
Log in to reply
 

Pycom on Twitter