History

Darian Leung 9d63e1da4a New Task Watchdog API (Revert of Revert) This commit reverts the revert on the new task watchdog API. It also fixes the following bug which caused the reversion. - sdkconfig TASK_WDT_TIMEOUT_S has been reverted from the unit of ms back to the unit of seconds. Fixes bug where projects using the new API without rebuilding sdkconfig would cause the old default value of 5 to be interpreted in ms. This commit also adds the following features to the task watchdog - Updated idle hook registration to be compatible with dual core hooks - Updated dual core hooks to support deregistration for cpu - Legacy mode has been removed and esp_task_wdt_feed() is now replaced by esp_task_wdt_reset(). esp_task_wdt_feed() is deprecated - Idle hooks to reset are now registered/deregistered when the idle tasks are added/deleted from the Task Watchdog instead of at Task Watchdog init/deinit - Updated example		2017-11-02 16:47:51 +08:00
..
bluetooth	Merge branch 'bugfix/btdm_modify_close_disconnect_event_params' into 'master'	2017-11-01 11:01:36 +08:00
ethernet	ethernet: remove CONFIG_ETHERNET	2017-08-18 08:31:43 +05:30
get-started	sdkconfig: Remove rest of the references to WIFI_ENABLED	2017-08-16 15:55:42 +05:30
performance	example: optimize the robust of TCP connect	2017-08-10 18:19:50 +08:00
peripherals	Merge branch 'feature/docs_update_timer_api' into 'master'	2017-10-27 13:31:18 +08:00
protocols	test: add test for https_request	2017-10-31 17:42:20 +08:00
storage	examples/sdmmc: enable internal pull-ups in SD mode	2017-10-13 08:21:06 +08:00
system	New Task Watchdog API (Revert of Revert)	2017-11-02 16:47:51 +08:00
wifi	Merge branch 'feature/dfs' into 'master'	2017-10-22 12:34:11 +08:00
README.md	examples: Standardise naming of files, symbols, etc. in examples	2017-03-27 17:42:05 +11:00

README.md

Examples

This directory contains a growing number of simple example projects for esp-idf. These are intended to show basic esp-idf functionality, and to provide you can use for your own projects.

Using Examples

Building examples is the same as building any other project:

Follow the setup instructions in the top-level esp-idf README.
Set IDF_PATH environment variable to point to the path to the esp-idf top-level directory.
Change into the directory of the example you'd like to build.
make menuconfig to configure the example. Most examples require a simple WiFi SSID & password via this configuration.
make to build the example.
Follow the printed instructions to flash, or run make flash.

Copying Examples

Each example is a standalone project. The examples do not have to be inside the esp-idf directory. You can copy an example directory to anywhere on your computer in order to make a copy that you can modify and work with.

The IDF_PATH environment variable is the only thing that connects the example to the rest of the esp-idf system.

If you're looking for a more bare-bones project to start from, try esp-idf-template.

Contributing Examples

If you have a new example you think we'd like, please consider sending it to us as a Pull Request.

Please read the esp-idf CONTRIBUTING.rst file which lays out general contribution rules.

In addition, here are some tips for creating good examples:

A good example is documented and the basic options can be configured.
A good example does not contain a lot of code. If there is a lot of generic code in the example, consider refactoring that code into a standalone component and then use the component's API in your example.
Names (of files, functions, variables, etc.) inside examples should be distinguishable from names of other parts of IDF (ideally, use example in names.)
Functions and variables used inside examples should be declared static where possible.
Examples should demonstrate one distinct thing each. Avoid multi-purposed "demo" examples, split these into multiple examples instead.
Examples must be licensed under the Apache License 2.0 or (preferably for examples) if possible you can declare the example to be Public Domain / Creative Commons Zero.