The latest articles on DEV Community by Tomáš Pilný (@pilnytomas). https://dev.to/pilnytomas https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1021717%2Facec466e-a0f8-4866-b01e-619782dc7545.jpeg https://dev.to/pilnytomas en Tomáš Pilný Mon, 06 Feb 2023 13:42:26 +0000 https://dev.to/pilnytomas/how-to-compile-arduino-esp32-core-with-esplogx-3n50 https://dev.to/pilnytomas/how-to-compile-arduino-esp32-core-with-esplogx-3n50 <p><strong>Why?</strong><br> In Arduino IDE you can set the core debug level, however, this only sets debug level for files in Arduino-esp32 but the core which is distributed as a precompiled library in .sdk files, located in your Arduinio installation folder, is unaffected - the debug level remains the default “error”.</p> <p><strong>What?</strong><br> If you want to change the core code or debug level, you need to clone the repo: <a href="https://github.com/espressif/esp32-arduino-lib-builder" rel="noopener noreferrer">https://github.com/espressif/esp32-arduino-lib-builder</a>, make the modifications there, compile and apply the changes (automatically by the build script).</p> <p><strong>How?</strong><br> There are 2 basic approaches. Both of them involve editing file <code>esp32-arduino-lib-builder/configs/defconfig.common</code>.</p> <p>The first option is to edit the file directly and then build.<br> Later you can <code>git restore configs/defconfig.common</code> to go back.</p> <p>The second option is to copy the file <code>cp configs/defconfig.common configs/defconfig.debug</code>, edit the debug version and then compile.</p> <p>Open the defconfig file<br> <code>vim configs/defconfig.common</code> or <code>vim configs/defconfig.debug</code></p> <p>Edit <code>line 45</code> containing by default <code>CONFIG_LOG_DEFAULT_LEVEL_ERROR=y</code> to one of the following lines depending on your desired log level:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>CONFIG_LOG_DEFAULT_LEVEL_NONE=y # No output CONFIG_LOG_DEFAULT_LEVEL_ERROR=y # Errors - default CONFIG_LOG_DEFAULT_LEVEL_WARN=y # Warnings CONFIG_LOG_DEFAULT_LEVEL_INFO=y # Info CONFIG_LOG_DEFAULT_LEVEL_DEBUG=y # Debug CONFIG_LOG_DEFAULT_LEVEL_VERBOSE=y # Verbose - All of the above </code></pre> </div> <p>Then simply build the libs for all SoCs or one specific SoC. Note that building for all SoCs takes a lot of time, so if you work only with one specific SoC, build only for that one.<br> If you have copied the defconfig file and the debug settings are in file <code>configs/defconfig.debug</code> add flag <code>debug</code><br> example : <code>./build.sh debug</code><br> Build all SoCs: <code>./build.sh</code><br> Build only selected SoC: <code>./build.sh -t &lt;soc&gt;</code><br> The exact text to choose the SoC:</p> <ul> <li>esp32</li> <li>esp32s2</li> <li>esp32c3</li> <li>esp32s3 Example: <code>./build.sh -t esp32</code> A wrong format or non-existing SoC will result in the error <code>sed: can't read sdkconfig: No such file or directory</code> </li> </ul> gratitude