ESP32_OLIMEX is not discovered after Flashing the Firmware

[M4rtinSc]

Target name(s)

ESP32_OLIMEX

Firmware version

1.12.4.372

Was working before? On which version?

ESP32_WT32_ETH01 1.12.4.372

Device capabilities

Firmware: ESP32_WT32_ETH01 1.12.4.372

System Information
HAL build info: nanoCLR running @ ESP32 built with ESP-IDF v5.2.3
Target: ESP32_WT32_ETH01
Platform: ESP32

Firmware build Info:
Date: Jul 24 2025
Type: MinSizeRel build, chip rev. >= 0, without support for PSRAM
CLR Version: 1.12.4.372
Compiler: GNU ARM GCC v13.2.0

OEM Product codes (vendor, model, SKU): 0, 0, 0

Serial Numbers (module, system):
00000000000000000000000000000000
1000000000483849D614

Target capabilities:
Has nanoBooter: NO
IFU capable: NO
Has proprietary bootloader: YES

AppDomains:

Assemblies:
SBCarWashControllerInterface, 1.0.0.0
System.Device.Gpio, 1.1.57.0
nanoFramework.M2Mqtt, 5.1.199.0
System.Net, 1.11.43.0
nanoFramework.System.Text, 1.3.42.0
System.IO.Streams, 1.1.96.0
mscorlib, 1.17.11.0
nanoFramework.Runtime.Events, 1.11.32.0
nanoFramework.Runtime.Native, 1.7.11.0
nanoFramework.M2Mqtt.Core, 5.1.199.0
System.Threading, 1.1.52.34401
nanoFramework.System.Collections, 1.5.67.0

Native Assemblies:
mscorlib v100.5.0.24, checksum 0x1549C856
nanoFramework.Runtime.Native v100.0.10.0, checksum 0x0EAE898B
nanoFramework.Hardware.Esp32 v100.0.10.0, checksum 0x6A20A689
nanoFramework.Hardware.Esp32.Rmt v100.0.5.1, checksum 0x8ADAC728
nanoFramework.Device.OneWire v100.0.4.0, checksum 0xB95C43B4
nanoFramework.Networking.Sntp v100.0.4.4, checksum 0xE2D9BDED
nanoFramework.ResourceManager v100.0.0.1, checksum 0xDCD7DF4D
nanoFramework.System.Collections v100.0.2.0, checksum 0x40DC251F
nanoFramework.System.Text v100.0.0.1, checksum 0x8E6EB73D
nanoFramework.System.IO.Hashing v100.0.0.1, checksum 0xEBD8ED20
nanoFramework.System.Security.Cryptography v100.0.0.3, checksum 0x343142CA
nanoFramework.Runtime.Events v100.0.8.0, checksum 0x0EAB00C9
EventSink v1.0.0.0, checksum 0xF32F4C3E
System.IO.FileSystem v1.1.0.4, checksum 0x1777E2FE
System.Math v100.0.5.5, checksum 0x9F9E2A7E
System.Net v100.2.0.11, checksum 0xD82C1452
System.Device.Adc v100.0.0.0, checksum 0xE5B80F0B
System.Device.Dac v100.0.0.6, checksum 0x02B3E860
System.Device.Gpio v100.1.0.6, checksum 0x097E7BC5
System.Device.I2c v100.0.0.2, checksum 0xFA806D33
System.Device.I2s v100.0.0.1, checksum 0x478490FE
System.Device.Pwm v100.1.0.4, checksum 0xABF532C3
System.IO.Ports v100.1.6.1, checksum 0xB798CE30
System.Device.Spi v100.1.2.0, checksum 0x3F6E2A7E
System.Runtime.Serialization v100.0.0.0, checksum 0x0A066871
System.Device.Wifi v100.0.6.4, checksum 0x00A058C6

++++++++++++++++++++++++++++++++
++ Memory Map ++
++++++++++++++++++++++++++++++++
Type Start Size
++++++++++++++++++++++++++++++++
RAM 0x3ffe46bc 0x0001b000
FLASH 0x00000000 0x01000000

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++ Flash Sector Map ++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Region Start Blocks Bytes/Block Usage
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
0 0x00010000 1 0x1B0000 nanoCLR
1 0x001C0000 1 0x2D0000 Deployment
2 0x00490000 1 0x300000 Configuration

