Skip to content

Latest commit

 

History

History
193 lines (121 loc) · 6.89 KB

ADF_TEMPLATE_EXAMPLE_README_EN.md

File metadata and controls

193 lines (121 loc) · 6.89 KB
Raw

Note that this is a template for an ESP-ADF example README.md file. When using this template, replace all these emphasised placeholders with example-specific content.

Example Title

Link to Chinese Version

Select one of the following to describe the difficulty level.

  • Basic Example: alt text - to get started
  • Regular Example: alt text - demonstrates functionality of ESP-ADF or audio board
  • Complex Example: alt text - like regular example but requires more configuration steps, interaction with other programs, setting up some cloud accounts, or more user expertise

Example Brief

  • Introduce the realization of the example program from a functional point of view. For instance, this example uses different decoders to play music in different formats from the microSD card.
  • From a technical point of view, describe the main technical functions demonstrated. For instance, this example demonstrates the use of pipeline and element, and how element obtains data directly from callback.

Resources

It's optional, such as RAM, CPU loading.

Prerequisites

  • It's optional
  • Guide first-time users to run get started example first
  • Guide users to learn the background

Folder contents

  • It's optional
  • It is short explanation of remaining files in the project folder and the folder structure. Below is the example of the play_mp3 folder.
├── components
│   └── my_board
│       ├── my_board_v1_0
│       │   ├── board.c
│       │   ├── board.h
│       │   ├── board_def.h
│       │   └── board_pins_config.c
│       ├── my_codec_driver
│       │   ├── new_codec.h
│       │   └── new_codec.c
│       ├── CMakeLists.txt
│       ├── component.mk
│       └── Kconfig.projbuild
├── CMakeLists.txt
├── example_test.py            Python script used for automated example testing
├── main
│   ├── CMakeLists.txt
│   ├── component.mk           Component make file
│   ├── adf_music.mp3          Test music file
│   └── play_mp3_example.c
├── Makefile                   Makefile used by legacy GNU Make
└── README.md                  This is the file you are currently reading

Environment Setup

Hardware Required

List all the hardware, such as development boards, speakers, microSD card, LCD module, camera module, Bluetooth speaker, and so on

Additional Requirements

  • It's optional
  • Audio files, SIP server, DLNA app and so on, such as Baidu Cloud's profile or Amazon's token.

Build and Flash

Default IDF Branch

Select either of the two expressions below depending on the actual situation.

This example supports IDF release/v[x.y] and later branches. By default, it runs on ADF's built-in branch $ADF_PATH/esp-idf.

This example supports IDF release/v[x.y] and later branches. By default, it runs on IDF release/v[x.y].

Other Special IDF Branches

  • When required to select a special IDF/ADF version branch, which must be clearly pointed out and described

  • For example, DU1906 project selects the IDF branch audio/stack_on_psram_v3.3 to compile

    cd $IDF_PATH
git checkout master
git pull
git checkout audio/stack_on_psram_v3.3
git submodule update --init --recursive

Configuration

  • Describe important items to configure in menuconfig, such as long file name support for FatFs, selection of compatible audio board, chip type, PSRAM clock, Wi-Fi/LWIP parameters and so on. Below is an example.

    Component config > FAT Filesystem support > Long filename support

  • Configuration of other software if required, such as specifying a patch

Build and Flash

Command to build the example

  • Legacy GNU Make command: make
  • CMake command: idf.py build

Command to flash the example

  • Legacy GNU Make command: make flash monitor
  • CMake command: idf.py -p PORT flash monitor

For full steps to configure and build an ESP-IDF project, please go to ESP-IDF Programming Guide and select the chip and version in the upper left corner of the page.

How to Use the Example

Example Functionality

  • To explain how to use this example, what features are supported and what results to get. For example, describe what keys or speech commands are supported. Below is the speech interaction with DuerOS.

    • "小度小度"，"在呢"，"讲个笑话"
    • "小度小度"，"在呢"，"上海天气怎么样？"
    • "小度小度"，"在呢"，"播放一首歌"
    • "小度小度"，"在呢"，"百度百科乐鑫信息科技"

  • If any other items are needed, such as server, Bluetooth device, app, second chip, do mention them here. Include links if applicable. Explain how to set them up. Below is an example.

    • Please run the HTTP server of pipeline_raw_http. This server is created on PC by running python server.py to receive data.

Example Log

The complete log is as follows:

I (64) boot: Chip Revision: 3
I (35) boot: ESP-IDF v3.3.1-203-g0c1859a5a 2nd stage bootloader
I (35) boot: compile time 21:43:15
I (35) boot: Enabling RNG early entropy source...
I (41) qio_mode: Enabling default flash chip QIO
I (46) boot: SPI Speed      : 80MHz
I (50) boot: SPI Mode       : QIO
I (54) boot: SPI Flash Size : 8MB
I (58) boot: Partition Table:
I (62) boot: ## Label            Usage          Type ST Offset   Length
I (69) boot:  0 nvs              WiFi data        01 02 00009000 00004000
I (76) boot:  1 otadata          OTA data         01 00 0000d000 00002000
I (84) boot:  2 phy_init         RF data          01 01 0000f000 00001000
I (91) boot:  3 ota_0            OTA app          00 10 00010000 00280000
I (99) boot:  4 ota_1            OTA app          00 11 00290000 00280000
I (106) boot:  5 dsp_bin          Unknown data     01 24 00510000 00280000
I (114) boot:  6 profile          Unknown data     01 29 00790000 00001000
I (121) boot:  7 flash_tone       Unknown data     01 27 00791000 00060000
I (129) boot: End of partition table

References

Troubleshooting

It's optional. If there are any likely problems or errors which many users might encounter, mention them here.

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.