LoPy died after update
-
@littlebat I tried (based on your advice), but still it failed to update.
So I put the jumper wire in place, connected with minicom, did the reset, the message 'waiting for download..' was shown, closed the terminal and run the firmware update: failed.
Other suggestions?
Thxs for you help! (also thxs to all others!).
-
@gertjanvanhethof Please see my reply from 2 minutes ago, with instructions to run the script manually.
-
@daniel said in LoPy died after update:
python updater.py -f ../firmware/lopy_0.9.2.b2_868.bin -p /dev/ttyUSB0
This is the output:
python updater.py -f ../firmware/lopy_0.9.2.b2_868.bin -p /dev/ttyUSB0
Namespace(file='../firmware/lopy_0.9.2.b2_868.bin', port='/dev/ttyUSB0')
Connecting...
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 115200
Changed.
Erasing flash...
Compressed 4096 bytes to 2891...
Wrote 4096 bytes (2891 compressed) at 0x00001000 in 0.3 seconds (effective 127.0 kbit/s)...
Hash of data verified.
Erasing flash...
Compressed 256 bytes to 125...
Wrote 256 bytes (125 compressed) at 0x00004000 in 0.0 seconds (effective 129.9 kbit/s)...
Hash of data verified.
Erasing flash...
Compressed 639008 bytes to 385542...
Wrote 639008 bytes (385542 compressed) at 0x00010000 in 33.9 seconds (effective 150.7 kbit/s)...
Hash of data verified.Leaving...
Verifying just-written flash...
Verifying 0x1000 (4096) bytes @ 0x00001000 in flash against /home/gertjan/Downloads/pyupgrade/bin/../firmware/bootloader.bin...
-- verify OK (digest matched)
Verifying 0x100 (256) bytes @ 0x00004000 in flash against /home/gertjan/Downloads/pyupgrade/bin/../firmware/partitions.bin...
-- verify OK (digest matched)
Verifying 0x9c020 (639008) bytes @ 0x00010000 in flash against ../firmware/lopy_0.9.2.b2_868.bin...
-- verify OK (digest matched)This worked! THXS for your splendid help!!!
-
Your are welcome. We'll sort this issue with the UI asap. Thanks for everyone's help.
Cheers,
Daniel -
Same here, only with Window 10 updater procede on friday.
LoPi module dead! No blinky, no output on PUTTY after reset with G23 connected to GND.
No juice with boot mode change, Dead, dead, dead.
Manual updater procedure today (sunday)
C:\Program Files (x86)\Pycom\Pycom Firmware Update\Upgrader>..\Python27\python.exe bin\updater.py --port COM4 --file firmware\lopy_0.9.2.b2_868.bin
Namespace(file='firmware\lopy_0.9.2.b2_868.bin', port='COM4')
Connecting...
Exception: Failed to connect to ESP32: Timed out waiting for packet header, on line 75 -
@Baruch1966 said in LoPy died after update:
Exception: Failed to connect to ESP32: Timed out waiting for packet header, on line 75
This usually happens if your LoPy / WiPy 2 isn't in ROM bootloader mode.
Please check that you have connected GND and G23 on the expansion board (P2 on the module itself).
If it still doesn't work please check that your COM port is correct (check COM ports in device manager).
What do you see in a serial terminal when you press the reset switch on the module when G23 / P2 is connected to GND?
-
@Xykon Did G23-GND connection, serial/USB is working, other LoPi works, no output with PUTTY @115200
-
When you press the reset button on the LoPy while GND is connected to G23 you should see the following in the serial terminal:
rst:0x1 (POWERON_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2)) waiting for downloadYou mention having two LoPy. Do you use the same expansion board each time?
Do you get the waiting for download message on the other LoPy when GND is connected to G23 and reset button is pressed?
If you get this on one LoPy but not the other and they both use the same expansion board, USB cable etc. then it's most likely one of your LoPy is broken. The waiting for download message is from the ROM bootloader in the chip itself which you can't accidentally modify/erase.
-
@Xykon said in LoPy died after update:
When you press the reset button on the LoPy while GND is connected to G23 you should see the following in the serial terminal:
rst:0x1 (POWERON_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2)) waiting for downloadYou mention having two LoPy. Do you use the same expansion board each time?
Do you get the waiting for download message on the other LoPy when GND is connected to G23 and reset button is pressed?
If you get this on one LoPy but not the other and they both use the same expansion board, USB cable etc. then it's most likely one of your LoPy is broken. The waiting for download message is from the ROM bootloader in the chip itself which you can't accidentally modify/erase.
No output with the faulty one. Output with the good one. What can I do now?
-
I'd suggest you email support@pycom.io to ask for an RMA. However I don't work for Pycom so I'm not sure about their official processes.
-
@Xykon Thxs for you help on this.
The given answer do 'python updater.py -f ../firmware/lopy_0.9.2.b2_868.bin -p /dev/ttyUSB0' (after it is set to 'Waiting for download') solved my issue.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login