RTK Facet GPS-19029 boot loop after firmware update

Hello,

after firmware update to my RTK Facet GPS-19029 I’m in a boot loop. I have only used the pre-compiled binary for the project website. The output on teraterm is following in a loop:

rst:0x3 (SW_RESET),boot:0x13 (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:1
load:0x3fff0030,len:1240
load:0x40078000,len:13012
load:0x40080400,len:3648
entry 0x400805f8
ets Jul 29 2019 12:21:46

I know this is indicating that the firmware is defect. Therefore I have tried to upload different firmware versions over the GUI updater. I receive always a good log from the GUI firmware updater but still stucked in the boot loop.

Detecting flash size
______________________________________________________________________
ESP32 Flash Size Detection
Command: [‘–chip’, ‘esp32’, ‘–port’, ‘\\.\COM4’, ‘–baud’, ‘115200’, ‘–before’, ‘default_reset’, ‘–after’, ‘no_reset’, ‘flash_id’]
esptool.py v4.7.0
Serial port \.\COM4
Connecting…
Device PID identification is only supported on COM and /dev/ serial ports.
.
Chip is ESP32-D0WD-V3 (revision v3.0)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 30:c6:f7:41:4e:34
Uploading stub…
Running stub…
Stub running…
Manufacturer: 20
Device: 4018
Detected flash size: 16MB
Staying in bootloader.
Flash detection complete. Uploading firmware…
Flash size is 16MB
Uploading firmware
______________________________________________________________________
ESP32 Firmware Upload
Command: [‘–chip’, ‘esp32’, ‘–port’, ‘\\.\COM4’, ‘–baud’, ‘115200’, ‘–before’, ‘default_reset’, ‘–after’, ‘no_reset’, ‘write_flash’, ‘-z’, ‘–flash_mode’, ‘dio’, ‘–flash_freq’, ‘80m’, ‘–flash_size’, ‘detect’, ‘0x1000’, ‘C:\Users\optos\AppData\Local\Temp\_MEI247682\resource\RTK_Surveyor.ino.bootloader.bin’, ‘0x8000’, ‘C:\Users\optos\AppData\Local\Temp\_MEI247682\resource\RTK_Surveyor_Partitions_16MB.bin’, ‘0xe000’, ‘C:\Users\optos\AppData\Local\Temp\_MEI247682\resource\boot_app0.bin’, ‘0x10000’, ‘C:/Users/optos/Documents/RTKFacet/RTK_Surveyor_Firmware_v4_0.bin’]
esptool.py v4.7.0
Serial port \.\COM4
Connecting…
Device PID identification is only supported on COM and /dev/ serial ports.
.
Chip is ESP32-D0WD-V3 (revision v3.0)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 30:c6:f7:41:4e:34
Uploading stub…
Running stub…
Stub running…
Configuring flash size…
Auto-detected Flash size: 16MB
Flash will be erased from 0x00001000 to 0x00005fff…
Flash will be erased from 0x00008000 to 0x00008fff…
Flash will be erased from 0x0000e000 to 0x0000ffff…
Flash will be erased from 0x00010000 to 0x00011fff…
Flash params set to 0x024f
Compressed 17984 bytes to 12318…
Writing at 0x00001000… (100 %)
Wrote 17984 bytes (12318 compressed) at 0x00001000 in 1.3 seconds (effective 106.7 kbit/s)…
Hash of data verified.
Compressed 3072 bytes to 129…
Writing at 0x00008000… (100 %)
Wrote 3072 bytes (129 compressed) at 0x00008000 in 0.1 seconds (effective 389.2 kbit/s)…
Hash of data verified.
Compressed 8192 bytes to 47…
Writing at 0x0000e000… (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 643.1 kbit/s)…
Hash of data verified.
Compressed 5264 bytes to 1880…
Writing at 0x00010000… (100 %)
Wrote 5264 bytes (1880 compressed) at 0x00010000 in 0.3 seconds (effective 156.3 kbit/s)…
Hash of data verified.
Leaving…
Staying in bootloader.
Firmware upload complete. Resetting ESP32…
Resetting ESP32
______________________________________________________________________
ESP32 Reset
Command: [‘–chip’, ‘esp32’, ‘–port’, ‘\\.\COM4’, ‘–before’, ‘default_reset’, ‘run’]
esptool.py v4.7.0
Serial port \.\COM4
Connecting…
Device PID identification is only supported on COM and /dev/ serial ports.
.
Chip is ESP32-D0WD-V3 (revision v3.0)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 30:c6:f7:41:4e:34
Uploading stub…
Running stub…
Stub running…
Hard resetting via RTS pin…
Reset complete…

What could be the issue here and how could it be solved ?

Thanks

Hi,

Please try downloading the firmware binary again. The “Compressed 5264 bytes to 1880… Writing at 0x00010000… (100 %)” is very suspicious… It is much too small.

I hope this helps,

Paul

You were correct the firmware bin file wasn’t downloaded correctly. I have now fixed this issue and have a file size for the 4.0 firmware version of 2,16 MB (2.275.472 Bytes).

I have tried it update the firmware also with different firmware versions but still I got the boot loop. Please see output of teraterm and GUI firmware updater (used version 1.6 and also tried version 1.5.2)

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (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:1
load:0x3fff0030,len:1240
load:0x07800000,len:3331136
ets Jul 29 2019 12:21:46
Detecting flash size
______________________________________________________________________
ESP32 Flash Size Detection
Command: [‘–chip’, ‘esp32’, ‘–port’, ‘\\.\COM4’, ‘–baud’, ‘921600’, ‘–before’, ‘default_reset’, ‘–after’, ‘no_reset’, ‘flash_id’]
esptool.py v4.7.0
Serial port \.\COM4
Connecting…
Device PID identification is only supported on COM and /dev/ serial ports.

Chip is ESP32-D0WD-V3 (revision v3.0)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 30:c6:f7:41:4e:34
Uploading stub…
Running stub…
Stub running…
Changing baud rate to 921600
Changed.
Manufacturer: 20
Device: 4018
Detected flash size: 16MB
Staying in bootloader.
Flash detection complete. Uploading firmware…
Flash size is 16MB
Uploading firmware
______________________________________________________________________
ESP32 Firmware Upload
Command: [‘–chip’, ‘esp32’, ‘–port’, ‘\\.\COM4’, ‘–baud’, ‘921600’, ‘–before’, ‘default_reset’, ‘–after’, ‘no_reset’, ‘write_flash’, ‘-z’, ‘–flash_mode’, ‘dio’, ‘–flash_freq’, ‘80m’, ‘–flash_size’, ‘detect’, ‘0x1000’, ‘C:\Users\optos\AppData\Local\Temp\_MEI253602\resource\RTK_Surveyor.ino.bootloader.bin’, ‘0x8000’, ‘C:\Users\optos\AppData\Local\Temp\_MEI253602\resource\RTK_Surveyor_Partitions_16MB.bin’, ‘0xe000’, ‘C:\Users\optos\AppData\Local\Temp\_MEI253602\resource\boot_app0.bin’, ‘0x10000’, ‘C:/Users/optos/Documents/RTKFacet/RTK_Surveyor_Firmware_v4_0.bin’]
esptool.py v4.7.0
Serial port \.\COM4
Connecting…
Device PID identification is only supported on COM and /dev/ serial ports.

Chip is ESP32-D0WD-V3 (revision v3.0)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 30:c6:f7:41:4e:34
Uploading stub…
Running stub…
Stub running…
Changing baud rate to 921600
Changed.
Configuring flash size…
Auto-detected Flash size: 16MB
Flash will be erased from 0x00001000 to 0x00005fff…
Flash will be erased from 0x00008000 to 0x00008fff…
Flash will be erased from 0x0000e000 to 0x0000ffff…
Flash will be erased from 0x00010000 to 0x0023bfff…
Flash params set to 0x024f
Compressed 17984 bytes to 12318…
Writing at 0x00001000… (100 %)
Wrote 17984 bytes (12318 compressed) at 0x00001000 in 0.4 seconds (effective 342.2 kbit/s)…
Hash of data verified.
Compressed 3072 bytes to 129…
Writing at 0x00008000… (100 %)
Wrote 3072 bytes (129 compressed) at 0x00008000 in 0.1 seconds (effective 485.4 kbit/s)…
Hash of data verified.
Compressed 8192 bytes to 47…
Writing at 0x0000e000… (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 674.4 kbit/s)…
Hash of data verified.
Compressed 2275472 bytes to 1497673…
Writing at 0x00010000… (1 %)
Writing at 0x0001ba5b… (2 %)
Writing at 0x00021a89… (3 %)
Writing at 0x00025aef… (4 %)
Writing at 0x00029aea… (5 %)
Writing at 0x0002dae5… (6 %)
Writing at 0x00031b28… (7 %)
Writing at 0x00035bc6… (8 %)
Writing at 0x00039bb2… (9 %)
Writing at 0x0003dbad… (10 %)
Writing at 0x00041df6… (11 %)
Writing at 0x00048fe1… (13 %)
Writing at 0x0005668f… (14 %)
Writing at 0x0006058b… (15 %)
Writing at 0x00069d84… (16 %)
Writing at 0x00072f01… (17 %)
Writing at 0x000870e9… (18 %)
Writing at 0x00093f66… (19 %)
Writing at 0x00099ea6… (20 %)
Writing at 0x0009f659… (21 %)
Writing at 0x000a527b… (22 %)
Writing at 0x000aad8d… (23 %)
Writing at 0x000b073f… (25 %)
Writing at 0x000b5e1f… (26 %)
Writing at 0x000bbcc6… (27 %)
Writing at 0x000c1664… (28 %)
Writing at 0x000c7916… (29 %)
Writing at 0x000cd233… (30 %)
Writing at 0x000d2f74… (31 %)
Writing at 0x000d87e7… (32 %)
Writing at 0x000de76f… (33 %)
Writing at 0x000e4a93… (34 %)
Writing at 0x000ea693… (35 %)
Writing at 0x000f044f… (36 %)
Writing at 0x000f62de… (38 %)
Writing at 0x000fb690… (39 %)
Writing at 0x001007f3… (40 %)
Writing at 0x0010629a… (41 %)
Writing at 0x0010bf4d… (42 %)
Writing at 0x00111464… (43 %)
Writing at 0x00116b08… (44 %)
Writing at 0x0011bef8… (45 %)
Writing at 0x0012115c… (46 %)
Writing at 0x0012651e… (47 %)
Writing at 0x0012c57b… (48 %)
Writing at 0x00131fbf… (50 %)
Writing at 0x0013762a… (51 %)
Writing at 0x0013ca11… (52 %)
Writing at 0x00141e1a… (53 %)
Writing at 0x001481f1… (54 %)
Writing at 0x0014da61… (55 %)
Writing at 0x001531b3… (56 %)
Writing at 0x00158eb6… (57 %)
Writing at 0x0015e795… (58 %)
Writing at 0x0016411d… (59 %)
Writing at 0x00169974… (60 %)
Writing at 0x0016f0ee… (61 %)
Writing at 0x00174bb2… (63 %)
Writing at 0x0017a4cd… (64 %)
Writing at 0x0017fb5c… (65 %)
Writing at 0x00185555… (66 %)
Writing at 0x0018a7be… (67 %)
Writing at 0x0018f909… (68 %)
Writing at 0x00195176… (69 %)
Writing at 0x0019a313… (70 %)
Writing at 0x001a0107… (71 %)
Writing at 0x001a6586… (72 %)
Writing at 0x001ac35a… (73 %)
Writing at 0x001b14c1… (75 %)
Writing at 0x001b6c71… (76 %)
Writing at 0x001bcef6… (77 %)
Writing at 0x001c2381… (78 %)
Writing at 0x001c7951… (79 %)
Writing at 0x001cd0ef… (80 %)
Writing at 0x001d23ad… (81 %)
Writing at 0x001d7777… (82 %)
Writing at 0x001dcb6c… (83 %)
Writing at 0x001e22a0… (84 %)
Writing at 0x001e7a57… (85 %)
Writing at 0x001ed833… (86 %)
Writing at 0x001f3253… (88 %)
Writing at 0x001f8a9c… (89 %)
Writing at 0x00201736… (90 %)
Writing at 0x00209f23… (91 %)
Writing at 0x00210c74… (92 %)
Writing at 0x00215fad… (93 %)
Writing at 0x0021da3d… (94 %)
Writing at 0x00223140… (95 %)
Writing at 0x002286ff… (96 %)
Writing at 0x0022e556… (97 %)
Writing at 0x002336f8… (98 %)
Writing at 0x0023928b… (100 %)
Wrote 2275472 bytes (1497673 compressed) at 0x00010000 in 23.2 seconds (effective 786.3 kbit/s)…
Hash of data verified.
Leaving…
Staying in bootloader.
Firmware upload complete. Resetting ESP32…
Resetting ESP32
______________________________________________________________________
ESP32 Reset
Command: [‘–chip’, ‘esp32’, ‘–port’, ‘\\.\COM4’, ‘–before’, ‘default_reset’, ‘run’]
esptool.py v4.7.0
Serial port \.\COM4
Connecting…
Device PID identification is only supported on COM and /dev/ serial ports.

Chip is ESP32-D0WD-V3 (revision v3.0)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 30:c6:f7:41:4e:34
Uploading stub…
Running stub…
Stub running…
Hard resetting via RTS pin…
Reset complete…

Hey optos,

I compared your upload log to my own, and it looks like there is no difference. The upload was successful, the data hash was verified, and the upload port was correct. I have a couple ideas we can try, though I haven’t seen this type of issue before.

  1. On the RTK Firmware Uploader GUI, drop the baud rate down to 115200. This will slow the upload down to about 3 minutes. If there are any issues with transfer speed due to the cable, this should eliminate them.

  2. Doing a full flash erase on the board. This one is a bit more involved, and the instructions are dependent on what you are comfortable with.

  • Install esptool (if you have pip installed, it is simply “pip install esptool” - let me know if you need more instructions)

  • esptool.exe --port COM4 erase_flash (use your USB-SERIAL CH340 COM port number in Device Manager)

  • RTK Firmware Uploader → Upload Firmware
  • If these fail to fix the issue, we can initiate a hardware swap for you; I’m quite curious to figure out why this issue is happening. Good luck, and please let us know how it goes!

    Thanks for your fast and detailed feedback. First I have tried to flash the firmware with the GUI update with 115200. This wasn’t resolving the boot loop.

    Second I have tried your advice with erasing the flash over esptool.exe. The output looks like the following

    C:\Users\optos>esptool.exe --port COM4 erase_flash
    esptool.py v4.7.0
    Serial port COM4
    Connecting....
    Detecting chip type... Unsupported detection protocol, switching and trying again...
    Connecting....
    Detecting chip type... ESP32
    Chip is ESP32-D0WD-V3 (revision v3.0)
    Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
    Crystal is 40MHz
    MAC: 30:c6:f7:41:4e:34
    Uploading stub...
    Running stub...
    Stub running...
    Erasing flash (this may take a while)...
    Chip erase completed successfully in 57.0s
    Hard resetting via RTS pin...
    

    For me it seems it was successful. Then I uploaded the firmware v4_0 again with the GUI updater. Please see the following output.

    etecting flash size
    ______________________________________________________________________
    ESP32 Flash Size Detection
    
    Command:	['--chip', 'esp32', '--port', '\\\\.\\COM4', '--baud', '115200', '--before', 'default_reset', '--after', 'no_reset', 'flash_id']
    
    esptool.py v4.7.0
    Serial port \\.\COM4
    Connecting...
    Device PID identification is only supported on COM and /dev/ serial ports.
    ..
    Chip is ESP32-D0WD-V3 (revision v3.0)
    Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
    Crystal is 40MHz
    MAC: 30:c6:f7:41:4e:34
    Uploading stub...
    Running stub...
    Stub running...
    Manufacturer: 20
    Device: 4018
    Detected flash size: 16MB
    Staying in bootloader.
    
    Flash detection complete. Uploading firmware...
    Flash size is 16MB
    
    Uploading firmware
    
    ______________________________________________________________________
    ESP32 Firmware Upload
    
    Command:	['--chip', 'esp32', '--port', '\\\\.\\COM4', '--baud', '115200', '--before', 'default_reset', '--after', 'no_reset', 'write_flash', '-z', '--flash_mode', 'dio', '--flash_freq', '80m', '--flash_size', 'detect', '0x1000', 'C:\\Users\\optos\\AppData\\Local\\Temp\\_MEI67202\\resource\\RTK_Surveyor.ino.bootloader.bin', '0x8000', 'C:\\Users\\optos\\AppData\\Local\\Temp\\_MEI67202\\resource\\RTK_Surveyor_Partitions_16MB.bin', '0xe000', 'C:\\Users\\optos\\AppData\\Local\\Temp\\_MEI67202\\resource\\boot_app0.bin', '0x10000', 'C:/Users/optos/Documents/RTKFacet/RTK_Surveyor_Firmware_v4_0.bin']
    
    esptool.py v4.7.0
    Serial port \\.\COM4
    Connecting...
    Device PID identification is only supported on COM and /dev/ serial ports.
    .
    Chip is ESP32-D0WD-V3 (revision v3.0)
    Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
    Crystal is 40MHz
    MAC: 30:c6:f7:41:4e:34
    Uploading stub...
    Running stub...
    Stub running...
    Configuring flash size...
    Auto-detected Flash size: 16MB
    Flash will be erased from 0x00001000 to 0x00005fff...
    Flash will be erased from 0x00008000 to 0x00008fff...
    Flash will be erased from 0x0000e000 to 0x0000ffff...
    Flash will be erased from 0x00010000 to 0x0023bfff...
    Flash params set to 0x024f
    Compressed 17984 bytes to 12318...
    Writing at 0x00001000... (100 %)
    Wrote 17984 bytes (12318 compressed) at 0x00001000 in 1.3 seconds (effective 107.0 kbit/s)...
    Hash of data verified.
    Compressed 3072 bytes to 129...
    Writing at 0x00008000... (100 %)
    Wrote 3072 bytes (129 compressed) at 0x00008000 in 0.1 seconds (effective 399.9 kbit/s)...
    Hash of data verified.
    Compressed 8192 bytes to 47...
    Writing at 0x0000e000... (100 %)
    Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 641.9 kbit/s)...
    Hash of data verified.
    Compressed 2275472 bytes to 1497673...
    Writing at 0x00010000... (1 %)
    Writing at 0x0001ba5b... (2 %)
    Writing at 0x00021a89... (3 %)
    Writing at 0x00025aef... (4 %)
    Writing at 0x00029aea... (5 %)
    Writing at 0x0002dae5... (6 %)
    Writing at 0x00031b28... (7 %)
    Writing at 0x00035bc6... (8 %)
    Writing at 0x00039bb2... (9 %)
    Writing at 0x0003dbad... (10 %)
    Writing at 0x00041df6... (11 %)
    Writing at 0x00048fe1... (13 %)
    Writing at 0x0005668f... (14 %)
    Writing at 0x0006058b... (15 %)
    Writing at 0x00069d84... (16 %)
    Writing at 0x00072f01... (17 %)
    Writing at 0x000870e9... (18 %)
    Writing at 0x00093f66... (19 %)
    Writing at 0x00099ea6... (20 %)
    Writing at 0x0009f659... (21 %)
    Writing at 0x000a527b... (22 %)
    Writing at 0x000aad8d... (23 %)
    Writing at 0x000b073f... (25 %)
    Writing at 0x000b5e1f... (26 %)
    Writing at 0x000bbcc6... (27 %)
    Writing at 0x000c1664... (28 %)
    Writing at 0x000c7916... (29 %)
    Writing at 0x000cd233... (30 %)
    Writing at 0x000d2f74... (31 %)
    Writing at 0x000d87e7... (32 %)
    Writing at 0x000de76f... (33 %)
    Writing at 0x000e4a93... (34 %)
    Writing at 0x000ea693... (35 %)
    Writing at 0x000f044f... (36 %)
    Writing at 0x000f62de... (38 %)
    Writing at 0x000fb690... (39 %)
    Writing at 0x001007f3... (40 %)
    Writing at 0x0010629a... (41 %)
    Writing at 0x0010bf4d... (42 %)
    Writing at 0x00111464... (43 %)
    Writing at 0x00116b08... (44 %)
    Writing at 0x0011bef8... (45 %)
    Writing at 0x0012115c... (46 %)
    Writing at 0x0012651e... (47 %)
    Writing at 0x0012c57b... (48 %)
    Writing at 0x00131fbf... (50 %)
    Writing at 0x0013762a... (51 %)
    Writing at 0x0013ca11... (52 %)
    Writing at 0x00141e1a... (53 %)
    Writing at 0x001481f1... (54 %)
    Writing at 0x0014da61... (55 %)
    Writing at 0x001531b3... (56 %)
    Writing at 0x00158eb6... (57 %)
    Writing at 0x0015e795... (58 %)
    Writing at 0x0016411d... (59 %)
    Writing at 0x00169974... (60 %)
    Writing at 0x0016f0ee... (61 %)
    Writing at 0x00174bb2... (63 %)
    Writing at 0x0017a4cd... (64 %)
    Writing at 0x0017fb5c... (65 %)
    Writing at 0x00185555... (66 %)
    Writing at 0x0018a7be... (67 %)
    Writing at 0x0018f909... (68 %)
    Writing at 0x00195176... (69 %)
    Writing at 0x0019a313... (70 %)
    Writing at 0x001a0107... (71 %)
    Writing at 0x001a6586... (72 %)
    Writing at 0x001ac35a... (73 %)
    Writing at 0x001b14c1... (75 %)
    Writing at 0x001b6c71... (76 %)
    Writing at 0x001bcef6... (77 %)
    Writing at 0x001c2381... (78 %)
    Writing at 0x001c7951... (79 %)
    Writing at 0x001cd0ef... (80 %)
    Writing at 0x001d23ad... (81 %)
    Writing at 0x001d7777... (82 %)
    Writing at 0x001dcb6c... (83 %)
    Writing at 0x001e22a0... (84 %)
    Writing at 0x001e7a57... (85 %)
    Writing at 0x001ed833... (86 %)
    Writing at 0x001f3253... (88 %)
    Writing at 0x001f8a9c... (89 %)
    Writing at 0x00201736... (90 %)
    Writing at 0x00209f23... (91 %)
    Writing at 0x00210c74... (92 %)
    Writing at 0x00215fad... (93 %)
    Writing at 0x0021da3d... (94 %)
    Writing at 0x00223140... (95 %)
    Writing at 0x002286ff... (96 %)
    Writing at 0x0022e556... (97 %)
    Writing at 0x002336f8... (98 %)
    Writing at 0x0023928b... (100 %)
    Wrote 2275472 bytes (1497673 compressed) at 0x00010000 in 132.0 seconds (effective 137.9 kbit/s)...
    Hash of data verified.
    
    Leaving...
    Staying in bootloader.
    
    Firmware upload complete. Resetting ESP32...
    Resetting ESP32
    
    ______________________________________________________________________
    ESP32 Reset
    
    Command:	['--chip', 'esp32', '--port', '\\\\.\\COM4', '--before', 'default_reset', 'run']
    
    esptool.py v4.7.0
    Serial port \\.\COM4
    Connecting...
    Device PID identification is only supported on COM and /dev/ serial ports.
    .
    Chip is ESP32-D0WD-V3 (revision v3.0)
    Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
    Crystal is 40MHz
    MAC: 30:c6:f7:41:4e:34
    Uploading stub...
    Running stub...
    Stub running...
    Hard resetting via RTS pin...
    
    Reset complete...
    

    In summary nothing has changed in the bahviour the RTK Facet is still in the boot loop. When I connect Teraterm I get continous the same output.

    rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (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:1
    load:0x3fff0030,len:1240
    load:0x07800000,len:3331136
    ets Jul 29 2019 12:21:46
    

    Please let me know if I should do more with the esptool.

    Thank you very much for your efforts.

    Do you have any updates on this topic ?

    swells:
    Hey optos,

    I compared your upload log to my own, and it looks like there is no difference. The upload was successful, the data hash was verified, and the upload port was correct. I have a couple ideas we can try, though I haven’t seen this type of issue before.

    1. On the RTK Firmware Uploader GUI, drop the baud rate down to 115200. This will slow the upload down to about 3 minutes. If there are any issues with transfer speed due to the cable, this should eliminate them.

    2. Doing a full flash erase on the board. This one is a bit more involved, and the instructions are dependent on what you are comfortable with.

  • Install esptool (if you have pip installed, it is simply “pip install esptool” - let me know if you need more instructions)

  • esptool.exe --port COM4 erase_flash (use your USB-SERIAL CH340 COM port number in Device Manager)

  • RTK Firmware Uploader → Upload Firmware
  • If these fail to fix the issue, we can initiate a hardware swap for you; I’m quite curious to figure out why this issue is happening. Good luck, and please let us know how it goes!

    I have tried all the stuff above, nothing have worked. Could we initiate a hardware swap as suggested ?

    Sorry about that, I never saw a notification that you’d replied.

    Yes, please fill out: https://www.sparkfun.com/returns

    Under the “why” section, include the link to this forum page.

    Thanks!

    Submitted the request via the link.