esp_core_dump.h 2.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364
  1. // Copyright 2015-2016 Espressif Systems (Shanghai) PTE LTD
  2. //
  3. // Licensed under the Apache License, Version 2.0 (the "License");
  4. // you may not use this file except in compliance with the License.
  5. // You may obtain a copy of the License at
  6. // http://www.apache.org/licenses/LICENSE-2.0
  7. //
  8. // Unless required by applicable law or agreed to in writing, software
  9. // distributed under the License is distributed on an "AS IS" BASIS,
  10. // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  11. // See the License for the specific language governing permissions and
  12. // limitations under the License.
  13. #ifndef ESP_CORE_DUMP_H_
  14. #define ESP_CORE_DUMP_H_
  15. /**
  16. * @brief Initializes core dump module internal data.
  17. *
  18. * @note Should be called at system startup.
  19. */
  20. void esp_core_dump_init();
  21. /**
  22. * @brief Saves core dump to flash.
  23. *
  24. * The structure of data stored in flash is as follows:
  25. * | MAGIC1 |
  26. * | TOTAL_LEN | TASKS_NUM | TCB_SIZE |
  27. * | TCB_ADDR_1 | STACK_TOP_1 | STACK_END_1 | TCB_1 | STACK_1 |
  28. * . . . .
  29. * . . . .
  30. * | TCB_ADDR_N | STACK_TOP_N | STACK_END_N | TCB_N | STACK_N |
  31. * | MAGIC2 |
  32. * Core dump in flash consists of header and data for every task in the system at the moment of crash.
  33. * For flash data integrity control two magic numbers are used at the beginning and the end of core dump.
  34. * The structure of core dump data is described below in details.
  35. * 1) MAGIC1 and MAGIC2 are special numbers stored at the beginning and the end of core dump.
  36. * They are used to control core dump data integrity. Size of every number is 4 bytes.
  37. * 2) Core dump starts with header:
  38. * 2.1) TOTAL_LEN is total length of core dump data in flash including magic numbers. Size is 4 bytes.
  39. * 2.2) TASKS_NUM is the number of tasks for which data are stored. Size is 4 bytes.
  40. * 2.3) TCB_SIZE is the size of task's TCB structure. Size is 4 bytes.
  41. * 3) Core dump header is followed by the data for every task in the system.
  42. * Task data are started with task header:
  43. * 3.1) TCB_ADDR is the address of TCB in memory. Size is 4 bytes.
  44. * 3.2) STACK_TOP is the top of task's stack (address of the topmost stack item). Size is 4 bytes.
  45. * 3.2) STACK_END is the end of task's stack (address from which task's stack starts). Size is 4 bytes.
  46. * 4) Task header is followed by TCB data. Size is TCB_SIZE bytes.
  47. * 5) Task's stack is placed after TCB data. Size is (STACK_END - STACK_TOP) bytes.
  48. */
  49. void esp_core_dump_to_flash();
  50. /**
  51. * @brief Print base64-encoded core dump to UART.
  52. *
  53. * The structure of core dump data is the same as for data stored in flash (@see esp_core_dump_to_flash) with some notes:
  54. * 1) Magic numbers are not present in core dump printed to UART.
  55. * 2) Since magic numbers are omitted TOTAL_LEN does not include their size.
  56. * 3) Printed base64 data are surrounded with special messages to help user recognize the start and end of actual data.
  57. */
  58. void esp_core_dump_to_uart();
  59. #endif