New Release Candidate 1.20.2.rc11 for Pygate

[d.alvrzx]

@andrew-parry This didn't happen to me upon update... Is the Pygate listed in the Device Manager (assuming you're on Windows) as COMX? You could also attempt to use the firmware updater CLI tool and list all available devices by running:

pycom-fwtool-cli.exe list

If something like COM4 [USB Serial Device (COM4)] [USB VID:PID=04D8:ED14 SER=PY4A2F7B LOCATION=1-3] comes up, you could then try a full erase via:

pycom-fwtool-cli.exe -p COM4 erase_all

And then attempt to upload the firmware again. Haven't tested this on Pygate, but this worked for me when sometimes updating the firmware on my LoPy4 caused issues.

[jcaron]

@andrew-parry This page states:

If PIC stays in bootloader mode, the dfu-util update should be performed

@Gijs Of course the link is broken, it probably meant to link to this page. Of course, no idea what is meant by "update" since there is no such command in dfu-util (at least the version I have here) and there is no published firmware for the Pygate. But dfu-util -l should at least be informative.

pycom-fwtool-cli can trigger moving the **Py to/from firmware upgrade mode. Just issue a command to read anything and it should get out of firmware upgrade mode when it exits.

[andrew.parry]

@d-alvrzx Yes I'll give it a try I'm using a lopy4 with the pygate, The Firmware update tool works fine, I've re-loaded the firmware multiple times without issue but still can't connect with Atom. I'm going to try reverting the Firmware to the previous version and see if that helps.

[serafimsaudade]

Hi,
I'm testing this release and when I try to set the RTC it don't update.

>>> from machine import RTC
>>> rtc = RTC()
>>> rtc.now()
(1970, 1, 1, 0, 5, 16, 423776, None)
>>> rtc.init((2014, 5, 1, 4, 13, 0, 0, 0))
>>> rtc.now()
(1970, 1, 1, 0, 6, 38, 714800, None)

This code works on all previous releases.

[peterp]

@serafimsaudade said in New Release Candidate 1.20.2.rc11 for Pygate:

Hi,
I'm testing this release and when I try to set the RTC it don't update.

>>> from machine import RTC
>>> rtc = RTC()
>>> rtc.now()
(1970, 1, 1, 0, 5, 16, 423776, None)
>>> rtc.init((2014, 5, 1, 4, 13, 0, 0, 0))
>>> rtc.now()
(1970, 1, 1, 0, 6, 38, 714800, None)

This code works on all previous releases.

Indeed I can reproduce the problem that init() does not set the rtc. Thanks for flagging! Now that I checked this, also the two previous pygate releases did not set the rtc from init(). The latest pybytes firmware does set it correctly for me.

Just to gauge the severity - do you actually need to set it to 2014? rtc.ntp_sync() seems to work ok, for me in all three pygate releases rc9, rc10, rc11 and latest stable 1.20.2.rc0.

[serafimsaudade]

I'm testing on wipy, gpy, fipy and lopy4.
The 2014 is a example only for show the bug.
I need to set the rtc manualy. Because my devices connect to the internet over modem3G and request the date and time over API, i don't use wifi.

[peterp]

@serafimsaudade said in New Release Candidate 1.20.2.rc11 for Pygate:

I'm testing on wipy, gpy, fipy and lopy4.

There is no pygate FW release for the FiPy! Are you looking for the Pygate firmware or the "normal" Pybytes one?

If you are indeed looking for the pygate firmware, could you then double check for me whether init() does actually work for you in pygate 1.20.2.rc10 and rc9?

The 2014 is a example only for show the bug.
I need to set the rtc manualy. Because my devices connect to the internet over modem3G and request the date and time over API, i don't use wifi.

ntp_sync is not restricted to wifi. It should work just as well over LTE.

[serafimsaudade]

Sry I maybe was not explicit. English e not my native language.
I don't have a pygate.
This Fw release 1.20.2.rc11 is only for the pygate? I can use it on other products (wipy, gpy, fipy, lopy4)?
I'm running custom frozen code, I compile fw from source code.
My devices are custom hardware with pycom cpu's, and all have thirdparty modem 2G/3G/4G.
I don't use NB-IOT/LTE Cat1, because the mobile cover are not good enough.

[peterp]

@serafimsaudade Ah, ok. Now I understand. From a build-from-source perspective, pygate and base/pybytes are now all merged together in the same branch. The differences are:

• latest pygate fw is built from latest public commit in Dev branch with make VARIANT=PYGATE
• latest pybytes fw is built from an earlier commit (783192e) using make VARIANT=PYBYTES. speaking simplified this is before/without any of the pygate code.
• for base variant we don't publish prebuilt binaries any more, but this might be what you build yourself.

Do you mind telling me how you build? That would help narrow down the rtc.init() issue.

For the time being you could try reverting to the tag for the stable release v1.20.2.r0. Let me know whether that works for you.

[serafimsaudade]

yes the v1.20.2.r0, rc9, rc10 are ok.

Build the FW:

make ESPPORT=/dev/ttyUSB0 BOARD=WIPY FS=LFS flash

[peterp]

@serafimsaudade said in New Release Candidate 1.20.2.rc11 for Pygate:

yes the v1.20.2.r0, rc9, rc10 are ok.

well, ok. I get it now - you're building from source, so we were talking past each other here. When you say rc9 (or10) you refer to the git tag v1.20.2.rc9 which means pybytes, while I was talking about the binary release of the pygate firmware. Those are not the same thing

Build the FW:

make ESPPORT=/dev/ttyUSB0 BOARD=WIPY FS=LFS flash

understood. thanks!

[serafimsaudade]

@peterp
Ahh ok. :). I thought it was implied, that I was talking about the git repository. Sry.

Best regards,

[Roy k carroll]

@serafimsaudade said in New Release Candidate 1.20.2.rc11 for Pygate:

yes the v1.20.2.r0, rc9, rc10 are ok.

[Jean Ferreira]

@peterp This is a problem for me as well - I set my G01 RTC from a another RTC chip on our OEM board.

[mikestanley464]

@mikestanley464 said in New Release Candidate 1.20.2.rc11 for Pygate: VidMate | Vidmate for pc | Canli macizle

thanks for it.

No reply?

[mikestanley464]

@mikestanley464 said in New Release Candidate 1.20.2.rc11 for Pygate:

thanks for it.

no reply. .?

[robert-hh]

@mikestanley464 Pycom Ltd. ceased operation. There will not be a reply.