Crash_Override/OVMS3-idf
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
Espressif IoT Development Framework. Official development framework for ESP32.
1297 commits 10 branches 75 tags 114 MiB
C 91.5%
Python 3.7%
C++ 2.7%
CMake 0.7%
Assembly 0.5%
Other 0.7%
Go to file
Jiang Jiang Jian bd20288b81 Merge branch 'feature/btdm_bluedroid' into 'master' 
Feature/btdm bluedroid

This branch contain the bluedroid host code.
Currently,  Only GAP/GATT SERVER/GATT CLIENT release to users.
Actually, the content of the codes is further more than GAP/GATT and etc.
In this release version, users only need to concern about the APIs which are in "api/include/".

Now, suggestions in comment have been resolved are following:
1. The APIs use callback function. Ivan , Jeroen and me have discussed it. Currently the code will not be changed.
2. The APIs use OPEN/CLOSE. I have ask Ivan, besides bluedroid do this, we will keep the name.
3. Coding style. I have run format.sh to handle the style. And some spell error have been fixed.
4. APIs doxygen. I have clean the warning by doxygen. But bt.rst is still need to be completed.
5. Other comment without resolved face to face that I have to add response in the comment and fix them in the code
6. Fix some incorrect things. See the git log for details.

This 1st version of bluedroid release still have lots of things to do. But it can be done after this merge.
1. Compelete the BLUFI(Bluetooth config wifi connection) documents, security, application protocol and other.
2. Add SPP-LIKE profile.
3. Do more examples codes to cover most of the APIs.
4. Test and fix bug.

Another thing：
1. Do the document of APIs.(xml->bt.rst->html) 
(I will do this before merge as Ivan's suggestion)
This is already done. Besides, the union type in doxygen have something error. Ivan will fix it.



See merge request !239
2016-12-02 12:07:20 +08:00
components Merge branch 'feature/btdm_bluedroid' into 'master' 2016-12-02 12:07:20 +08:00
docs Merge branch 'feature/btdm_bluedroid' into 'master' 2016-12-02 12:07:20 +08:00
examples Merge branch 'feature/btdm_bluedroid' into 'master' 2016-12-02 12:07:20 +08:00
make Merge branch 'feature/sha_tls_integration' into 'master' 2016-11-25 10:12:29 +08:00
tools mbedtls tests: Add additional MPI (bignum), SHA tests 2016-11-25 19:21:49 +11:00
.gitignore add unit tests to esp-idf 2016-11-22 14:45:50 +08:00
.gitlab-ci.yml Merge branch 'bugfix/unit_test_run' into 'master' 2016-11-24 18:29:32 +08:00
.gitmodules Secure boot: initial image signature support 2016-11-14 11:08:42 +11:00
add_path.sh add_path.sh: Use non-bash-specific instructions 2016-09-12 18:39:20 +10:00
CONTRIBUTING.rst docs: Hyperlinks to guides 2016-11-21 10:24:12 +08:00
Kconfig build system: fix setting C**FLAGS from project makefile 2016-10-20 17:17:54 +08:00
LICENSE Initial public version 2016-08-17 23:08:22 +08:00
README.md Back to .md format 2016-11-01 01:20:04 +08:00

README.md

Using Espressif IoT Development Framework with the ESP32

alt text

Setting Up ESP-IDF

In the docs directory you will find per-platform setup guides:

Finding A Project

As well as the esp-idf-template project mentioned in the setup guide, esp-idf comes with some example projects in the examples directory.

Once you've found the project you want to work with, change to its directory and you can configure and build it:

Configuring your project

make menuconfig

Compiling your project

make all

... will compile app, bootloader and generate a partition table based on the config.

Flashing your project

When make all finishes, it will print a command line to use esptool.py to flash the chip. However you can also do this from make by running:

make flash

This will flash the entire project (app, bootloader and partition table) to a new chip. The settings for serial port flashing can be configured with make menuconfig.

You don't need to run make all before running make flash, make flash will automatically rebuild anything which needs it.

Compiling & Flashing Just the App

After the initial flash, you may just want to build and flash just your app, not the bootloader and partition table:

  • make app - build just the app.
  • make app-flash - flash just the app.

make app-flash will automatically rebuild the app if it needs it.

(There's no downside to reflashing the bootloader and partition table each time, if they haven't changed.)

The Partition Table

Once you've compiled your project, the "build" directory will contain a binary file with a name like "my_app.bin". This is an ESP32 image binary that can be loaded by the bootloader.

A single ESP32's flash can contain multiple apps, as well as many different kinds of data (calibration data, filesystems, parameter storage, etc). For this reason a partition table is flashed to offset 0x4000 in the flash.

Each entry in the partition table has a name (label), type (app, data, or something else), subtype and the offset in flash where the partition is loaded.

The simplest way to use the partition table is to make menuconfig and choose one of the simple predefined partition tables:

  • "Single factory app, no OTA"
  • "Factory app, two OTA definitions"

In both cases the factory app is flashed at offset 0x10000. If you make partition_table then it will print a summary of the partition table.

For more details about partition tables and how to create custom variations, view the docs/partition-tables.rst file.

Resources