- This topic has 21 replies, 2 voices, and was last updated 6 years, 1 month ago by
.
-
Posts
-
In the ESP-IDF release 3.1, I create the simple wifi example and I want to add some http server functionality, however I cannot find the http server files.
I see the esp_http_client files but the http_server is missing.
Am I doing something wrong?
Thanks.
I am getting a bit confused. I don’t understand what is the difference between ESP-IDF and the different versions of it.
So, lets make it more simple.
If I start from the simple wifi example, how can I add a http_server in my program?
Thanks.
I used downloaded the master branch and there are three http server examples.
So, why there is not a http server example in the v3.1 (and I also noticed that there is not one in v3.0 as well)???
However the simple project fails to build. This is the output, can you help?:
—— Build started: Project: EmbeddedProject6, Configuration: Debug VisualGDB ——
VisualGDB: Run “c:\SysGCC\esp32\bin\bash.exe –login -c “export IDF_PATH=/esp-idf/master && export BATCH_BUILD=1 && export -n PYTHONHOME && export LANG=en_US && cd /cygdrive/c/Users/kostbill/source/repos/EmbeddedProject6/EmbeddedProject6 && make -j4 BUILD_DIR_BASE=’/cygdrive/c/Users/kostbill/source/repos/EmbeddedProject6/EmbeddedProject6/Debug’ SDKCONFIG=’/cygdrive/c/Users/kostbill/source/repos/EmbeddedProject6/EmbeddedProject6/sdkconfig-debug’ V=0″” in directory “” on local computer
including /esp-idf/master/components/app_update/Makefile.projbuild…
including /esp-idf/master/components/bootloader/Makefile.projbuild…
including /esp-idf/master/components/bootloader_support/Makefile.projbuild…
including /esp-idf/master/components/coap/Makefile.projbuild…
including /esp-idf/master/components/esp32/Makefile.projbuild…
including /esp-idf/master/components/esptool_py/Makefile.projbuild…
including /esp-idf/master/components/mbedtls/Makefile.projbuild…
including /esp-idf/master/components/nghttp/Makefile.projbuild…
including /esp-idf/master/components/partition_table/Makefile.projbuild…
including /esp-idf/master/components/ulp/Makefile.projbuild…
make[1]: Entering directory ‘/esp-idf/master/tools/kconfig’
cc -c -D_GNU_SOURCE -D_DEFAULT_SOURCE -DCURSES_LOC=”<ncurses.h>” -DNCURSES_WIDECHAR=1 -DLOCALE -MMD /esp-idf/master/tools/kconfig/mconf.c -o mconf.o
flex -L -P zconf -o zconf.lex.c /esp-idf/master/tools/kconfig/zconf.l
bison -t -l -p zconf -o zconf.tab.c /esp-idf/master/tools/kconfig/zconf.y
sed -E “s/\\x0D$//” /esp-idf/master/tools/kconfig/zconf.gperf | gperf -t –output-file zconf.hash.c -a -C -E -g -k ‘1,3,$’ -p -t
cc -I /esp-idf/master/tools/kconfig -c -D_GNU_SOURCE -D_DEFAULT_SOURCE -DCURSES_LOC=”<ncurses.h>” -DNCURSES_WIDECHAR=1 -DLOCALE -MMD zconf.tab.c -o zconf.tab.o
/esp-idf/master/tools/kconfig/lxdialog/check-lxdialog.sh -check cc -D_GNU_SOURCE -D_DEFAULT_SOURCE -DCURSES_LOC=”<ncurses.h>” -DNCURSES_WIDECHAR=1 -DLOCALE -MMD -lncursesw -lintl
cc -c -D_GNU_SOURCE -D_DEFAULT_SOURCE -DCURSES_LOC=”<ncurses.h>” -DNCURSES_WIDECHAR=1 -DLOCALE -MMD /esp-idf/master/tools/kconfig/lxdialog/checklist.c -o lxdialog/checklist.o
cc -c -D_GNU_SOURCE -D_DEFAULT_SOURCE -DCURSES_LOC=”<ncurses.h>” -DNCURSES_WIDECHAR=1 -DLOCALE -MMD /esp-idf/master/tools/kconfig/lxdialog/util.c -o lxdialog/util.o
cc -c -D_GNU_SOURCE -D_DEFAULT_SOURCE -DCURSES_LOC=”<ncurses.h>” -DNCURSES_WIDECHAR=1 -DLOCALE -MMD /esp-idf/master/tools/kconfig/lxdialog/inputbox.c -o lxdialog/inputbox.o
cc -c -D_GNU_SOURCE -D_DEFAULT_SOURCE -DCURSES_LOC=”<ncurses.h>” -DNCURSES_WIDECHAR=1 -DLOCALE -MMD /esp-idf/master/tools/kconfig/lxdialog/textbox.c -o lxdialog/textbox.o
cc -c -D_GNU_SOURCE -D_DEFAULT_SOURCE -DCURSES_LOC=”<ncurses.h>” -DNCURSES_WIDECHAR=1 -DLOCALE -MMD /esp-idf/master/tools/kconfig/lxdialog/yesno.c -o lxdialog/yesno.o
cc -c -D_GNU_SOURCE -D_DEFAULT_SOURCE -DCURSES_LOC=”<ncurses.h>” -DNCURSES_WIDECHAR=1 -DLOCALE -MMD /esp-idf/master/tools/kconfig/lxdialog/menubox.c -o lxdialog/menubox.o
cc -o mconf-idf mconf.o zconf.tab.o lxdialog/checklist.o lxdialog/util.o lxdialog/inputbox.o lxdialog/textbox.o lxdialog/yesno.o lxdialog/menubox.o -lncursesw -lintl
cc -c -D_GNU_SOURCE -D_DEFAULT_SOURCE -DCURSES_LOC=”<ncurses.h>” -DNCURSES_WIDECHAR=1 -DLOCALE -MMD /esp-idf/master/tools/kconfig/conf.c -o conf.o
cc -o conf-idf conf.o zconf.tab.o -lncursesw -lintl
make[1]: Leaving directory ‘/esp-idf/master/tools/kconfig’
GENCONFIG
#
# configuration written to /cygdrive/c/Users/kostbill/source/repos/EmbeddedProject6/EmbeddedProject6/sdkconfig-debug
#
including /esp-idf/master/components/app_update/Makefile.projbuild…
including /esp-idf/master/components/bootloader/Makefile.projbuild…
including /esp-idf/master/components/bootloader_support/Makefile.projbuild…
including /esp-idf/master/components/coap/Makefile.projbuild…
including /esp-idf/master/components/esp32/Makefile.projbuild…
including /esp-idf/master/components/esptool_py/Makefile.projbuild…
including /esp-idf/master/components/mbedtls/Makefile.projbuild…
including /esp-idf/master/components/nghttp/Makefile.projbuild…
including /esp-idf/master/components/partition_table/Makefile.projbuild…
including /esp-idf/master/components/ulp/Makefile.projbuild…
CC Debug/app_trace/app_trace.o
CC Debug/app_update/esp_ota_ops.o
The following Python requirements are not satisfied:
future>=0.16.0
cryptography
Please run “/usr/bin/python -m pip install –user -r /esp-idf/master/requirements.txt” for resolving the issue.
make: *** [/esp-idf/master/make/project.mk:454: check_python_dependencies] Error 1
make: *** Waiting for unfinished jobs….
CC Debug/app_trace/host_file_io.o
CC Debug/app_trace/app_trace_util.o
AR Debug/app_update/libapp_update.a
CC Debug/app_trace/gcov/gcov_rtio.o
AR Debug/app_trace/libapp_trace.a
including /esp-idf/master/components/esptool_py/Makefile.projbuild…
including /esp-idf/master/components/bootloader_support/Makefile.projbuild…
including /esp-idf/master/components/bootloader/subproject/main/Makefile.projbuild…
WARNING: Toolchain version is not supported: crosstool-ng-1.22.0-80-g6c4433a5
Expected to see version: crosstool-ng-1.22.0-80-g6c4433a
Please check ESP-IDF setup instructions and update the toolchain, or proceed at your own risk.
including /esp-idf/master/components/esptool_py/Makefile.projbuild…
including /esp-idf/master/components/bootloader_support/Makefile.projbuild…
including /esp-idf/master/components/bootloader/subproject/main/Makefile.projbuild…
CC Debug/bootloader/bootloader_support/src/bootloader_random.o
CC Debug/bootloader/log/log.o
CC Debug/bootloader/spi_flash/spi_flash_rom_patch.o
CC Debug/bootloader/micro-ecc/micro-ecc/uECC.o
CC Debug/bootloader/bootloader_support/src/flash_encrypt.o
AR Debug/bootloader/log/liblog.a
AR Debug/bootloader/spi_flash/libspi_flash.a
AR Debug/bootloader/micro-ecc/libmicro-ecc.a
CC Debug/bootloader/bootloader_support/src/bootloader_sha.o
CC Debug/bootloader/soc/esp32/rtc_clk.o
CC Debug/bootloader/main/bootloader_start.o
CC Debug/bootloader/bootloader_support/src/esp_image_format.o
CC Debug/bootloader/bootloader_support/src/flash_partitions.o
CC Debug/bootloader/soc/esp32/rtc_time.o
AR Debug/bootloader/main/libmain.a
CC Debug/bootloader/bootloader_support/src/secure_boot_signatures.o
CC Debug/bootloader/bootloader_support/src/bootloader_clock.o
CC Debug/bootloader/soc/esp32/rtc_sleep.o
CC Debug/bootloader/soc/esp32/gpio_periph.o
CC Debug/bootloader/bootloader_support/src/secure_boot.o
CC Debug/bootloader/bootloader_support/src/bootloader_common.o
CC Debug/bootloader/soc/esp32/rtc_clk_init.o
CC Debug/bootloader/soc/esp32/spi_periph.o
CC Debug/bootloader/bootloader_support/src/bootloader_utility.o
CC Debug/bootloader/bootloader_support/src/bootloader_init.o
CC Debug/bootloader/soc/esp32/rtc_init.o
CC Debug/bootloader/soc/esp32/sdio_slave_periph.o
CC Debug/bootloader/bootloader_support/src/efuse.o
CC Debug/bootloader/soc/esp32/rtc_wdt.o
CC Debug/bootloader/bootloader_support/src/flash_qio_mode.o
CC Debug/bootloader/soc/esp32/sdmmc_periph.o
CC Debug/bootloader/bootloader_support/src/bootloader_flash.o
CC Debug/bootloader/soc/esp32/cpu_util.o
CC Debug/bootloader/soc/esp32/rtc_periph.o
CC Debug/bootloader/soc/esp32/rtc_pm.o
AR Debug/bootloader/bootloader_support/libbootloader_support.a
CC Debug/bootloader/soc/esp32/soc_memory_layout.o
CC Debug/bootloader/soc/src//memory_layout_utils.o
AR Debug/bootloader/soc/libsoc.a
LD Debug/bootloader/bootloader.elf
esptool.py v2.5.0
————————————————————-
Command exited with code 2
Executable: c:\SysGCC\esp32\bin\bash.exe
Arguments: –login -c “export IDF_PATH=/esp-idf/master && export BATCH_BUILD=1 && export -n PYTHONHOME && export LANG=en_US && cd /cygdrive/c/Users/kostbill/source/repos/EmbeddedProject6/EmbeddedProject6 && make -j4 BUILD_DIR_BASE=’/cygdrive/c/Users/kostbill/source/repos/EmbeddedProject6/EmbeddedProject6/Debug’ SDKCONFIG=’/cygdrive/c/Users/kostbill/source/repos/EmbeddedProject6/EmbeddedProject6/sdkconfig-debug’ V=0”
Directory:
VisualGDB: Error: Command-line action failed
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========Hi,
This looks like a common problem of the ESP32 toolchain. Please follow the instructions described in this thread in order to fix it.
Please also note that the ESP-IDF is not as stable as other SDKs; components may be added and removed between versions, and the master branch may simply not always work. VisualGDB provides convenient user interface and workarounds for common issues, however the exact contents of each ESP-IDF release is outside our control, so we would generally advise trying several ESP-IDF versions and finding the one that works the best for you.
I am unable to follow all the things in the thread you posted, it follows commands from another thread, where the user is using linux and I am totally confused.
I don’t even know what the MSYS2 is and where I should install it, and how to tell to the environment where to find it.
I tried to build another example from the master rep, even the experimental one, with no luck.
I tried to use the embedded project wizard, instead of the ESP IDF wizard, but still would not build.
I have the latest visualgdb and I didn’t do anything by hand, the wizard took care of downloading the packages.
Is there another procedure I should use, which is not automated?
Thanks.
Well, it seems that there are very few examples that I can actually compile.
I have no idea how to work from here.
Sorry for the delay. We were running the final tests on the new VisualGDB 5.4 Preview 6 that considerably improves the ESP-IDF experience and have just released it.
Please try downloading VisualGDB 5.4 Preview 6 and then update your ESP32 toolchain to the latest version. Please try using CMake instead of the regular GNU Make when creating the project – it should result in much faster build speed.
Let us know if you encounter any problems with the new toolchain and VisualGDB build and we will be happy to help.
Nop, didn’t work. Have you tried the simple http server example? Does it work for you?
However this time I didn’t have the module connected to my PC. Do you think this could be the reason? I will have the module again on Monday.
If this is not the reason, let me know to paste the output.
Hi,
We have just rested everything. The ESP-IDF v3.1 works as expected. Trying out the master branch indeed results in errors.
It looks like a known bug of the latest ESP-IDF and Espressif might be working on resolving it. As one of the comments on the bug thread mentions, you might be able to get it to work by rebuilding the toolchain from scratch (let us know if you need help getting VisualGDB to recognize the rebuilt toolchain), but if you don’t want to spend time diagnosing incompatibility between different components, we would simply advise waiting until Espressif fixes this (we will update our toolchain accordingly once they release a stable package compatible with the master branch).
Thanks for that, I will wait.
In the meanwhile, I will setup the eclipse environment, do you think it will cause problems with the visualgdb installation?
I am asking because of all the environment paths etc.
Thanks.
Hi,
It shouldn’t cause any extra problems, but it will trigger the same issue is you use the pre-packaged toolchain (as the problem is due to missing packages in the toolchain and not in VisualGDB). If you use a different toolchain (e.g. build one from scratch) and it works, you can easily use it with VisualGDB as well by copying the toolchain.xml file and esp32-bsp folder from our toolchain to it and importing it into VisualGDB.
I have a question, if I use an older version, shouldn’t that work?
I downloaded v3.0 and I still have errors. I don’t understand.
Any advice?
Hi,
Sorry, it’s hard to give any advice without seeing the exact error messages. The easiest way to get it to work would be to:
- Install VisualGDB 5.4 Preview 6.
- Completely remove your ESP32 toolchain and install it from scratch via VisualGDB Package Manager.
- Create a new project using the v3.1 checkout that is included in the toolchain.
This is the scenario that we test as a part of our pre-release tests, so it should work out-of-the-box.
- You must be logged in to reply to this topic.