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

[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 :-)

[PCA]

Dear Pycom Team,
update successful to 0.9.6.b1 on my LoPy.
But crashes a few second after the end of the boot process....

MicroPython v1.8.6-40-gd10463e on 2016-11-25; LoPy with ESP32
Type "help()" for more information.

import os
os.uname()
(sysname='LoPy', nodename='LoPy', release='0.9.6.b1', version='v1.8.6-40-gd10463e on 2016-11-25', machine='LoPy with ESP32')

Guru Meditation Error of type InstrFetchProhibited occurred on core 0. Exception was unhandled.
Register dump:
PC : 002c002c PS : 00060330 A0 : 801252ce A1 : 3ffdfac0
A2 : 00000001 A3 : 3ffd9274 A4 : 002c002c A5 : 00000008
A6 : 00000000 A7 : 3ffd3398 A8 : 8011ef50 A9 : 00000002
A10 : 3ffd9274 A11 : 00000001 A12 : 3ffd4f14 A13 : 00000000
A14 : 3ffdf3c4 A15 : 3ffd4cf8 SAR : 00000019 EXCCAUSE: 00000014
EXCVADDR: 002c002c LBEG : 00000000 LEND : 00000000 LCOUNT : 00000000
Rebooting...

Can I help in sending other data ?

[daniel]

@PCA does it crash if you boot in safe mode? (https://docs.pycom.io/pycom_esp32/pycom_esp32/general.html?highlight=safe boot#boot-modes-and-safe-boot)

What are your main.py and boot.py doing?