Mirror/AI-on-the-edge-device-docs
1
0
Fork 0
mirror of https://github.com/jomjol/AI-on-the-edge-device-docs.git synced 2025-12-10 21:46:57 +03:00
Code Issues Packages Projects Releases Wiki Activity

Deployed 0cd98c6 with MkDocs version: 1.6.1

Browse Source
This commit is contained in:
github-actions[bot]
2025-10-30 23:07:10 +00:00
parent 1cf6dd2f0a
commit 15be0aba0d
23 changed files with 293 additions and 259 deletions
Download Patch File Download Diff File Expand all files Collapse all files

122
Frequent-Reboots/index.html
View File

@@ -450,7 +450,7 @@
</label>
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix="">
<li class="md-nav__item">
<a class="md-nav__link" href="#sporadic-random-reboots">1.0.1
<a class="md-nav__link" href="#sporadic-random-reboots">1.1
<span class="md-ellipsis">
Sporadic random reboots
</span>
@@ -458,14 +458,15 @@
<nav aria-label="Sporadic random reboots" class="md-nav">
<ul class="md-nav__list">
<li class="md-nav__item">
<a class="md-nav__link" href="#system-instabilities">1.0.1.0.1
<a class="md-nav__link" href="#system-instabilities">1.1.1
<span class="md-ellipsis">
System instabilities
</span>
</a>
</li>
<nav aria-label="System instabilities" class="md-nav">
<ul class="md-nav__list">
<li class="md-nav__item">
<a class="md-nav__link" href="#overload-during-html-access">1.0.1.1
<a class="md-nav__link" href="#overload-during-html-access">1.1.1.1
<span class="md-ellipsis">
Overload during HTML access
</span>
@@ -473,7 +474,7 @@
<nav aria-label="Overload during HTML access" class="md-nav">
<ul class="md-nav__list">
<li class="md-nav__item">
<a class="md-nav__link" href="#bad-or-insufficient-power-supply">1.0.1.1.1
<a class="md-nav__link" href="#bad-or-insufficient-power-supply">1.1.1.1.1
<span class="md-ellipsis">
Bad or insufficient power supply
</span>
@@ -486,7 +487,7 @@
</nav>
</li>
<li class="md-nav__item">
<a class="md-nav__link" href="#repeating-boot-loops">1.0.2
<a class="md-nav__link" href="#repeating-boot-loops">1.1.2
<span class="md-ellipsis">
Repeating boot loops
</span>
@@ -494,7 +495,7 @@
<nav aria-label="Repeating boot loops" class="md-nav">
<ul class="md-nav__list">
<li class="md-nav__item">
<a class="md-nav__link" href="#sd-card-related-issues">1.0.2.0.1
<a class="md-nav__link" href="#sd-card-related-issues">1.1.2.1
<span class="md-ellipsis">
SD card related issues
</span>
@@ -502,21 +503,22 @@
<nav aria-label="SD card related issues" class="md-nav">
<ul class="md-nav__list">
<li class="md-nav__item">
<a class="md-nav__link" href="#sd-card-wrong-filesystem-only-fat32-is-supported">1.0.2.0.1.1
<a class="md-nav__link" href="#sd-card-wrong-filesystem-only-fat32-is-supported">1.1.2.1.1
<span class="md-ellipsis">
SD card: Wrong filesystem (only FAT32 is supported)
</span>
</a>
</li>
<nav aria-label="SD card: Wrong filesystem (only FAT32 is supported)" class="md-nav">
<ul class="md-nav__list">
<li class="md-nav__item">
<a class="md-nav__link" href="#sd-card-not-detected-not-supported">1.0.2.0.1.2
<a class="md-nav__link" href="#sd-card-not-detected-not-supported">1.1.2.1.1.1
<span class="md-ellipsis">
SD card not detected / not supported
</span>
</a>
</li>
<li class="md-nav__item">
<a class="md-nav__link" href="#sd-card-detected-but-files-are-not-readable-writeable">1.0.2.0.1.3
<a class="md-nav__link" href="#sd-card-detected-but-files-are-not-readable-writeable">1.1.2.1.1.2
<span class="md-ellipsis">
SD card detected but files are not readable / writeable
</span>
@@ -526,7 +528,7 @@
</nav>
</li>
<li class="md-nav__item">
<a class="md-nav__link" href="#ram-related-issues">1.0.2.0.2
<a class="md-nav__link" href="#ram-related-issues">1.1.2.1.2
<span class="md-ellipsis">
RAM related issues
</span>
@@ -534,7 +536,7 @@
<nav aria-label="RAM related issues" class="md-nav">
<ul class="md-nav__list">
<li class="md-nav__item">
<a class="md-nav__link" href="#too-less-external-ram-psram">1.0.2.0.2.1
<a class="md-nav__link" href="#too-less-external-ram-psram">1.1.2.1.2.1
<span class="md-ellipsis">
Too less external RAM (PSRAM)
</span>
@@ -544,7 +546,7 @@
</nav>
</li>
<li class="md-nav__item">
<a class="md-nav__link" href="#configuration-related-issues">1.0.2.0.3
<a class="md-nav__link" href="#configuration-related-issues">1.1.2.1.3
<span class="md-ellipsis">
Configuration related issues
</span>
@@ -552,14 +554,14 @@
<nav aria-label="Configuration related issues" class="md-nav">
<ul class="md-nav__list">
<li class="md-nav__item">
<a class="md-nav__link" href="#folders-and-files-missing">1.0.2.0.3.1
<a class="md-nav__link" href="#folders-and-files-missing">1.1.2.1.3.1
<span class="md-ellipsis">
Folders and files missing
</span>
</a>
</li>
<li class="md-nav__item">
<a class="md-nav__link" href="#cnn-model-file-not-available-corrupt">1.0.2.0.3.2
<a class="md-nav__link" href="#cnn-model-file-not-available-corrupt">1.1.2.1.3.2
<span class="md-ellipsis">
CNN model file not available / corrupt
</span>
@@ -574,6 +576,12 @@
</ul>
</nav>
</li>
</ul>
</nav>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
<a class="md-nav__link" href="../Demo-Mode/">
<span class="md-ellipsis">
@@ -784,7 +792,7 @@
</label>
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix="">
<li class="md-nav__item">
<a class="md-nav__link" href="#sporadic-random-reboots">1.0.1
<a class="md-nav__link" href="#sporadic-random-reboots">1.1
<span class="md-ellipsis">
Sporadic random reboots
</span>
@@ -792,14 +800,15 @@
<nav aria-label="Sporadic random reboots" class="md-nav">
<ul class="md-nav__list">
<li class="md-nav__item">
<a class="md-nav__link" href="#system-instabilities">1.0.1.0.1
<a class="md-nav__link" href="#system-instabilities">1.1.1
<span class="md-ellipsis">
System instabilities
</span>
</a>
</li>
<nav aria-label="System instabilities" class="md-nav">
<ul class="md-nav__list">
<li class="md-nav__item">
<a class="md-nav__link" href="#overload-during-html-access">1.0.1.1
<a class="md-nav__link" href="#overload-during-html-access">1.1.1.1
<span class="md-ellipsis">
Overload during HTML access
</span>
@@ -807,7 +816,7 @@
<nav aria-label="Overload during HTML access" class="md-nav">
<ul class="md-nav__list">
<li class="md-nav__item">
<a class="md-nav__link" href="#bad-or-insufficient-power-supply">1.0.1.1.1
<a class="md-nav__link" href="#bad-or-insufficient-power-supply">1.1.1.1.1
<span class="md-ellipsis">
Bad or insufficient power supply
</span>
@@ -820,7 +829,7 @@
</nav>
</li>
<li class="md-nav__item">
<a class="md-nav__link" href="#repeating-boot-loops">1.0.2
<a class="md-nav__link" href="#repeating-boot-loops">1.1.2
<span class="md-ellipsis">
Repeating boot loops
</span>
@@ -828,7 +837,7 @@
<nav aria-label="Repeating boot loops" class="md-nav">
<ul class="md-nav__list">
<li class="md-nav__item">
<a class="md-nav__link" href="#sd-card-related-issues">1.0.2.0.1
<a class="md-nav__link" href="#sd-card-related-issues">1.1.2.1
<span class="md-ellipsis">
SD card related issues
</span>
@@ -836,21 +845,22 @@
<nav aria-label="SD card related issues" class="md-nav">
<ul class="md-nav__list">
<li class="md-nav__item">
<a class="md-nav__link" href="#sd-card-wrong-filesystem-only-fat32-is-supported">1.0.2.0.1.1
<a class="md-nav__link" href="#sd-card-wrong-filesystem-only-fat32-is-supported">1.1.2.1.1
<span class="md-ellipsis">
SD card: Wrong filesystem (only FAT32 is supported)
</span>
</a>
</li>
<nav aria-label="SD card: Wrong filesystem (only FAT32 is supported)" class="md-nav">
<ul class="md-nav__list">
<li class="md-nav__item">
<a class="md-nav__link" href="#sd-card-not-detected-not-supported">1.0.2.0.1.2
<a class="md-nav__link" href="#sd-card-not-detected-not-supported">1.1.2.1.1.1
<span class="md-ellipsis">
SD card not detected / not supported
</span>
</a>
</li>
<li class="md-nav__item">
<a class="md-nav__link" href="#sd-card-detected-but-files-are-not-readable-writeable">1.0.2.0.1.3
<a class="md-nav__link" href="#sd-card-detected-but-files-are-not-readable-writeable">1.1.2.1.1.2
<span class="md-ellipsis">
SD card detected but files are not readable / writeable
</span>
@@ -860,7 +870,7 @@
</nav>
</li>
<li class="md-nav__item">
<a class="md-nav__link" href="#ram-related-issues">1.0.2.0.2
<a class="md-nav__link" href="#ram-related-issues">1.1.2.1.2
<span class="md-ellipsis">
RAM related issues
</span>
@@ -868,7 +878,7 @@
<nav aria-label="RAM related issues" class="md-nav">
<ul class="md-nav__list">
<li class="md-nav__item">
<a class="md-nav__link" href="#too-less-external-ram-psram">1.0.2.0.2.1
<a class="md-nav__link" href="#too-less-external-ram-psram">1.1.2.1.2.1
<span class="md-ellipsis">
Too less external RAM (PSRAM)
</span>
@@ -878,7 +888,7 @@
</nav>
</li>
<li class="md-nav__item">
<a class="md-nav__link" href="#configuration-related-issues">1.0.2.0.3
<a class="md-nav__link" href="#configuration-related-issues">1.1.2.1.3
<span class="md-ellipsis">
Configuration related issues
</span>
@@ -886,14 +896,14 @@
<nav aria-label="Configuration related issues" class="md-nav">
<ul class="md-nav__list">
<li class="md-nav__item">
<a class="md-nav__link" href="#folders-and-files-missing">1.0.2.0.3.1
<a class="md-nav__link" href="#folders-and-files-missing">1.1.2.1.3.1
<span class="md-ellipsis">
Folders and files missing
</span>
</a>
</li>
<li class="md-nav__item">
<a class="md-nav__link" href="#cnn-model-file-not-available-corrupt">1.0.2.0.3.2
<a class="md-nav__link" href="#cnn-model-file-not-available-corrupt">1.1.2.1.3.2
<span class="md-ellipsis">
CNN model file not available / corrupt
</span>
@@ -907,6 +917,12 @@
</li>
</ul>
</nav>
</li>
</ul>
</nav>
</li>
</ul>
</nav>
</div>
</div>
</div>
@@ -927,7 +943,7 @@
<li>Repeating boot loops (reoccuring, always stop working after same precondition)</li>
</ol>
<hr/>
<h3 id="sporadic-random-reboots"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.1</span> Sporadic random reboots</h3>
<h2 id="sporadic-random-reboots"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.1</span> Sporadic random reboots</h2>
<p>Sporadic random reboots could have the following reasons:</p>
<ul>
<li>In general: Unstable system due to software issues (e.g. overload during HTML access, ...)
@@ -936,8 +952,8 @@
--&gt; The power supply need to stable to ensure proper operation of the device. If it's not stable the device tents to sporadic reboots (brownout detection)</li>
</ul>
<p>In general: There are several mechanisms in the firmware (like saving previous values), to have a "smooth" reboot without too many notable disturbance.</p>
<h5 id="system-instabilities"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.1.0.1</span> System instabilities</h5>
<p>If your system is sometimes running smoothly over several runs and sometimes reboots obviously randomly, you have an partially unstable device. </p>
<h3 id="system-instabilities"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.1.1</span> System instabilities</h3>
<p>If your system is sometimes running smoothly over several runs and sometimes reboots obviously randomly, you have an partially unstable device.</p>
<p>You can check this in the standard log file on the SD card:</p>
<div class="language-text highlight"><pre><span></span><code><span id="__span-0-1"><a href="#__codelineno-0-1" id="__codelineno-0-1" name="__codelineno-0-1"></a>2021-12-26T06:34:09: task_autodoFlow - round done
</span><span id="__span-0-2"><a href="#__codelineno-0-2" id="__codelineno-0-2" name="__codelineno-0-2"></a>2021-12-26T06:34:09: CPU Temperature: 56.1
@@ -945,40 +961,40 @@
</span></code></pre></div>
<p>Here you see, that the round #23 is starting, so obviously there were no reboots in the last 22 rounds. There is hardware (ESP32CAM), where only 2-3 stable rounds are possible and others, where way more than 100 rounds without any reboots is possible.
There is noting you can do about it, beside testing different hardware.</p>
<h4 id="overload-during-html-access"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.1.1</span> Overload during HTML access</h4>
<p>If you frequently access the web server over HTML requests, the firmware tends to reboot. This especially happens during the first run and when the ESP32 is busy with the digitization flow. </p>
<h4 id="overload-during-html-access"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.1.1.1</span> Overload during HTML access</h4>
<p>If you frequently access the web server over HTML requests, the firmware tends to reboot. This especially happens during the first run and when the ESP32 is busy with the digitization flow.</p>
<p>The reason for this are running out of memory during a flow, minor memory leakage in combination with missing error handling.</p>
<p>There is noting you can do about this kind of reboot, beside two thing:</p>
<ol>
<li>Support the firmware development with improved and tested part of code</li>
<li>Be patient :-)</li>
</ol>
<h5 id="bad-or-insufficient-power-supply"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.1.1.1</span> Bad or insufficient power supply</h5>
<h5 id="bad-or-insufficient-power-supply"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.1.1.1.1</span> Bad or insufficient power supply</h5>
<p>A good and stabilized power supply is essential to have error free operation. The device is quite picky in terms of proper power supply. Especially the wifi module have some load spikes which the power supply needs to cover. If the power is not stable enough, the brwonout mechanism is protecting against strange behaviour and force a reboot whenever the voltage drops below a specific level. You can see this in random reboots which indication is logfile: --&gt; Reset reason: Brownout</p>
<h3 id="repeating-boot-loops"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.2</span> Repeating boot loops</h3>
<h3 id="repeating-boot-loops"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.1.2</span> Repeating boot loops</h3>
<p>Repeating boot loops at the same situation during the flow has a systematic problem either in the hardware or the configuration. It usually happens during initialization state or processing the first round as there all needed parts of the firmware have been loaded for the first time.</p>
<p>To identify the root cause the logfiles, the reduced web interface, the red board LED or the serial log of the UART interface (no remote access, USB access needed) is helpful. </p>
<p>To identify the root cause the logfiles, the reduced web interface, the red board LED or the serial log of the UART interface (no remote access, USB access needed) is helpful.</p>
<p>Possible issues:</p>
<ul>
<li>SD card related issues</li>
<li>RAM related issues</li>
<li>Configuration related issues</li>
</ul>
<h5 id="sd-card-related-issues"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.2.0.1</span> SD card related issues</h5>
<h4 id="sd-card-related-issues"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.1.2.1</span> SD card related issues</h4>
<p>The ESP32CAM is a little bit "picky" with the supported SD cards. Due to the limited availability of GPIOs the SD card can only be accessed via 1-wire mode. Therefore not all SD cards are supported. The following error cases can occur:</p>
<h6 id="sd-card-wrong-filesystem-only-fat32-is-supported"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.2.0.1.1</span> SD card: Wrong filesystem (only FAT32 is supported)</h6>
<h5 id="sd-card-wrong-filesystem-only-fat32-is-supported"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.1.2.1.1</span> SD card: Wrong filesystem (only FAT32 is supported)</h5>
<p>If this SD card error is detected only the following indications are available. No web interface will be accessible.</p>
<ul>
<li>Red board LED is blinking. The blinking codes are described here: <a href="https://jomjol.github.io/AI-on-the-edge-device-docs/StatusLED-BlinkCodes/">Status LED Blinkcodes</a></li>
<li>Error messages on serial log (UART interface)</li>
</ul>
<h6 id="sd-card-not-detected-not-supported"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.2.0.1.2</span> SD card not detected / not supported</h6>
<h6 id="sd-card-not-detected-not-supported"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.1.2.1.1.1</span> SD card not detected / not supported</h6>
<p>If this SD card error is detected the following indication are available. No web interface will be accessible.</p>
<ul>
<li>Red board LED is blinking. The blinking codes are described here: <a href="https://jomjol.github.io/AI-on-the-edge-device-docs/StatusLED-BlinkCodes/">Status LED Blinkcodes</a></li>
<li>Error messages on serial log (UART interface)</li>
</ul>
<h6 id="sd-card-detected-but-files-are-not-readable-writeable"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.2.0.1.3</span> SD card detected but files are not readable / writeable</h6>
<h6 id="sd-card-detected-but-files-are-not-readable-writeable"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.1.2.1.1.2</span> SD card detected but files are not readable / writeable</h6>
<p>The SD card is detected, but the files cannot be read or written. A basic SD card check for SD reading / writing is performed on every boot. This not 100% guarantee that SD card is working but it's at least a indication.</p>
<p>If this SD card error is detected the following indications are available:</p>
<ul>
@@ -987,10 +1003,10 @@ There is noting you can do about it, beside testing different hardware.</p>
<li>Red board LED is blinking. The blinking codes are described here: <a href="https://jomjol.github.io/AI-on-the-edge-device-docs/StatusLED-BlinkCodes/">Status LED Blinkcodes</a></li>
<li>Error messages on serial log (UART interface)</li>
</ul>
<h5 id="ram-related-issues"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.2.0.2</span> RAM related issues</h5>
<h5 id="ram-related-issues"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.1.2.1.2</span> RAM related issues</h5>
<p>In order to run the firmware, 4 MB of external RAM (PSRAM) are mandatory. Usually, the ESP32CAM is equipped with 8MB (64Mbit) PSRAM chip, whereof only 4MB can be used effectively (direct addressable).
Unfortunately, there is hardware around, where no PSRAM or only 2MB of PSRAM is present - <strong>even if you have bought a device where a 8MB PSRAM was promoted</strong>. These modules are not suiable for this firmware because the external RAM is needed to handle the CNN files and camera images. There is nothing to do, than to buy a new ESP32CAM with <strong>really</strong> 64MBit of PSRAM. </p>
<h6 id="too-less-external-ram-psram"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.2.0.2.1</span> Too less external RAM (PSRAM)</h6>
Unfortunately, there is hardware around, where no PSRAM or only 2MB of PSRAM is present - <strong>even if you have bought a device where a 8MB PSRAM was promoted</strong>. These modules are not suiable for this firmware because the external RAM is needed to handle the CNN files and camera images. There is nothing to do, than to buy a new ESP32CAM with <strong>really</strong> 64MBit of PSRAM.</p>
<h6 id="too-less-external-ram-psram"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.1.2.1.2.1</span> Too less external RAM (PSRAM)</h6>
<p>During the boot process the available RAM is going to be checked.</p>
<p>If there is too less RAM (PSRAM or total HEAP &lt; 4MB) detected, the follwoing indications are available:</p>
<ul>
@@ -999,8 +1015,8 @@ Unfortunately, there is hardware around, where no PSRAM or only 2MB of PSRAM is
<li>Red board LED is blinking. The blinking codes are described here: <a href="https://jomjol.github.io/AI-on-the-edge-device-docs/StatusLED-BlinkCodes/">Status LED Blinkcodes</a></li>
<li>Error messages on serial log (UART interface)</li>
</ul>
<h5 id="configuration-related-issues"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.2.0.3</span> Configuration related issues</h5>
<h6 id="folders-and-files-missing"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.2.0.3.1</span> Folders and files missing</h6>
<h5 id="configuration-related-issues"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.1.2.1.3</span> Configuration related issues</h5>
<h6 id="folders-and-files-missing"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.1.2.1.3.1</span> Folders and files missing</h6>
<p>Most of the relevant folders and files are checked during boot. The complete list can be found here: <a href="https://jomjol.github.io/AI-on-the-edge-device-docs/Error-Codes/">Error codes on reduced webinterface</a></p>
<p>If a relevant folder or file is missing the following indications are available:</p>
<ul>
@@ -1009,13 +1025,13 @@ Unfortunately, there is hardware around, where no PSRAM or only 2MB of PSRAM is
<li>Red board LED is blinking. The blinking codes are described here: <a href="https://jomjol.github.io/AI-on-the-edge-device-docs/StatusLED-BlinkCodes/">Status LED Blinkcodes</a></li>
<li>Error messages on serial log (UART interface)</li>
</ul>
<h6 id="cnn-model-file-not-available-corrupt"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.0.2.0.3.2</span> CNN model file not available / corrupt</h6>
<h6 id="cnn-model-file-not-available-corrupt"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.1.2.1.3.2</span> CNN model file not available / corrupt</h6>
<p>Additionally for operation CNN model files on SD card are mandatory, one CNN model file for analog counter and for for digit numbers each.</p>
<ul>
<li><code>/config/XXXXX.tflite</code> (XXXXX is the file name, that is written in the <code>config.ini</code>)</li>
</ul>
<p>If the files which are configured in <code>config.ini</code> are not present or corrupt, the process is going to be interrupted (or at worst case a device crash occurs). Please check logs files to have an indicator for the root cause.</p>
<p>This a logfile extract (DEBUB log level) where digit CNN model file is not present. The system is initializing the system and trying to load the model files:
<p>This a logfile extract (DEBUB log level) where digit CNN model file is not present. The system is initializing the system and trying to load the model files:</p>
<div class="language-text highlight"><pre><span></span><code><span id="__span-1-1"><a href="#__codelineno-1-1" id="__codelineno-1-1" name="__codelineno-1-1"></a>[0d00h05m11s] 2023-03-27T12:25:14 [TFLITE] CTfLiteClass::LoadModel
</span><span id="__span-1-2"><a href="#__codelineno-1-2" id="__codelineno-1-2" name="__codelineno-1-2"></a>[0d00h05m11s] 2023-03-27T12:25:14 [TFLITE] CTfLiteClass::ReadFileToModel: /sdcard
</span><span id="__span-1-3"><a href="#__codelineno-1-3" id="__codelineno-1-3" name="__codelineno-1-3"></a>[0d00h05m11s] 2023-03-27T12:25:14 [PSRAM] Failed to allocate 0 bytes in PSRAM for 'TFLITE-&gt;modelfile'!
@@ -1032,12 +1048,12 @@ Unfortunately, there is hardware around, where no PSRAM or only 2MB of PSRAM is
</span><span id="__span-1-14"><a href="#__codelineno-1-14" id="__codelineno-1-14" name="__codelineno-1-14"></a>[0d00h05m12s] 2023-03-27T12:25:15 [TFLITE] CTfLiteClass::MakeAllocate
</span><span id="__span-1-15"><a href="#__codelineno-1-15" id="__codelineno-1-15" name="__codelineno-1-15"></a>[0d00h05m12s] 2023-03-27T12:25:15 [PSRAM] Freeing memory in PSRAM used for 'TFLITE-&gt;modelfile'...
</span><span id="__span-1-16"><a href="#__codelineno-1-16" id="__codelineno-1-16" name="__codelineno-1-16"></a>[0d00h05m12s] 2023-03-27T12:25:15 [PSRAM] Freeing memory in PSRAM used for 'TFLITE-&gt;tensor_arena'...
</span></code></pre></div></p>
</span></code></pre></div>
<ul>
<li>Bad config example:</li>
<li>
<p><code>[0d00h05m11s] 2023-03-27T12:25:14 [TFLITE] CTfLiteClass::ReadFileToModel: /sdcard</code>
--&gt; model file missing: check configuration or file presence </p>
--&gt; model file missing: check configuration or file presence</p>
</li>
<li>
<p>Good config example:</p>