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.
5816 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
Ivan Grokhotkov f9f2937694 spi_flash: raise priority of the task performing spi_flash operation 
The fix is for the situation when cache disabling mechanism causes
a deadlock with user tasks. Situation is as follows:

1. spi_flash operation is started from low-priority task on CPU0
2. It uses IPC to wake up high-priority IPC1 task on CPU1, preventing
   all other tasks on CPU1 from running. This is needed to safely
   disable the cache.
3. While the task which started spi_flash operation is waiting for IPC1
   task to acknowledge that CPU1 is not using cache anymore, it is
   preempted by a higher priority application task ("app0").
4. Task app0 busy-waits for some operation on CPU1 to complete. But
   since application tasks are blocked out by IPC1 task, this never
   happens. Since app0 is busy-waiting, the task doing spi flash
   operation never runs.

The more or less logical soltion to the problem would be to also do
cache disabling on CPU0 and the SPI flash operation itself from IPC0
task. However IPC0 task stack would need to be increased to allow doing
SPI flash operation (and IPC1 stack as well). This would waste some
memory. An alternative approach adopted in this fix is to call FreeRTOS
functions to temporary increase the priority of SPI flash operation task
to the same level as the IPC task.

Fixes https://github.com/espressif/arduino-esp32/issues/740
Fixes https://github.com/espressif/esp-idf/issues/1157
2018-07-01 20:44:42 +08:00
components spi_flash: raise priority of the task performing spi_flash operation 2018-07-01 20:44:42 +08:00
docs Merge branch 'bugfix/eclipse_regex' into 'master' 2018-06-27 09:38:47 +08:00
examples Merge branch 'bugfix/btdm_some_ble_hid_bugs' into 'master' 2018-06-29 15:36:53 +08:00
make Merge branch 'feature/expansion_space_for_bootloader' into 'master' 2018-06-18 12:34:53 +08:00
tools stop main thread when one failed 2018-06-26 11:02:23 +08:00
.editorconfig Add .editorconfig file 2017-12-18 12:47:30 +07:00
.gitignore gitignore: Add test_multi_heap_host 2018-05-22 12:09:30 +10:00
.gitlab-ci.yml CI: add stage host_test: 2018-06-25 15:20:58 +08:00
.gitmodules mbedtls: re-add version 2.9.0 as a submodule 2018-05-09 23:15:28 +08:00
add_path.sh Add espcoredump to the add_path shell helper 2017-02-12 22:48:41 +00:00
CONTRIBUTING.rst docs: Add "Creating Examples" docs page, template example README 2018-06-14 16:49:22 +10:00
Kconfig Kconfig: split out compiler options, add them to reference 2018-06-15 15:49:23 +08:00
Kconfig.compiler Kconfig: split out compiler options, add them to reference 2018-06-15 15:49:23 +08:00
LICENSE Initial public version 2016-08-17 23:08:22 +08:00
README.md docs: Switch base URL from esp-idf.readthedocs.io to docs.espressif.com 2018-06-19 11:23:33 +00:00

README.md

Espressif IoT Development Framework

alt text

ESP-IDF is the official development framework for the ESP32 chip.

Developing With the ESP-IDF

Setting Up ESP-IDF

See setup guides for detailed instructions to set up the ESP-IDF:

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 the Project

make menuconfig

  • Opens a text-based configuration menu for the project.
  • Use up & down arrow keys to navigate the menu.
  • Use Enter key to go into a submenu, Escape key to go out or to exit.
  • Type ? to see a help screen. Enter key exits the help screen.
  • Use Space key, or Y and N keys to enable (Yes) and disable (No) configuration items with checkboxes "[*]"
  • Pressing ? while highlighting a configuration item displays help about that item.
  • Type / to search the configuration items.

Once done configuring, press Escape multiple times to exit and say "Yes" to save the new configuration when prompted.

Compiling the Project

make all

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

Flashing the 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.

Viewing Serial Output

The make monitor target uses the idf_monitor tool to display serial output from the ESP32. idf_monitor also has a range of features to decode crash output and interact with the device. Check the documentation page for details.

Exit the monitor by typing Ctrl-].

To flash and monitor output in one pass, you can run:

make flash monitor

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.

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

Parallel Builds

ESP-IDF supports compiling multiple files in parallel, so all of the above commands can be run as make -jN where N is the number of parallel make processes to run (generally N should be equal to or one more than the number of CPU cores in your system.)

Multiple make functions can be combined into one. For example: to build the app & bootloader using 5 jobs in parallel, then flash everything, and then display serial output from the ESP32 run:

make -j5 flash monitor

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 0x8000 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/en/api-guides/partition-tables.rst file.

Erasing Flash

The make flash target does not erase the entire flash contents. However it is sometimes useful to set the device back to a totally erased state, particularly when making partition table changes or OTA app updates. To erase the entire flash, run make erase_flash.

This can be combined with other targets, ie make erase_flash flash will erase everything and then re-flash the new app, bootloader and partition table.

Resources