Deploying the managed application to the ESP32 target failed

[jingqunhu]

It seems that the application is not written as successful，
but I can deploy it using the debug run of VS2022，
Is there any friend who has encountered such a situation? I have also switched many versions of nanoff, and it is the same problem. Thank you so much

[jingqunhu]

When I look at the startup log with 115200 baud rate it looks like this

I (458) quad_psram: This chip is ESP32-D0WD
I (459) esp_psram: Found 8MB PSRAM device
I (462) esp_psram: Speed: 40MHz
I (466) esp_psram: PSRAM initialized, cache is in low/high (2-core) mode.
W (474) esp_psram: Virtual address not enough for PSRAM, map as much as we can. 4MB is mapped
I (483) cpu_start: Pro cpu up.
I (486) cpu_start: Starting app cpu, entry point is 0x400843a8
I (0) cpu_start: App cpu up.
I (1372) esp_psram: SPI SRAM memory test OK
I (1380) cpu_start: Pro cpu start user code
I (1380) cpu_start: cpu freq: 240000000 Hz
I (1380) cpu_start: Application information:
I (1383) cpu_start: Project name:     nanoCLR
I (1388) cpu_start: App version:      1.10.0.10
I (1393) cpu_start: Compile time:     Jul  5 2024 22:13:51
I (1400) cpu_start: ELF file SHA256:  fc73a3e8a6acad76...
I (1406) cpu_start: ESP-IDF:          v5.1.4
I (1411) cpu_start: Min chip rev:     v3.0
I (1415) cpu_start: Max chip rev:     v3.99 
I (1420) cpu_start: Chip rev:         v3.1
I (1425) heap_init: Initializing. RAM available for dynamic allocation:
I (1433) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
I (1439) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM
I (1445) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM
I (1451) heap_init: At 3FFCF0C0 len 00010F40 (67 KiB): DRAM
I (1457) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (1464) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (1470) heap_init: At 4009B49C len 00004B64 (18 KiB): IRAM
I (1477) esp_psram: Adding pool of 4096K of PSRAM memory to heap allocator
I (1485) spi_flash: detected chip: gd
I (1488) spi_flash: flash io: dio
W (1492) rmt(legacy): legacy driver is deprecated, please migrate to `driver/rmt_tx.h` and/or `driver/rmt_rx.h`
W (1503) i2s(legacy): legacy i2s driver is deprecated, please migrate to use driver/i2s_std.h, driver/i2s_pdm.h or driver/i2s_tdm.h
W (1516) ADC: legacy driver is deprecated, please migrate to `esp_adc/adc_oneshot.h`
I (1536) coexist: coex firmware version: d96c1e51f
I (1537) app_start: Starting scheduler on CPU0
II (1537) app_start: Starting scheduler on CPU1
 (1537) main_task: Started on CPU0
I (1547) esp_psram: Reserving pool of 32K of internal memory for DMA/internal allocations
I (1547) main_task: Calling app_main()

[alberk8]

If you want to see the Console.WriteLine or Debug.WriteLine of your app on the Serial Console then you need to set the BaudRate to 921600

[jingqunhu]

Yes, the picture is Portland 961200

[alberk8]

If you get NFPKTV1 and that means the VS extension should be able to talk to it. Make sure you close all your serial console program as VS will not be able to detect if other serial console program is running and connecting to the same COM port.

[jingqunhu]

I solved this problem by burning directly from the command line of esptool