<![CDATA[LoPy4 Firmware upgrade impossible]]>No route for firmware upgrade works. Finally PuTTy reveals this during a cmdline test any thoughts pls?
rst:0x10 (RTCWDT_RTC_RESET),boot:0x2b (HSPI_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x2b (HSPI_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x2b (HSPI_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x2b (HSPI_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x3b (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff9010,len:12
ho 0 tail 12 room 4
load:0x3fff9020,len:388
load:0x40078000,len:11584
load:0x4009fb00,len:848
entry 0x4009fc9c
MicroPython v1.8.6-798-gebbcca48-dirty on 2017-10-31; LoPy4 with ESP32
Type "help()" for more information.

]]>https://forum.pycom.io/topic/3265/lopy4-firmware-upgrade-impossibleRSS for NodeSun, 17 May 2026 20:33:37 GMTThu, 17 May 2018 06:15:26 GMT60<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Thu, 17 May 2018 06:15:26 GMT]]>No route for firmware upgrade works. Finally PuTTy reveals this during a cmdline test any thoughts pls?
rst:0x10 (RTCWDT_RTC_RESET),boot:0x2b (HSPI_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x2b (HSPI_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x2b (HSPI_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x2b (HSPI_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x3b (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff9010,len:12
ho 0 tail 12 room 4
load:0x3fff9020,len:388
load:0x40078000,len:11584
load:0x4009fb00,len:848
entry 0x4009fc9c
MicroPython v1.8.6-798-gebbcca48-dirty on 2017-10-31; LoPy4 with ESP32
Type "help()" for more information.

]]>https://forum.pycom.io/post/19711https://forum.pycom.io/post/19711Thu, 17 May 2018 06:15:26 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Thu, 17 May 2018 22:36:48 GMT]]>@dicktonyboy
Can you be more clear please? What do you mean by "No route for firmware upgrade works". What exactly is the error?

Thanks

]]>https://forum.pycom.io/post/19736https://forum.pycom.io/post/19736Thu, 17 May 2018 22:36:48 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Fri, 18 May 2018 06:10:30 GMT]]>@jmarcelino Well, at it's simplest, downloading and running 'pycon_firmware_update_1.14.2.exe' accepting all defaults and knowing the com port is correct AND ensuring the port is available (no other software running) The result is 'Upgrade failed Failed to connect ESP32: Invalid head of packet (\x08)' In all other ways I'm pushing and getting files back and forth and running program happily. 1st expereince with these modules and they are almost simple to use than Arduino.

]]>https://forum.pycom.io/post/19740https://forum.pycom.io/post/19740Fri, 18 May 2018 06:10:30 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Fri, 18 May 2018 18:41:55 GMT]]>@dicktonyboy Did you connect P2 to GND, or use the Expansion board 3?

]]>https://forum.pycom.io/post/19757https://forum.pycom.io/post/19757Fri, 18 May 2018 18:41:55 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Fri, 18 May 2018 18:43:13 GMT]]>@robert-hh P2 to ground

]]>https://forum.pycom.io/post/19758https://forum.pycom.io/post/19758Fri, 18 May 2018 18:43:13 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Fri, 18 May 2018 18:47:57 GMT]]>@dicktonyboy P2 to GND and then push reset. When you do that with Putty open, you should see something like:

ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
waiting for download

