New firmware release 1.2.0.b1

[daniel]

@constantinos I just tested your example, and I even enabled the print statement, but I can't reproduce the crash... (still running for ~10 minutes)

EDIT: OK got the guru meditation error now getting closer to the 11 minutes. We'll investigate. Thanks for the report.

Cheers,
Daniel

[Wembly]

@daniel Thanks for reply, nevermind my comment. It was my bad. Interrupts works !

Edit: however, interrupts will not work if waiting for socket operation (which was the only reason to why I needed them to work). I have added an issue here:
https://github.com/pycom/pycom-micropython/issues/57

[abilio]

@constantinos, thanks again for your report. We found the cause of the issue inside the garbage collector code. We're fixing it right now. It should be fixed for the next firmware release.

[abilio]

@Wembly, thanks for reporting the issue with the sockets, we've tracked it to the GIL (global interpreter lock) not being taken care of inside the sockets code. I've already tested a fix, so it should be included for the next firmware release.

[constantinos]

@abilio I appreciate your effort and your response. I started one week ago having no experience in python but having a lot in Enterprise Infrastructure & Software (Banking & Finance) and offcourse made plenty projects with atmega and ESP8266. Check my pyCom coda library in github

[gertjanvanhethof]

@daniel Can you also give us access to older firmware updates? Sometimes I need that because of breaking updates.

[daniel]

@gertjanvanhethof yes of course. I'll publish links to access the old updates tomorrow. Sorry for the delay.

[livius]

@daniel
can you confirm this on WiPy2?

when i do:
ir = Pin('P13', mode=Pin.IN, pull=None)
or
ir = Pin('P14', mode=Pin.IN, pull=None)

then this is connected to same pin?
P15 is ok
but P13 is same as P14

it looks to me as firmware error

pin P13 not work at all (first on the right bottom) only second one and P13 and P14 are connected to it

[robert-hh]

When do you plan to update the GitHub repository. Due to limited RAM, beaing able to use pre-compiled code is important, and that's what I do with the sources:

I add the line:
#define MICROPY_PERSISTENT_CODE_LOAD (1)
to mpconfigport.h and recompile it. The compiler I use is mpy-cross of that repository. Using mingw32, it can even be built under Windows.

[scratchrobot]

@daniel I run the latest osx updater tool but can not select the country.

[daniel]

@scratchrobot we saw this before and it was happening because you are not connected to the internet while you run the tool, or because your firewall if blocking the connection. The tools needs to connect to download the correct binary for your board.

[daniel]

@robert-hh we will upload them in a couple of hours.

[daniel]

Hello everyone,

The old firmware versions are now published in the Firmware Updates sections of this link:

https://www.pycom.io/support/supportdownloads/

Just scroll down and you'll see the list.

Cheers,
Daniel

[daniel]

@livius it's just a firmware error. The Pins were swapped. Thanks for the report.

[robert-hh]

@Daniel: Got the repository; compiles & runs, with pre-compiled code too. Thanks a lot.

[arneme]

@daniel What does "Update the LoRaWAN stack to Semtech's version 4.3.0" mean. To my knowledge the latest LoRa Alliance LoraWAN specification is on version 1.0.2? Is the version number 4.3.0 related to some internal Semtech ESP stack implementation? The reason I am asking is that we are having troubles with LoPy´s running last firmware update (still investigating) on our LoRaWAN network.

[bmarkus]

@arneme said in New firmware release 1.2.0.b1:

@daniel What does "Update the LoRaWAN stack to Semtech's version 4.3.0" mean.

Probably this

https://stackforce.github.io/LoRaMac-doc/

[daniel]

Probably this
https://stackforce.github.io/LoRaMac-doc/

Yes, that's correct.

@arneme what problems are you experiencing?

[arneme]

@daniel The problems were related to "CRC failures", "FailedAuthentication" and problems with "Packets out of order". We are however not sure if it is a firmware problem or if we have a failing gateway in our network. Moving the devices to a location with a different gateway in reach seems to have solved the problem. We also did a restart of our network server and that could also have solved the problem. I will let you know if we see more errors like this.

[daniel]

@arneme OK thanks for the update. Please let us know when you know more.