New firmware release v1.11.0.b1 and new updater tool version v1.1.4.b1 (FiPy and GPy support)

[seb]

@robert-hh said in New firmware release v1.11.0.b1 and new updater tool version v1.1.4.b1 (FiPy and GPy support):

@daniel said in New firmware release v1.11.0.b1 and new updater tool version v1.1.4.b1 (FiPy and GPy support):

P12 is also the safeboot pin and the antenna select pin in the WiPy3, LoPy4, GPy and FiPy

If you look into the Pin-out diagrams, there is still a mess about that topic.

Hi,
I just looked over all of the pinouts, only the LoPy4 remained to fixed and has now been resolved. The pinouts now all accurately reflect where each module has its antenna select. I will soon be improving the documentation around the other issue you raised with safe boot.

[robert-hh]

@seb Thanks, and in case we do not talk again: Merry Christmas

[dbrgn]

@seb said in New firmware release v1.11.0.b1 and new updater tool version v1.1.4.b1 (FiPy and GPy support):

@dbrgn

You would only need to change the way you instantiate the SPI class to use the old pin layout, you can find an example of this here: https://docs.pycom.io/chapter/firmwareapi/pycom/machine/SPI.html
No need to recompile the whole firmware. The reason this has been changed is because on new devices P12 controls the external WiFi antenna switch and therefor should not be used for SPI. The pinout diagrams will soon be updated to reflect these changes.

Ah, thank you for clarification, that helps :)

@livius said:

It is good practice that if you have default configuration which can by changed by params,
to specify default params also.

Yep, I agree :) I was under the impression that this mapping is something that is done in the ESP32 firmware, not in the "MicroPython userspace", which would have been a bit more complicated in my case.

[tcottle]

@daniel Updater tool does not work on Win7(!) No indication of Win10 requirement in the docs and the installer does not catch this error.

[daniel]

@tcottle it should work on Win7 as well. What errors do you get?

[tcottle]

@daniel I never got an executable. The installer created and populated python 2.7 and installer directories and then quit. After several install and uninstall cycles I tried it on Win10 machine and everything worked fine

[daniel]

@tcottle thanks for this bug report. We well do some more testing as in principle it works fine on our Win7 test machines.

[incognico]

I used this on Win7 (64) with no issues.

Installer put a link to the executable in my start menu.

[Xykon]

@tcottle We have tested the firmware update tool on Windows 7 multiple times and never encountered any issues.

Could you please provide the type (32/64bit) of your Windows 7 installation.

Did the installer create the Icon for the firmware update tool in the start menu?

Did you get any error message when trying to launch the tool from the start menu?

I'm working on a new firmware update tool that will work with a single executable file but until this is ready I would like to make sure the current version doesn't have any issues.

Thanks a lot for your assistance.

[tcottle]

@xykon Running Win7 Pro SP1 64 bit. The installer seemed to run OK but I definitely didn't get an icon. Uninstalled and reinstalled multiple times (even tried "Run as Administrator") This machine rarely gets rebooted but it did get a reboot since my original e-mail. Today when I reinstalled the firmware tool now get a start menu icon(!) Go figure ...

[Smeedy]

@daniel any news on Sigfox for the 1.11 on FiPy?

[daniel]

@Smeedy it will be available in a new release today or tomorrow.