mirror of
https://github.com/jomjol/AI-on-the-edge-device-docs.git
synced 2025-12-07 12:07:01 +03:00
Update Error-Codes.md
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
# Reduced webinterface (only for error indication and tracing)
|
||||
# Reduced webinterface (error indication and tracing)
|
||||
|
||||
Whenever an error occurs during boot process which avoids loading of regular processing and regular webinterface, a reduced webinterface gets loaded to have at least some visual feedback and the possibilitiy to figure out the root cause by browsing the logfiles or trigger another OTA update.
|
||||
|
||||
@@ -6,11 +6,11 @@ The error code(s) get printed with specific error codes. This page lists the pos
|
||||
|
||||
Note: Here the error codes are defined in source code: [error codes](https://github.com/jomjol/AI-on-the-edge-device/blob/rolling/code/components/jomjol_helper/Helper.h).
|
||||
|
||||
# Critical Errors
|
||||
## Critical Errors
|
||||
Those Errors make the normal operation of the device impossible.
|
||||
Most likely they are caused by a hardware issue!
|
||||
|
||||
## `0x00000001` PSRAM bad
|
||||
### `0x00000001` PSRAM bad
|
||||
Your device most likely has no PSRAM at all or it is too small (needs to have at least 4 MBytes)!
|
||||
See [Hardware Compatibility](../Hardware-Compatibility).
|
||||
|
||||
@@ -20,10 +20,10 @@ psram: PSRAM ID read error: 0xffffffff
|
||||
cpu_start: Failed to init external RAM!
|
||||
```
|
||||
|
||||
## `0x00000002` Heap too small
|
||||
### `0x00000002` Heap too small
|
||||
The firmware failed to allocate enough memory. This most likely is a consequential error of a bad PSRAM!
|
||||
|
||||
## `0x00000004` Cam bad
|
||||
### `0x00000004` Cam bad
|
||||
The attached camera can not be initialized.
|
||||
This usually is because on of the following reasons:
|
||||
|
||||
@@ -31,7 +31,7 @@ This usually is because on of the following reasons:
|
||||
* The camera is not attached properly -> Try to remove and attach it again. Make sure you move the black part enough into the socket!
|
||||
* The camera or the camera cable is damaged
|
||||
|
||||
## `0x00000008` SD card basic check failed
|
||||
### `0x00000008` SD card basic check failed
|
||||
One or more basic SD card checks failed.
|
||||
|
||||
The following checks are performed during boot sequence:
|
||||
@@ -45,7 +45,7 @@ Detailed error indication (write, rerad or delete error) can be derived from bli
|
||||
|
||||
Recommendation: Reformat SD card and check again or try another SD card
|
||||
|
||||
## `0x00000010` SD folder or file presence check failed
|
||||
### `0x00000010` SD folder or file presence check failed
|
||||
One or more mandatory folders and/or files are missing on SD card.
|
||||
To have early indication that SD card is potentially ready for operation, some folder and files, which are mandatory are presence checked. This is not a 100% check and a successful test does not mean everthing is OK.
|
||||
|
||||
@@ -68,13 +68,13 @@ The following folders / files get checked during boot sequence:
|
||||
|
||||
Recommendation: Check logs and / or redo a Over-The-Air Update (OTA Update) to ensure proper SD card structure
|
||||
|
||||
# Non-Critical Errors
|
||||
## Non-Critical Errors
|
||||
Those Errors can be caused by an error during initialization. It is possible that the error has no impact at all or that a reboot solves it.
|
||||
|
||||
## `0x00000100` Cam Framebuffer bad
|
||||
### `0x00000100` Cam Framebuffer bad
|
||||
The firmware was unable to initialize the Camera Framebuffer.
|
||||
The firmware will continue to work, but other consequential error might arise.
|
||||
A reboot of the device might help.
|
||||
|
||||
## `0x00000200` NTP failed
|
||||
### `0x00000200` NTP failed
|
||||
The firmware failed to get the world time from an NTP server. The firmware will continue to work, but has a wrong time.
|
||||
|
||||
Reference in New Issue
Block a user