New Firmware Release 1.20.2.rc3

[Xykon]

A new firmware release 1.20.2.rc2 1.20.2.rc3 is now available. Even though this is marked as a release candidate, we think it's significantly more stable than the previous release which is why it's available in the standard pybytes category. Furthermore we have added a flag to disable the built-in pybytes code.

import pycom
pycom.pybytes_on_boot(False)

A new firmware updater will be released shortly that will allow setting this during the upgrade.

The full release notes can be found here: https://github.com/pycom/pycom-micropython-sigfox/releases/tag/v1.20.2.rc2 and and the elf files for rc3 here: https://github.com/pycom/pycom-micropython-sigfox/releases/tag/v1.20.2.rc3

[robert-hh]

@Xykon Thanks.

[Xykon]

You can temporarily use the links below to download Pybytes firmware files.

• WiPy
• LoPy
• SiPy
• GPy
• FiPy
• LoPy4

[robert-hh]

@peterp I guess, what people are missing are the tarballs of the most recent firmware packages, like the ones placed in here: https://software.pycom.io/downloads/FiPy etc.. That was promised once, and worked for a short time.
That can be used for scripted device update, which is preferable if you update more than one device. Obviously, elf-files contain everything and can be used together with esptool.py and the build scripts to create such a tarball. But having the "official" tarballs available is preferred.
I'm not arguing against the elf files. If you want to debug the firmware, they are needed. But most people don't do that. They expect Pycom to do it.

[peterp]

@securigy said in New Firmware Release 1.20.2.rc3:

@Xykon Why everything is always so complicated? What are .elf files? Is that just for pros?
Why can't it be just one file as before that you load into Firmware upgrade tool?

@securigy Let's take a step back. I don't think it actually is complicated. If you use Firmware upgrade tool, you should get 1.20.2.rc3. Please try (again).

[securigy]

@Xykon Why everything is always so complicated? What are .elf files? Is that just for pros?
Why can't it be just one file as before that you load into Firmware upgrade tool?

[kjm]

@Xykon I'm familiar with updater.elf but not application.elf Can someone please like me to some docs that explain how to use application.elf for debugging pls?

[Xykon]

@robert-hh said in New Firmware Release 1.20.2.rc3:

@Xykon @iwahdan just published v1.20.0.rc13. That is confusing. What is the relation between v1.20.2rc3 and v1.20.0rc13?

It was an old draft that hadn't been published before. We considered deleting it but for consistency we just decided to publish that release in case anyone still needs the elf files for debugging.

[robert-hh]

@Xykon @iwahdan just published v1.20.0.rc13. That is confusing. What is the relation between v1.20.2rc3 and v1.20.0rc13?

[peterp]

1.20.2.rc3 has just been released and rc2 has been removed. Please update

[robert-hh]

@Xykon Thanks. I confirm it's fixed.

Edit: The pybytes_on_boot() function is not exposed unless you build the pybytes variant.

I've seen that, and it's consistent.

[Xykon]

@robert-hh said in New Firmware Release 1.20.2.rc2:

@Xykon If built without pybytes, there is no pybytes_on_boot() method in the modukle pycom, but an error message comes up:
could not find module '_main_pybytes.py'
That was already mentioned before. It looks like the trouble is here:

        if (config_get_pybytes_autostart()) {
            pyexec_frozen_module("_main_pybytes.py");
        } else {
            pyexec_frozen_module("_main.py");
        }

config_get_pybytes_autostart() seems to return True, even if it was never enabled. And since the method pybytes_on_boot() does not exist, it cannot be disabled,

An update will be available shortly (1.20.2.rc3) which fixes that. It's already on GitHub in the Dev branch.

Edit: The pybytes_on_boot() function is not exposed unless you build the pybytes variant.

[jcaron]

@Xykon Can you please make sure that docs are updated, and where necessary, that they mention in which version things changed? E.g. the BLE callback.

[robert-hh]

@Xykon If built without pybytes, there is no pybytes_on_boot() method in the modukle pycom, but an error message comes up:
could not find module '_main_pybytes.py'
That was already mentioned before. It looks like the trouble is here:

        if (config_get_pybytes_autostart()) {
            pyexec_frozen_module("_main_pybytes.py");
        } else {
            pyexec_frozen_module("_main.py");
        }

config_get_pybytes_autostart() seems to return True, even if it was never enabled. And since the method pybytes_on_boot() does not exist, it cannot be disabled,