I see somtimes the message about invalid packet header, if the update speed is too high. Then I have to use a lower speed, like 460800 baud or even less.

]]>https://forum.pycom.io/post/19759https://forum.pycom.io/post/19759Fri, 18 May 2018 18:47:57 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Fri, 18 May 2018 18:53:46 GMT]]>thats when i get
rst:0x10 (RTCWDT_RTC_RESET),boot:0x2b (HSPI_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x2b (HSPI_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x2b (HSPI_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x2b (HSPI_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x2b (HSPI_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x3b (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff9010,len:12
ho 0 tail 12 room 4
load:0x3fff9020,len:388
load:0x40078000,len:11584
load:0x4009fb00,len:848
entry 0x4009fc9c
MicroPython v1.8.6-798-gebbcca48-dirty on 2017-10-31; LoPy4 with ESP32
Type "help()" for more information.

]]>https://forum.pycom.io/post/19760https://forum.pycom.io/post/19760Fri, 18 May 2018 18:53:46 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Fri, 18 May 2018 19:08:16 GMT]]>@dicktonyboy Then the device is NOT in update state. You have to see the message "waiting for download". That turns up when P2 is connected to GND during Reset (push the reset button on the module or pull reset pin low for a short moment.
Edit: Reset is not P0, but the one next to P0

]]>https://forum.pycom.io/post/19761https://forum.pycom.io/post/19761Fri, 18 May 2018 19:08:16 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Fri, 18 May 2018 19:08:32 GMT]]>Now I am confused. Is this sequence described fully anywhere so that I may follow it pls?

]]>https://forum.pycom.io/post/19762https://forum.pycom.io/post/19762Fri, 18 May 2018 19:08:32 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Fri, 18 May 2018 19:25:01 GMT]]>@dicktonyboy to some extend it is here:
https://docs.pycom.io/chapter/gettingstarted/installation/firmwaretool.html
In step 4, it says: reconnect
That is equivalent to being connected and pushing reset. My experience is, that reconnecting not always brings the device into proper dowload mode, put pushing reset does.
Did it work now?

]]>https://forum.pycom.io/post/19763https://forum.pycom.io/post/19763Fri, 18 May 2018 19:25:01 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Fri, 18 May 2018 19:31:57 GMT]]>@robert-hh Wow your support is faster than I'm allowed to rely (limit 600s). I'm not using a expansion board but this set up https://github.com/keptenkurk/pyTTNmap/blob/master/documentation/Schematics.jpg . I need a few moments to clear my desk (Thanks for this great response btw )

]]>https://forum.pycom.io/post/19764https://forum.pycom.io/post/19764Fri, 18 May 2018 19:31:57 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Fri, 18 May 2018 19:42:51 GMT]]>No - this is where we came in. Note that I cant have Putty and the firmware updater program both running on Com7 simultaneously. Just running the updater produces the failure originally reported.

]]>https://forum.pycom.io/post/19765https://forum.pycom.io/post/19765Fri, 18 May 2018 19:42:51 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Fri, 18 May 2018 19:50:32 GMT]]>@dicktonyboy Sure. Putty is just for confirming for being in the update state. Then you must close putty and start the updater.

]]>https://forum.pycom.io/post/19766https://forum.pycom.io/post/19766Fri, 18 May 2018 19:50:32 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Fri, 18 May 2018 20:23:07 GMT]]>@robert-hh grand kids have arrived - must play grandpa for a moment -will get back to you with the results Thanks for all of your help.

]]>https://forum.pycom.io/post/19767https://forum.pycom.io/post/19767Fri, 18 May 2018 20:23:07 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Sun, 20 May 2018 20:10:48 GMT]]>This board will NOT flash. Even trying lower speeds it does not correctly switch modes. The blue heartbeat led stops as it should when the pin is grounded but nothing more.

]]>https://forum.pycom.io/post/19784https://forum.pycom.io/post/19784Sun, 20 May 2018 20:10:48 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Sun, 20 May 2018 20:14:28 GMT]]>@dicktonyboy So did you see the message "waiting for download" in Putty, if you do the download preparation steps, or not?

]]>https://forum.pycom.io/post/19785https://forum.pycom.io/post/19785Sun, 20 May 2018 20:14:28 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Sun, 20 May 2018 20:35:08 GMT]]>@robert-hh No just the original message I posted - repeated several times and can you remove this annoying restriction that pops up each time I reply please

Error

As a new user, you can only post once every 600 second(s) until you have earned 3 reputation - please wait before posting again
.

]]>https://forum.pycom.io/post/19786https://forum.pycom.io/post/19786Sun, 20 May 2018 20:35:08 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Sun, 20 May 2018 20:58:58 GMT]]>@dicktonyboy If you do not see the message, then something may be wrong with P2 aka GPIO0. The sequence of messages you see is also strange.

Remark. I gave you 3 reputations. So the delay should be gone.

]]>https://forum.pycom.io/post/19787https://forum.pycom.io/post/19787Sun, 20 May 2018 20:58:58 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Sun, 20 May 2018 21:05:01 GMT]]>@robert-hh Well this is very weird as to all intents and purposes everything else is functioning correctly. I am new to this - and this is my first LoPy project. I'm running TTN Cardiff and wanted to provide the locals with a signal strength mapping project. https://youtu.be/-H-W76OMkyY?t=16s I feel so much cleaner with my new-found reputation - thank you for that!

]]>https://forum.pycom.io/post/19788https://forum.pycom.io/post/19788Sun, 20 May 2018 21:05:01 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Sun, 20 May 2018 21:13:10 GMT]]>@robert-hh I've no ideaa whether this is of an help but the response to:-

C:\Users\dicktonyboy>ampy -p com7 ls
flash

and the response to:-
C:\Users\dicktonyboy>ampy -p com7 ls /flash
main.py
sys
lib
cert
boot.py
Location History.json
AdafruitIO.py
filer
umqtt.py
project.pymakr
lopylcd.mpy
micropygps.mpy
micropygps.py

I can't delete the bottom three files or Location History.json (probably due to the space in the name)

]]>https://forum.pycom.io/post/19789https://forum.pycom.io/post/19789Sun, 20 May 2018 21:13:10 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Mon, 21 May 2018 06:10:45 GMT]]>@dicktonyboy If you have the REPL prompt, you can always reformat the internal file system with uos.mkfs().
But updating requires the device to be in upload mode. Sorry if I'm asking the obvious again, but are you sure that you connected P2 to GND. That's the 4th Pin from the edge close to the reset button, next to TX. Strapping it low sometime causes the RGB LED to switch colors.

]]>https://forum.pycom.io/post/19792https://forum.pycom.io/post/19792Mon, 21 May 2018 06:10:45 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Mon, 21 May 2018 07:16:15 GMT]]>@robert-hh double and triple checked - correct. :)

]]>https://forum.pycom.io/post/19793https://forum.pycom.io/post/19793Mon, 21 May 2018 07:16:15 GMT<![CDATA[Reply to LoPy4 Firmware upgrade impossible on Mon, 21 May 2018 08:19:51 GMT]]>@dicktonyboy You could check, whether P2 is connected at least to the RGB Led. It is one of the connections faced to the LoPy Shield, opposite to P2.
0_1526890777128_lopy.jpg

]]>https://forum.pycom.io/post/19794https://forum.pycom.io/post/19794Mon, 21 May 2018 08:19:51 GMT