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

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?

PCA

@daniel no crash in safe mode.
main.py is empty (just a comment)
boot.py is

the dupterm to the uart and
wifi connection to my Wlan (and it works as usual)
do you need the full code ?
Pascal

rdixey

Hi Daniel,

I received new LoPy yesterday. Using Ubuntu 16.04 / ttyUSB0 I was able to complete the update to firmware version 0.9.6.b1.

uos.uname().release
'0.9.6.b1'

Then when attempting to connect my LoPy to my WiFi router it receives 'Guru Meditation Error of type InstrFetchProhibited occurred on core 0.' Does a dump and reboots.

What is the cause of this?

I have tried multiple times with the same results.

I do not expect this to happen since I am following the guide exactly.

import machine
from network import WLAN
wlan = WLAN(mode=WLAN.STA)
nets = wlan.scan()
for net in nets:
... if net.ssid == 'DixeyLAN_WiFi':
... print('Network found!')
... wlan.connect(net.ssid, auth=(net.sec, 'cbcd062459'), timeout=50)
... while not wlan.isconnected():
... machine.idle()
... print('WLAN connection succeeded!')
... break
...
...
...
Network found!
I (734541) wifi: n:1 0, o:6 0, ap:255 255, sta:1 0, prof:6
I (735516) wifi: state: 0 -> 2 (b0)
I (735519) wifi: state: 2 -> 3 (0)
I (735523) wifi: state: 3 -> 5 (10)
I (735538) wifi: connected with DixeyLAN_WiFi, channel 1
Guru Meditation Error of type InstrFetchProhibited occurred on core 0. Exception was unhandled.
Register dump:
PC : 002c002c PS : 00060330 A0 : 801250de A1 : 3ffdfc80
A2 : 00000001 A3 : 3ffd9934 A4 : 002c002c A5 : 00000008
A6 : 00000000 A7 : 3ffd35e8 A8 : 8011ed60 A9 : 00000002
A10 : 3ffd9934 A11 : 00000001 A12 : 3ffd5164 A13 : 00000000
A14 : 3ffdf584 A15 : 3ffd4f48 SAR : 00000019 EXCCAUSE: 00000014
EXCVADDR: 002c002c LBEG : 4000c349 LEND : 4000c36b LCOUNT : ffffffff
Rebooting...
ets Jun 8 2016 00:22:57

rst:0x3 (SW_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
��XTAL 40Mct 20 2016 12:36:18
I (872) phy: phy_version: 246, Nov 18 2016, 17:30:07, 0, 0

tcpip_task_hdlxxx : 3ffdfd50, prio:18,stack:2048
frc2_timer_task_hdl:3ffe98a8, prio:22, stack:2048
I (1612) wifi: pp_task_hdl : 3ffec100, prio:23, stack:8192
mode : softAP(24:0a:c4:00:0f:c3)
dhcp server start:(ip: 192.168.4.1, mask: 255.255.255.0, gw: 192.168.4.1)
MicroPython v1.8.6-40-gd10463e on 2016-11-25; LoPy with ESP32
Type "help()" for more information.

rdixey

@rdixey

Additional info:
I have a second new LoPy that i did not update and it connects to the WiFi network successfully using the code in the guide:

uos.uname()
(sysname='ESP32', nodename='ESP32', release='0.9.0b', version='8785822 on 2016-10-06', machine='LoPy with ESP32')
import machine
from network import WLAN
wlan = WLAN(mode=WLAN.STA)
mode : sta(24:0a:c4:00:b9:54)
nets = wlan.scan()
for net in nets:
... if net.ssid == 'DixeyLAN_WiFi':
... print('Network found!')
... wlan.connect(net.ssid, auth=(net.sec, 'cbcd062459'), timeout=5000)
... while not wlan.isconnected():
... machine.idle()
... print('WLAN connection succeeded!')
... break
...
...
...
Network found!
n:1 0, o:6 0, ap:255 255, sta:1 0, prof:6
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0

WLAN connection succeeded!

livius

@rdixey
interesting - then bug was introduced in some recent firmware
i am also interesting because my WiPy2.0 also have the same problem like you
but my not restart (crash) only repeatedly print same and same info state: ....

P.S use ``` to include source code

JF002

I have the same issue as @rdixey : It crashed after w while (seconds) after a successful connection to my home wifi router.
Here is what i do:

>>> from network import WLAN
>>> wlan = WLAN(mode=WLAN.STA)
mode : sta(24:0a:c4:00:c0:52)
>>> wlan.connect('MY_SSID', auth=('WLAN.WPA2', '********************'))
>>> I (24972) wifi: n:9 0, o:6 0, ap:255 255, sta:9 0, prof:6
I (25946) wifi: state: 0 -> 2 (b0)
I (25949) wifi: state: 2 -> 3 (0)
I (25953) wifi: state: 3 -> 5 (10)
I (25970) wifi: connected with MY_SSID, channel 9

... Wait 10 seconds

Guru Meditation Error of type InstrFetchProhibited occurred on core   0. Exception was unhandled.
Register dump:
PC      :  002c002c  PS      :  00060330  A0      :  801252ce  A1      :  3ffdfa30  
A2      :  00000001  A3      :  3ffd9738  A4      :  002c002c  A5      :  00000008  
A6      :  00000000  A7      :  3ffd3398  A8      :  8011ef50  A9      :  00000002  
A10     :  3ffd9738  A11     :  00000001  A12     :  3ffd4f14  A13     :  00000000  
A14     :  3ffdf338  A15     :  3ffd4cf8  SAR     :  00000019  EXCCAUSE:  00000014  
EXCVADDR:  002c002c  LBEG    :  4000c2e0  LEND    :  4000c2f6  LCOUNT  :  ffffffff  
Rebooting...
ets Jun  8 2016 00:22:57

rst:0x3 (SW_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
rtc v134 Oct 20 2016 12:36:18øXTAL 40M
I (876) phy: phy_version: 246, Nov 18 2016, 17:30:07, 0, 0

tcpip_task_hdlxxx : 3ffdfb18, prio:18,stack:2048
frc2_timer_task_hdl:3ffe9680, prio:22, stack:2048
I (1636) wifi: pp_task_hdl : 3ffebed8, prio:23, stack:8192
mode : softAP(24:0a:c4:00:c0:53)
dhcp server start:(ip: 192.168.4.1, mask: 255.255.255.0, gw: 192.168.4.1)
MicroPython v1.8.6-40-gd10463e on 2016-11-25; LoPy with ESP32
Type "help()" for more information.
>>>

This a brand new Lopy, updated to the "new" 0.9.6.b1 firmware:

>>> 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')

Any idea?

abilio

@JF002 there is a new firmware, 0.9.7.b1. Can you test it and post your issue in case it keeps happening?

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

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

Pycom on Twitter