ESP IDF Version

nonagon
Posts: 17
Joined: Thu May 06, 2021 12:56 pm

ESP IDF Version

Postby nonagon » Mon Jun 21, 2021 1:37 pm

I have this log from compiled firmware:
Please can you point me to understand what version of ESP-IDF I'm using?
This log indicate ESP-IDF 3.4 but I was sure of using the 4.2
Thank you in advice.

Code: Select all

␛[0;32mI (29) boot: ESP-IDF 3.40200.210118 2nd stage bootloader␛[0m
␛[0;32mI (29) boot: compile time 12:11:25␛[0m
␛[0;32mI (29) boot: chip revision: 3␛[0m
␛[0;32mI (33) boot_comm: chip revision: 3, min. bootloader chip revision: 0␛[0m

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

Re: ESP IDF Version

Postby ESP_Sprite » Tue Jun 22, 2021 2:30 am

It almost looks like that message got corrupted... if you still have the log output, later versions of ESP-IDF also spit out their version later on, e.g.

Code: Select all

I (145) boot: Disabling RNG early entropy source...
I (151) cpu_start: Pro cpu up.
I (166) cpu_start: Pro cpu start user code
I (166) cpu_start: cpu freq: 160000000
I (166) cpu_start: Application information:
I (168) cpu_start: Project name:     blink
I (173) cpu_start: App version:      1
I (178) cpu_start: Compile time:     Jun 21 2021 17:24:55
I (184) cpu_start: ELF file SHA256:  e7ffbf22cd005bd1...
I (190) cpu_start: ESP-IDF:          v4.4-dev-1758-g23b7558a7e

nonagon
Posts: 17
Joined: Thu May 06, 2021 12:56 pm

Re: ESP IDF Version

Postby nonagon » Tue Jun 22, 2021 9:33 am

Hello,
that symbols are the ANSI color special characters, the output is not corrupted, anyway I found in menuconfig how disable it, now I have this output:

Code: Select all

I (532) boot: Disabling RNG early entropy source...
I (533) psram: This chip is ESP32-D0WD
I (536) spiram: Found 64MBit SPI RAM device
I (540) spiram: SPI RAM mode: flash 40m sram 40m
I (544) spiram: PSRAM initialized, cache is in low/high (2-core) mode.
I (550) cpu_start: Pro cpu up.
I (553) cpu_start: Application information:
I (557) cpu_start: Project name:     BuildTest
I (562) cpu_start: App version:      1
I (566) cpu_start: Compile time:     Jun 22 2021 11:09:33
I (571) cpu_start: ELF file SHA256:  9ef31b7ee58127c1...
I (576) cpu_start: ESP-IDF:          3.40200.210118
I (580) cpu_start: Starting app cpu, entry point is 0x40081e40
I (0) cpu_start: App cpu up.
I (1473) spiram: SPI SRAM memory test OK
I (1474) heap_init: Initializing. RAM available f
the Build output give me other informations:

Code: Select all

CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp-wrover-kit.html
PLATFORM: Espressif 32 (3.2.0+sha.56f9c60) > Espressif ESP-WROVER-KIT
HARDWARE: ESP32 240MHz, 320KB RAM, 8MB Flash
DEBUG: Current (ftdi) On-board (ftdi) External (esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES:
[b] - framework-espidf 3.40201.210513 (4.2.1)[/b]
 - tool-cmake 3.16.4
 - tool-esptoolpy 1.30000.201119 (3.0.0)
 - tool-idf 1.0.1
 - tool-mconf 1.4060000.20190628 (406.0.0)
 - tool-mkspiffs 2.230.0 (2.30)
 - tool-ninja 1.9.0
 - toolchain-esp32ulp 1.22851.191205 (2.28.51)
 - toolchain-xtensa32 2.80400.210211 (8.4.0)
Reading CMake configuration...
LDF: Library Dependency Finder -> http://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 0 compatible libraries
Scanning dependencies...
No dependencies
Building in release mode
In this last output now I can understand that I'm using the 4.2.1 version of the SDK, as expected.

I'm using platformio with IDF because I found it more automatized than Espressif Visual Studio Code pluging.
Do you are planning to move to a better, more integrated, IDE solution like a custom version of Visual Studio?
I like the IDF framework, the API are good documented and it seems stable but there is a big gap with others microcontroller family with dedicated IDE. I had the firmware code (Developed for ARM) so what I need is to write HAL to make it working with ESP32, and I did it.
But I think is not possibile today to write a big project for ESP32. IDE tools are too poor despite the good API's, this is a feedback, if I'm wrong please point me to a better developing enviroment for ESP32.

Who is online

Users browsing this forum: No registered users and 109 guests