Unfortunatelly, when trying to program the new custom board with the PICO-V3, the flashing procedure fails half way through.
When starting the ESP in the normal way, this is outputted from the UART port:
Code: Select all
rst:0x10 (RTCWDT_RTC_RESET),boot:0x1f (SPI_FAST_FLASH_BOOT)
invalid header: 0xffffffff
invalid header: 0xffffffff
invalid header: 0xffffffff
...
When trying to flash new code, it gets a timeout mid way thorugh the process:
Code: Select all
TRACE +0.000 Write 171 bytes:
c00011a000720000 0090000000000000 | .....r..........
0000000000000000 0078da5b15dbdcc8 | .........x.[....
c430818181218081 21afac98011dac0a | .0...!..!.......
6064607800642830 30e49724a6249624 | `d`x.d(00..$.$.$
a2c93308303000d5 3088302416141860 | ..3.00..0.0$...`
ea671064601085c9 1b62317f26038326 | .g.d`....b1.&..&
03c894d4d482a2fc 5c0cf9260601a0fc | ........\..&....
073186e282ccb434 3427be7efd1f055c | .1.....44'.~...\
779150cfe638b964 ddae9f6f23ac4f4c | w.P..8.d...o#.OL
fb3f0a46c1281805 a360148c8251300a | .?.F.(...`...Q0.
46c128800300fb17 44a6c0 | F.(.....D..
TRACE +0.018 Read 1 bytes: c0
TRACE +0.000 Read 11 bytes: 01110200000000000000c0
TRACE +0.001 Received full packet: 01110200000000000000
TRACE +0.001 command op=0x0a data len=4 wait_response=1 timeout=3.000 data=00100040
TRACE +0.000 Write 14 bytes: c0000a04000000000000100040c0
TRACE +3.014 Timed out waiting for packet header
A fatal error occurred: Timed out waiting for packet header
Based on this log, it seems like the UART communication (we are using a CP2102N USB-UART) works as expected.
My best guess is that when the PICO-V3 is used, a special flash configuration needs to be set, but we have been playing with it for a while and we have had no success.
Any idea on why that might be happening?