New firmware release 1.2.0.b1

[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.

[livius]

i try to use pin callback
but how to check what cause callback?
e.g.:

p_in.callback(Pin.IRQ_FALLING | Pin.IRQ_RISING, pin_handler)
def pin_handler(arg):
    if need to know if raising:
        something when rising
    else:
       something when falling

chow to check in callback that it is executed because
a) IRQ_FALLING
b) IRQ_RISING
?

[daniel]

@livius good question, we are implementing that feature as we speak ;-)

[daniel]

@livius in the meantime, you can check the pin value inside the callback. If the pin is low, then most likely it was due to a falling edge, otherwise it was a rising edge.

[arneme]

@daniel We have now several LoPys up and running on our LoRaWAN network with version 1.2.0.b1 and they all behave as they should. The problem must have been with our infrastructure at the location we tested during the weekend.

[daniel]

@arneme great to hear that, thanks for the feedback :-)