+++++++++++++++++++++++++++++++++++++++++++++++++++
++ Storage Usage Map ++
+++++++++++++++++++++++++++++++++++++++++++++++++++
Start Size (kB) Usage
+++++++++++++++++++++++++++++++++++++++++++++++++++
0x00490000 0x300000 (3072kB) Configuration
0x00010000 0x1B0000 (1728kB) nanoCLR
0x001C0000 0x2D0000 (2880kB) Deployment

Deployment Map
Empty

Description

I own a Olimex ESP32-POE-ISO-16MB rev. M Development board.

if i flash the Firmware ESP32_OLIMEX 1.12.4.372 the board is not discovered by VisualStudio
if I flash the Firmware ESP32_WT32_ETH01 1.12.4.372 is discovered

How to reproduce

1. Flash ESP32_OLIMEX 1.12.4.372 nanoff --update --target ESP32_OLIMEX --serialport COM4
2. Unplug the board
3. Replug the board
4. Check Serial Port
5. Open VS
6. Open Device Explorer -> no device

Same procedure with ESP32_WT32_ETH01 1.12.4.372 Firmware shows up a device

Expected behaviour

No response

Screenshots

No response

Aditional information

No response

[alberk8]

@M4rtinSc, Try to flash nanoff --update --target ESP32_OLIMEX --serialport COM4 --masserase

[M4rtinSc]

thanks for the reply, but still the same behavior.

I tested with other "inbuild ethernet" images:

