ESP32-PICO-V3-02

ESP_Sprite
Posts: 9715
Joined: Thu Nov 26, 2015 4:08 am

Re: ESP32-PICO-V3-02

Postby ESP_Sprite » Fri Jul 08, 2022 12:57 am

The 'two banks of flash' probably is an artifact of the same flash seen through both ESP32 cores; you can ignore it, there's only one 8MiB flash chip detected. There's two bootloaders in the ESP32, but only one of them is in flash; the one used for serial download is located in internal ROM (and is not changable or flashable as such).

If the bootloader is too large, it will clash with the partition table, so you'll need to relocate that as well; you can do that using menuconfig, Partition Table -> Offset of partition table.

AndreyVinogradov
Posts: 11
Joined: Thu Jun 23, 2022 4:51 pm

Re: ESP32-PICO-V3-02

Postby AndreyVinogradov » Fri Jul 08, 2022 6:41 pm

I see, thank you. But I still don't understand why after flashing via JTAG project stop flashing with UART. Probably the problem is not in bootloader size, but something else. I'm still trying to flash ESP-IDF-AT project to PICO, but the program always crushing at start. The same AT project I loaded with UART to ESP-WROOM-32D test board, and it loaded just fine:

Code: Select all

ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_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:2
load:0x3fff0030,len:6364
ho 0 tail 12 room 4
load:0x40078000,len:18392
ho 0 tail 12 room 4
load:0x40080400,len:4132
entry 0x400806c8
I (31) boot: ESP-IDF v4.3.2-553-g588436db47 2nd stage bootloader
I (31) boot: compile time 17:41:53
I (31) boot: chip revision: 3
I (35) boot_comm: chip revision: 3, min. bootloader chip revision: 0
I (42) boot.esp32: SPI Speed      : 40MHz
I (47) boot.esp32: SPI Mode       : DIO
I (51) boot.esp32: SPI Flash Size : 8MB
I (56) boot: Enabling RNG early entropy source...
I (61) boot: Partition Table:
I (65) boot: ## Label            Usage          Type ST Offset   Length
I (72) boot:  0 phy_init         RF data          01 01 0000f000 00001000
I (79) boot:  1 otadata          OTA data         01 00 00010000 00002000
I (87) boot:  2 nvs              WiFi data        01 02 00012000 0000e000
I (94) boot:  3 at_customize     unknown          40 00 00020000 000e0000
I (102) boot:  4 ota_0            OTA app          00 10 00100000 00180000
I (109) boot:  5 ota_1            OTA app          00 11 00280000 00180000
I (117) boot: End of partition table
I (121) boot_comm: chip revision: 3, min. application chip revision: 0
I (128) esp_image: segment 0: paddr=00100020 vaddr=3f400020 size=150e8h ( 86248)                                                                                                                                                              map
I (168) esp_image: segment 1: paddr=00115110 vaddr=3ffbdb60 size=03b48h ( 15176)                                                                                                                                                              load
I (174) esp_image: segment 2: paddr=00118c60 vaddr=40080000 size=073b8h ( 29624)                                                                                                                                                              load
I (186) esp_image: segment 3: paddr=00120020 vaddr=400d0020 size=ec80ch (968716)                                                                                                                                                              map
I (530) esp_image: segment 4: paddr=0020c834 vaddr=400873b8 size=139bch ( 80316)                                                                                                                                                              load
I (564) esp_image: segment 5: paddr=002201f8 vaddr=400c0000 size=00064h (   100)                                                                                                                                                              load
I (564) esp_image: segment 6: paddr=00220264 vaddr=50000000 size=00010h (    16)                                                                                                                                                              load
I (586) boot: Loaded app from partition at offset 0x100000
I (586) boot: Disabling RNG early entropy source...
module_name:WROOM-32
max tx power=78,ret=0
2.4.0
If I load it to PICO with UART it keeps returning "invalid header" errors.
And if I load project with JTAG, it can't flash some binaries at all. There is total 17 binary files I need to flash:
0x1000 build\bootloader\bootloader.bin
0xa000 build\partition_table\partition-table.bin
0xf000 build\phy_multiple_init_data.bin
0x10000 build\ota_data_initial.bin
0x20000 build\at_customize.bin
0x21000 build\customized_partitions\ble_data.bin
0x24000 build\customized_partitions\server_cert.bin
0x26000 build\customized_partitions\server_key.bin
0x28000 build\customized_partitions\server_ca.bin
0x2a000 build\customized_partitions\client_cert.bin
0x2c000 build\customized_partitions\client_key.bin
0x2e000 build\customized_partitions\client_ca.bin
0x30000 build\customized_partitions\factory_param.bin
0x37000 build\customized_partitions\mqtt_cert.bin
0x39000 build\customized_partitions\mqtt_key.bin
0x3B000 build\customized_partitions\mqtt_ca.bin
0x100000 build\esp-at.bin

And I can't flash ble_data.bin and mqtt_key.bin. It says that there is wrong checksum or something like dat. I tried to flash them separately from other files, change their location in memory, but no use. If I just ignore them program will be still crushing after "boot: Disabling RNG early entropy source..." and return "invalid header" errors infinitely. I tried to flash those two files with UART, but PICO did not like that too.

BTW, I don't even need those files. I already have external chip that is going to use it's own LwIP library and communicate with ESP-chip with AT-commands and do all the TCP stuff, like he did with ESP8285. But I can't even disable Bluetooth, because it's required by precompiled libraries in AT-project. Well, never mind, just grumbling...

ESP_Sprite
Posts: 9715
Joined: Thu Nov 26, 2015 4:08 am

Re: ESP32-PICO-V3-02

Postby ESP_Sprite » Sat Jul 09, 2022 2:32 am

AndreyVinogradov wrote:
Fri Jul 08, 2022 6:41 pm
BTW, I don't even need those files. I already have external chip that is going to use it's own LwIP library and communicate with ESP-chip with AT-commands and do all the TCP stuff, like he did with ESP8285. But I can't even disable Bluetooth, because it's required by precompiled libraries in AT-project. Well, never mind, just grumbling...
So you have your own TCP/IP stack? Then you're using the wrong project. Try esp-hosted instead.

Who is online

Users browsing this forum: aapee-jcv and 446 guests