esp-idf/examples/get-started/hello_world
huardti a01820c583 hello_world: fix incorrect printf format
spi_flash_get_chip_size return a size_t to printf this type it's better to use %u than %d.

We didn't use %zu because it will be ignored by "nano" printf (i.e. when
CONFIG_NEWLIB_NANO_FORMAT is on).

Closes https://github.com/espressif/esp-idf/pull/8900
2022-05-06 10:38:49 +00:00
..
main hello_world: fix incorrect printf format 2022-05-06 10:38:49 +00:00
CMakeLists.txt [examples]: removed hyphens 2021-10-09 13:58:24 +08:00
example_test.py ci: run Example_GENERIC for C3 2021-03-15 10:27:07 +08:00
README.md add new command to idf 2020-09-21 23:38:52 +02:00
sdkconfig.ci example_tests: Deletes usage esp32c3 ECO0 in CI (by default ECO3) 2021-09-24 13:55:07 +08:00

Hello World Example

Starts a FreeRTOS task to print "Hello World".

(See the README.md file in the upper level 'examples' directory for more information about examples.)

How to use example

Follow detailed instructions provided specifically for this example.

Select the instructions depending on Espressif chip installed on your development board:

Example folder contents

The project hello_world contains one source file in C language hello_world_main.c. The file is located in folder main.

ESP-IDF projects are built using CMake. The project build configuration is contained in CMakeLists.txt files that provide set of directives and instructions describing the project's source files and targets (executable, library, or both).

Below is short explanation of remaining files in the project folder.

├── CMakeLists.txt
├── example_test.py            Python script used for automated example testing
├── main
│   ├── CMakeLists.txt
│   ├── component.mk           Component make file
│   └── hello_world_main.c
├── Makefile                   Makefile used by legacy GNU Make
└── README.md                  This is the file you are currently reading

For more information on structure and contents of ESP-IDF projects, please refer to Section Build System of the ESP-IDF Programming Guide.

Troubleshooting

  • Program upload failure

    • Hardware connection is not correct: run idf.py -p PORT monitor, and reboot your board to see if there are any output logs.
    • The baud rate for downloading is too high: lower your baud rate in the menuconfig menu, and try again.

Technical support and feedback

Please use the following feedback channels:

  • For technical queries, go to the esp32.com forum
  • For a feature request or bug report, create a GitHub issue

We will get back to you as soon as possible.