@@ -74,7 +74,27 @@ We assume you have a working setup for the
74
74
75
75
That's it! You should be good to go!
76
76
77
- ### Building the demo app:
77
+ ### Memfault Project Key
78
+
79
+ An API key will need to be configured for Memfault HTTP client to communicate
80
+ with Memfault's web services. Go to https://app.memfault.com/ , navigate to the
81
+ project you want to use and select 'Settings'. Copy the 'Project Key', and
82
+ configure it; either by running ` idf.py menuconfig ` and setting the
83
+ ` MEMFAULT_PROJECT_KEY ` config value, or by inserting to ` sdkconfig.defaults ` :
84
+
85
+ ``` kconfig
86
+ CONFIG_MEMFAULT_PROJECT_KEY="<YOUR PROJECT KEY>"
87
+ ```
88
+
89
+ > Note: when doing a clean build, or a build in CI, another option is to place
90
+ > the Project Key in a second ` sdkconfig.defaults ` file, for example:
91
+ >
92
+ > ``` bash
93
+ > ❯ echo CONFIG_MEMFAULT_PROJECT_KEY=\" < YOUR PROJECT KEY> \" > sdkconfig.extra
94
+ > ❯ idf.py build -DSDKCONFIG_DEFAULTS=" sdkconfig.defaults;sdkconfig.extra"
95
+ > ` ` `
96
+
97
+ # ## Building the demo app
78
98
79
99
using pyinvoke:
80
100
@@ -183,8 +203,13 @@ I (77840) mflt: Has coredump with size: 768
183
203
#### Uploading Symbols
184
204
185
205
Memfault needs the symbols for the firmware in order to analyze the coredump.
186
- The ESP32 SDK demo app symbol file can be found at:
187
- ` /path/to/examples/esp32/apps/memfault_demo_app/build/memfault-esp32-demo-app.elf `
206
+ The ESP32 SDK demo app symbol file can be found in the build folder:
207
+
208
+ ` apps/memfault_demo_app/build/memfault-esp32-demo-app.elf.memfault_log_fmt `
209
+
210
+ > Note: the file to be uploaded is
211
+ > ` memfault-esp32-demo-app.elf.memfault_log_fmt ` , _ not_
212
+ > ` memfault-esp32-demo-app.elf ` , when using compact logs!
188
213
189
214
This ELF file contains the symbols (debug information) amongst other things.
190
215
0 commit comments