New firmware release, version 1.6.0.b1

[livius]

@daniel said in New firmware release, version 1.6.0.b1:

could it be that your file system is corrupted from previous firmware versions? Could you try:
import os
os.mkfs('/flash')

to format the file system and start from scratch...
Cheers,
Daniel

formated and tested on 1.6.1.b1 and still file corruption :(
now i am testing 1.6.3
on the left you have oryginal file - on the right corrupted

UPDATE
flashed to 1.6.3
formated and error is same -

but!

It is not visible at start see steps:

1. write e.g. test.py (copy normal onewire content twice to this file on computer)
2. copy this file to wipy throught ftp
3. download it and see if it is ok - yes it is ok
4. disable power (totally)
5. power on wipy
6. connect to it by ftp and download test.py - now it is corrupted

UPDATE2
It looks like it happened not always
after few try storing file and restart i finally have file ok (strange)

[PCA]

I confirm the issue with bluetooth callback disabled in 1.6.0.b1 is solved in 1.6.3.b2.
thanks @daniel

[Neo]

@Daniel On LoPy with 1.6.3.b2 the issue with the gc.collect()/memeory release is till persistent. Please run that test file with the LoRa socket recv and check it.

When do you think that we will have a fix for this? It is CRITICAL from many people point o view.

(sysname='LoPy', nodename='LoPy', release='1.6.3.b2', version='v1.8.6-464-g0f843911 on 2017-02-17', machine='LoPy with ESP32', lorawan='1.0.0')

[daniel]

@Neo I agree it's super CRITICAL. It's on the top of our priorities at this moment. We'll do our best to resolve it ASAP.

Cheers,
Daniel

[JF002]

@Neo said in New firmware release, version 1.6.0.b1:

@Daniel On LoPy with 1.6.3.b2 the issue with the gc.collect()/memeory release is till persistent. Please run that test file with the LoRa socket recv and check it.

When do you think that we will have a fix for this? It is CRITICAL from many people point o view.

(sysname='LoPy', nodename='LoPy', release='1.6.3.b2', version='v1.8.6-464-g0f843911 on 2017-02-17', machine='LoPy with ESP32', lorawan='1.0.0')

I also still have this bug... I was hoping it would be resolved in this update (1.3.6), but it doesn't seem to be the case... Do you want us to fill a bug on github?

Thanks!

[daniel]

@JF002 yes please do report it on Github with a piece of code to reproduce the issue easily (include your boot.py as well if possible). Thanks!

[JF002]

@daniel said in New firmware release, version 1.6.0.b1:

@JF002 yes please do report it on Github with a piece of code to reproduce the issue easily (include your boot.py as well if possible). Thanks!

Here it is :) https://github.com/pycom/pycom-micropython/issues/82

[crankshaft]

@daniel - as you requested, I re-posted my issues / bugs on github duplicating the posts I already made on the this forum, and surprise, surprise, no replies on the github issues either.

I am very disappointed that despite posting my issues, nobody has taken a few minutes to verify / validate or even ask me any questions regarding these issues, I think that you really need to review your priorities.

I have spent the last week porting my code to ESP8266 and I face none of the issues that I posted on this forum regarding guru mediation crashes, intermittent loss of socket connections etc etc etc.

Remember that it takes a long time to develop a good reputation, and very little time to loose it !

:-(

[daniel]

@crankshaft we have seen your issues and we are working on fixing them, but it takes time, the ESP-IDF is in an unstable state which doesn't make things easy.

[crankshaft]

@daniel - someone needs to reply to each issue posted by users, we are not mind readers !

[zmrzli]

This post is deleted!

[stacymarkel]

This post is deleted!