ESP32_OLIMEX_WROVER
ESP32_ETHERNET_KIT_1.2
ESP32_WT32_ETH01
The device is discovered and i can deploy to them, but the network interfaces (LAN/WiFi aren't working

ESP32_WESP32
ESP32_LILYGO
The device is not discovered, like ESP32_OLIMEX

Any Ideas?

[M4rtinSc]

ESP32_REV0 is discovered, but ethernet / wifi not working.

if I run
nanoff --update --identifyfirmware --serialport COM5
I get following output:

Reading details from chip...OK                                                                                                            

Connected to:
ESP32 (ESP32-D0WD-V3 (revision v3.1))
Features WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Flash size 16MB unknown from  (manufacturer 0x161 device 0x16408)
PSRAM: undetermined
Crystal 40MHz
MAC xxxxxxx

Target 'ESP32_REV3' best matches the device characteristics.

if I flash the ESP32_REV3 image, device is discovered and WIFI is working, but LAN not.
NetworkInterface.GetAllNetworkInterfaces(); Returns only WIFI and WIFI AP, so I think the LAN Drivers not present in that Image.

[alberk8]

Ok that means the VS Debug is working with non LAN image. You have to check of the GPIO1 and GPIO3 are not utilized by your program.

[M4rtinSc]

GPIO1 and GPIO3 aren't in use.

I think I found a reason why it's not detected:
Putty Output

Rebooting...
ets Jul 29 2019 12:21:46

rst:0x3 (SW_RESET),boot:0x1b (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:6064
load:0x40078000,len:14996
ho 0 tail 12 room 4
load:0x40080400,len:4
load:0x40080404,len:3748
entry 0x40080618
I (30) boot: .NET nanoFramework 2nd stage bootloader ESP-IDF v5.2.3
I (30) boot: build Jul 24 2025 00:13:03
I (32) boot: chip revision: v3.1
I (36) boot.esp32: SPI Speed      : 80MHz
I (40) boot.esp32: SPI Mode       : DIO
I (45) boot.esp32: SPI Flash Size : 16MB
I (50) boot: Enabling RNG early entropy source...
I (55) boot: Partition Table:
I (59) boot: ## Label            Usage          Type ST Offset   Length
I (66) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (73) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (81) boot:  2 factory          factory app      00 00 00010000 001b0000
I (88) boot:  3 deploy           Unknown data     01 84 001c0000 002d0000
I (96) boot:  4 config           Unknown data     01 83 00490000 00300000
I (103) boot: End of partition table
I (108) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=2ed68h (191848) map
I (144) esp_image: segment 1: paddr=0003ed90 vaddr=3ff80062 size=00008h (     8) load
I (144) esp_image: segment 2: paddr=0003eda0 vaddr=3ffb0000 size=01278h (  4728) load
I (151) esp_image: segment 3: paddr=00040020 vaddr=400d0020 size=eb4ach (963756) map
I (299) esp_image: segment 4: paddr=0012b4d4 vaddr=3ffb1278 size=02e9ch ( 11932) load
I (302) esp_image: segment 5: paddr=0012e378 vaddr=40080000 size=1b320h (111392) load
I (327) esp_image: segment 6: paddr=001496a0 vaddr=400c0000 size=00064h (   100) load
I (340) boot: Loaded app from partition at offset 0x10000
I (341) boot: Disabling RNG early entropy source...
I (352) cpu_start: Multicore app
I (353) quad_psram: This chip is ESP32-D0WD
E (353) quad_psram: PSRAM ID read error: 0xffffffff, PSRAM chip not found or not supported
E (361) esp_psram: PSRAM enabled but initialization failed. Bailing out.
I (368) cpu_start: Failed to init external RAM; continuing without it.
I (387) cpu_start: Pro cpu start user code
I (387) cpu_start: cpu freq: 160000000 Hz
I (387) cpu_start: Application information:
I (392) cpu_start: Project name:     nanoCLR
I (397) cpu_start: App version:      1.12.4.372
I (402) cpu_start: Compile time:     Jul 24 2025 00:10:37
I (408) cpu_start: ELF file SHA256:  9b46fc395...
I (414) cpu_start: ESP-IDF:          v5.2.3
I (418) cpu_start: Min chip rev:     v0.0
I (423) cpu_start: Max chip rev:     v3.99
I (428) cpu_start: Chip rev:         v3.1
I (433) heap_init: Initializing. RAM available for dynamic allocation:
I (440) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (446) heap_init: At 3FFBE060 len 00021FA0 (135 KiB): DRAM
I (452) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (459) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (465) heap_init: At 4009B320 len 00004CE0 (19 KiB): IRAM
Guru Meditation Error: Core  0 panic'ed (Cache disabled but cached memory region accessed).

Core  0 register dump:
PC      : 0x401b3d0c  PS      : 0x00060534  A0      : 0x80091a00  A1      : 0x3ffe3a90
A2      : 0x3ff42000  A3      : 0x3ffe3b1f  A4      : 0x00000000  A5      : 0x00000003
A6      : 0x00000001  A7      : 0x00000001  A8      : 0x80091676  A9      : 0x00000004
A10     : 0x3ffe3b1c  A11     : 0x3ffe3a90  A12     : 0x00000003  A13     : 0x00000000
A14     : 0xbfffffff  A15     : 0x3ffb0710  SAR     : 0x00000008  EXCCAUSE: 0x00000007
EXCVADDR: 0x00000000  LBEG    : 0x40099ee2  LEND    : 0x40099ee6  LCOUNT  : 0x00000000


Backtrace: 0x401b3d09:0x3ffe3a90 0x400919fd:0x3ffe3ad0 0x40099eff:0x3ffe3b00 0x4008823e:0x3ffe3b40 0x4017307d:0x3ffe3b70 0x40088342:0x3ffe3b90 0x40172edb:0x3ffe3bc0 0x4012dbf0:0x3ffe3c20 0x40083b7d:0x3ffe3c60 0x400795ce:0x3ffe3c90 |<-CORRUPTED




ELF file SHA256: 9b46fc395

I own this board:
https://www.olimex.com/Products/IoT/ESP32/ESP32-POE-ISO/open-source-hardware
the ESP32-POE-ISO-16MB version.
Is the ESP32_OLIMEX image the right one for that board?

[josesimoes]

For a network device, with TLS and all that, you would be better served with a version featuring PSRAM...
On your comment above, yes, the device is constantly rebooting because of that core panic. Reason for not showing up on VS.

Pinging @AdrianSoundy

[AdrianSoundy]

You are better off with the ESP32-POE-ISO-WROVER variant of the board which has psram.
This uses the ESP32_OLIMEX_WROVER firmware which is working.

[AdrianSoundy]

The ESP32_olimex build gives a panic on startup with the IDF 5.2.3
This is resolved in the next IDF version which should be merged soon.
See PR -> #3132

[M4rtinSc]

Thanks a lot