@rskoniec said in New Firmware release v1.18.1.r1: @mfa2214 xPy module f/w and GPy/Fipy modem f/w are separate, so GPy/Fipy module f/w doesn't contain modem f/w. Here http://stiny.webd.pl/PYCOM/ on my VPS you have collection of CATM1/NB1 *.dup files. FiPy-1.18.1.r1 GPy-1.18.1.r1 Many thanks @rskoniec for sharing the files :)

Hi @terryz, This is not a bug, the firmware updater works as expected, your antivirus software has an issue. Someone else had an issue similar to this, in that case the reason was that the firmware updater connects to the internet and that's considered "suspicious" for some anti-virus applications. If you add it to the exception list, you can continue using it.

@jirkakrepl Thanks. I had worked this out.

@robert-hh A further look revealed, that both the LOPY4 and FIPY image are below 1536k. Only if I add one of the IN865 or EU433 regions AND my favorite frozen scripts, the FIPY build exceed 1536k. Still some slimming is advised, or more room in the partition table.

@robert-hh Because we only changed 3 lines of code and released only versions for GPy and FiPy. That didn't seem to warrant anything more than updating the release tag. In case you are wondering, 1.18.0 is considered a short form of 1.18.0.r0 as we consider r0 the default unless otherwise specified. From a viewpoint of our internal versioning algorithm, we have 4 different types of versions: 1.18.0. a0 is an alpha version (only used internally), b0 is a beta (up until 1.18.0 everything was released as a beta even though the firmware updater treats them as stable), rc0 (release candidate, we never used this so far but we have the option for it) and r0 as stable release.

@jadowdl You do not need an expansion board. Almost any USB/UART bridge and a few cables will do. You just have ot take care that the USB/UART bridge can supply 5V while the UART signals are at 3.3v. If you already have a REPL prompt through USB, then you are almost set. The only additional step for upload is to connect P2 to GND and pzsh reset. About Pin numbers, look here:https://docs.pycom.io/chapter/datasheets/development/gpy.html

@brady-aiello For the old expansion board you do not need the DFU drivers, as it uses an FTDI or similar USB/Serial bridge. it should work out-of-the-box. If you installed drivers according to the instructions you cited, remove them. See also the instructions here https://docs.pycom.io/chapter/gettingstarted/installation/firmwaretool.html#first in the expansion board 2 tab. Some people had trouble with Windows and the V2.x expansion board, and there is a lot of discussion around it in the board, which sometimes is more confusing than helpful. As result of that, the instructions in the manual were updated. b.t.w.: I prefer the V2 expansion board. Updating with the expansion board V3 or the pyxxxx board seems inconvenient, as it requires unplugging and replugging the board with a tight timing and reconfiguration of each OS.

Just a quick note to say there will be no new development release this weekend.

@colateral It's in the development branch.

@charly86 said in New firmware release v1.18.0: cardgenerator @iwahdan Nice, but that's not my PR so I don't want to get any credit for it ;-) Are you still facing this issue? @charly86 said in New firmware release v1.18.0: @iwahdan Nice, but that's not my PR so I don't want to get any credit for it ;-)

@grantosw Glad I could help. ;o)

@jmarcelino do you already searching for a solution or have found it ???? I have the same problem

That worked perfectly. Thanks, Zac

Hi A roadmap would be highly appreciated, even if dates can not be set in detail it would be nice if there where som sort of roadmap with what features that can be expected in the next few releases. This could also be a way to get input on the priority of what goes into each release. At the same time it gives some indication on what features we can expect and thus do some planning accordingly by finding workaround solution or adjust the features of the product depending on the the pycom modules.