New firmware 0.9.6.b1 and Pymakr v1.0.0.b7 released + new complete docs

[daniel]

Dear All,

I'm pleased to announce the release of firmware version 0.9.6.b1. Get the new firmware here (under Firmware Updates).

The change log is:

• Enable SHA family functions to the hashlib module.
• Force port #2 on lorawan_send().
• If a socket is already connected, do the SSL handshake when wrapping.
• Change LoRa sockopt exception to EOPNOTSUPP.
• Correctly set LoRa socket options.
• Remove stray character in UART output while re-configuring.
• Correctly close SSL sockets.
• Add the wlan.bssid() method.
• Replace libraries with the ones built without log output.
• Update the bootloader to match newest IDF changes. Also increase CPU frequency to 160MHz.
• Update to the latest IDF from Espressif.
• Correctly trace the certificates data with the GC.
• Add the errno module.

We also released a new version of Pymakr (1.0.0.b7), get it here.

The change log is:

• Fixed multiple bugs in serial and telnet communication
• Added Light color theme
• Fixed backspace-bug in 'pycom console'
• Font type preference now working.
• Fixed compatibility with git repositories in project folder
• Fixed 7-day-update reminder on windows
• Added options to send soft-reset on connect or when running code to preferences
• Fixed 'QStackedWidget' popup exception

The new docs are complete and have effectively replaced the old ones (both for LoPy and WiPy 2.0): https://docs.pycom.io/

Cheers,
Daniel

Note: the initially released upgrader tools were affected by a bug. New installers are available and are identified as pycom_update_0.9.6.b1a.dmg, pycom_firmware_update_0.9.6.b1a.exe and pycom_update_0.9.6.b1a.tar.gz. The firmware version remains the same, and will be reported as 0.9.6.b1.

[livius]

after "succesfull" update WiPy2.0
all my WiPy2 hang totally at start
tested on two WiPy2.0 one on Expansion board second without

ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
ets Jun  8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (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:812
ho 0 tail 12 room 4
load:0x40078000,len:3692
load:0x4009f000,len:944
entry 0x4009f1f0

above never end

[AgriKinetics]

The same as @livius my two LoPy hang completely after a successful update of the 0.9.6.b1 firmware. Sometimes on reboot I get a solid Blue light from the heartbeat LED.

I have tried the safe boot (G28 and 3.3v) but, never get the orange flashing light. So now the LOPy is useless and I can't do anything at all. Pymakr says .."connected" then fails immediately.

Not sure where to go from here, but, another week another fail!

[abilio]

@AgriKinetics, @livius, can I ask what upgrade method did you use?

[livius]

@abilio
by updater tool and wire between GND and G23
2 WiPy2
one on expansion board second by UART/USB converter

P.S. one have green RGB led solid
second nothing on RGB led
WiPy without Expansion board is clear - without any my code
only upgraded previously to 9.5 and now to 9.6

[abilio]

@livius, can you tell me which OS are you using?

[AgriKinetics]

@abilio Windows 7, standard update method, G23 to GND, USB - cannot do a safe boot now either.

[abilio]

@livius, @AgriKinetics, I confirm the report. I bricked a LoPy using Windows. Thanks for the report. In the meantime you can downgrade to previous version if needed

Edit: fixed, see note on initial post of this thread

[gdpl]

I have the same issue - new firmare and new Pymakr :

Pycom console:
Connecting to a Pycom device...
Connected
Error while communicating with the Pycom device! (click to attempt to reconnect)
Connecting to a Pycom device...
Connected

[livius]

I have downgraded to 9.5 but installed new Pymakr
and now i can connect be new Pymakr to my WiPY by COM port
what was previousy not possible

[abilio]

As I mentioned in a previous post, I can confirm that there is a bug in the 0.9.6.b1 firmware. In case you want to downgrade and don't have the installer anymore, the download link now points to the version 0.9.5.b1 until further notice. Sorry for the inconvenience and thank you all for the support.

Edit: fixed, see note on initial post of this thread

[abilio]

We confirm that the initially released upgrader tools were affected by a bug. New installers are available and are identified as pycom_update_0.9.6.b1a.dmg, pycom_firmware_update_0.9.6.b1a.exe and pycom_update_0.9.6.b1a.tar.gz. The firmware version remains the same, and will be reported as 0.9.6.b1.

[Roosted]

The problem does also occur on Linux!
Just not when using the 'update' shell script - but it does brick when installing with the Python gui...

[abilio]

@Roosted, the Linux tool is meant to be run from the shell script, but thanks for the report, now is also fixed.

[robert-hh]

Dear Pycom team,

the 0.9.6.b1 update looks ok. But would you mind to keep the git repository in sync with that? I'm using a slightly modified configuration of the firmware.

[AgriKinetics]

@abilio The fix works thank you

[daniel]

@robert-hh github is up to date with the latest release... what makes you think otherwise? Please also update the IDF (https://github.com/pycom/pycom-esp-idf) if you are having compilation errors...

Cheers,
Daniel

[robert-hh]

Hello Daniel, machine.freq() returned different values. But I have rebuild the code afain, and now it seems to match. I might have uploaded appimg.bin only in the first test with ftp, and not used "make flash" via USB.

[livius]

https://docs.pycom.io/pycom_esp32/pycom_esp32/underhood.html
add DAC (coming soon)

[daniel]

@livius done, thanks :-)