LoPy4 Firmware upgrade impossible

dicktonyboy

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: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.

robert-hh

@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.

dicktonyboy

@robert-hh double and triple checked - correct. :)

robert-hh

@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.

dicktonyboy

@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)

dicktonyboy

@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!

robert-hh

@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.

dicktonyboy

@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
.

robert-hh

@dicktonyboy So did you see the message "waiting for download" in Putty, if you do the download preparation steps, or not?

dicktonyboy

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.

dicktonyboy

@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.

robert-hh

@dicktonyboy Sure. Putty is just for confirming for being in the update state. Then you must close putty and start the updater.

dicktonyboy

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.

dicktonyboy

@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 )

robert-hh

@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?

dicktonyboy

Now I am confused. Is this sequence described fully anywhere so that I may follow it pls?

robert-hh

@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

dicktonyboy

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: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.

robert-hh

@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.

dicktonyboy

@robert-hh P2 to ground

Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

LoPy4 Firmware upgrade impossible

Pycom on Twitter