Look up an error from Serial File Manager or its firmware.
Connection and protocol
PROTOCOL_ERR
- Serial request line too long
- Malformed JSON
- Ignored malformed serial response
The serial data could not be read as a valid request or response.
What to try Use matching firmware and app versions. Close the Serial Monitor and try a direct USB connection.
HELLO_ERR
- Unsupported protocol version
- Unknown command
- Unexpected response
The board and app may be using different versions of the serial protocol.
What to try Check that the firmware and Windows app are from compatible releases.
SET_BAUD_ERR
- BAUD_CONFIRM_ERR
- Unsupported serial baud rate
- A baud-rate change is already pending
- Baud-rate confirmation does not match the pending rate
The board rejected the requested serial speed or could not confirm the switch.
What to try Reconnect at the default serial speed before trying a supported rate again.
Serial port is closed
- Not connected to the ESP32
- The ESP32 connection was lost
- The ESP32 disconnected before the drop completed
The COM port closed before the request or transfer completed.
What to try Check the cable, reconnect, and check transfer recovery before restarting the operation.
No response from the ESP32 before the serial request timed out
- The ESP32 did not send a binary transfer frame in time
The board did not reply before the app’s timeout.
What to try Confirm the COM port, close other serial tools, and check the USB cable and firmware. Try a small transfer after reconnecting.
Access denied
- UnauthorizedAccessException
Windows denied access to the COM port or to a local file or folder.
What to try For COM errors, close other apps using the port. For file errors, choose a destination you can write to.
Request id collision
The app could not track another serial request using the same ID.
What to try Disconnect and reopen the app. Record the error and app version if it recurs.
Storage and PC sessions
SESSION_BEGIN_ERR
- Board is not ready
- The board is not ready for a PC session
- Board reported state
The board could not start a PC session. The details may identify SD or LittleFS readiness.
What to try Check that the card is seated and readable, and that the matching firmware can mount LittleFS.
LittleFS is not ready; safe PC sessions require the fallback queue
- StorageLibrary could not start a host session
The firmware could not prepare safe storage for records generated during a PC session.
What to try Check the firmware build, partition layout, and mount status. Avoid formatting if it could erase queued records.
Begin a PC session first
- No active PC session
- Cannot sync while the PC owns the storage
The command was made in the wrong session state.
What to try Reconnect for file operations. Use Disconnect to end the PC session before attempting storage sync.
SESSION_END_ERR
- Could not release the StorageLibrary host session
- Queued-record sync is still pending
- SD card unavailable; queued sensor records remain safely in LittleFS
- queued sensor data remains held
- queued sensor data remains safely held
The session could not finish cleanup or the firmware could not replay queued records to the card yet.
What to try Check SD availability and allow the firmware to finish syncing. Keep LittleFS intact while records are queued.
Files and folders
LIST_ERR
- Folder not found
- Path not found
- File not found
- File not found for binary download
- The dropped file or folder no longer exists
- A selected upload item no longer exists
The item was moved, deleted, or is on a volume the app can no longer read.
What to try Refresh the file list and select the existing item again. Check the local source path for upload errors.
MKDIR_ERR
- Could not create folder
- Could not create destination folder
The firmware could not create the folder.
What to try Check that the parent exists, the name is valid, and the card has space and can be written to.
DELETE_ERR
- Cannot delete the SD root
- Invalid or protected SD path
- Invalid or protected destination path
- Choose a storage volume before changing files or folders
The request targets a protected, invalid, or virtual storage path.
What to try Open a writable volume and select an ordinary file or folder inside it.
RENAME_ERR
- MOVE_ERR
- COPY_ERR
- RENAME must keep the item in its current folder
- A folder cannot be moved into itself or one of its subfolders
- Choose a different folder to move this folder
- Copy a file or folder first
The source or destination is unsuitable for the requested operation.
What to try Use Rename in the current folder, Move for another folder, or select a source before Paste. Use a destination outside the source tree.
Enter a valid folder name
- Enter a name without slashes or reserved characters
- An ESP32 file or folder has a name that Windows cannot use
- The ESP32 returned a filename that Windows cannot use
- A folder already exists
- already exists on the ESP32
- A folder with that name already exists here
The requested name is invalid for the destination or conflicts with an existing item.
What to try Use a different Windows-compatible name or choose a different destination.
Transfers and recovery
GET_BEGIN_ERR
- GET_CHUNK_ERR
- Invalid chunk request
- File or offset is invalid
- Short read
- Base64 encoding failed
- The ESP32 reported an invalid file size
The download could not read or encode the expected data.
What to try Refresh the file listing and retry with a file that is no longer being written. Check the card and firmware if it recurs.
PUT_BEGIN_ERR
- Another upload is active
- Could not create staging file
- Invalid size or CRC
The firmware could not start staging the upload.
What to try Finish or cancel the current upload. Check space on the destination and try a small file.
PUT_CHUNK_ERR
- No matching upload
- Unexpected offset or invalid CRC
- Invalid base64 at offset
- Chunk CRC or length is invalid
- Staging write failed
The firmware rejected or could not write part of the upload.
What to try Reconnect and use the app’s resume or restart option. Check the card and USB cable if the error repeats.
PUT_COMMIT_ERR
- PUT_ABORT_ERR
- Whole-file verification failed
- Could not preserve prior destination
- Could not commit upload
The firmware could not verify, finish, or clean up the staged upload.
What to try Refresh and check the destination before retrying. Keep the original file until a complete copy has been verified.
CRC check
- A downloaded chunk failed its CRC check
- The complete file failed its CRC check
- The complete binary download failed its CRC check
- The complete downloaded file failed its CRC check
- A text-file chunk failed its CRC check
- The complete text file failed its CRC check
A checksum showed that received data differs from what was expected.
What to try Retry after checking the cable and card. Keep the source file and discard or replace any unverified copy through the app.
Binary transfer mode is not active
- The ESP32 does not advertise binary transfer support
- Received a frame from a different transfer
- Binary frame payload is too large
- ERROR frame
- FAST_FRAME_ERROR
- frame type 7
- NAK
The transfer mode, frame contents, or transfer ID did not match expectations. A NAK asks for missing or corrupt data again.
What to try Check that the firmware matches the app, reconnect, and retry a small file.
The ESP32 rejected a binary upload window
- The ESP32 acknowledged an unexpected upload position
- The ESP32 did not confirm the completed binary upload
- The ESP32 sent an unexpected frame during download
- The ESP32 sent an out-of-order or invalid download frame
- The ESP32 did not finish the binary download correctly
The app and firmware disagreed about transfer progress or completion.
What to try Reconnect and check the transfer recovery prompt. Verify the destination before attempting an overwrite.
Invalid upload resume position
- Unexpected upload start offset
- The ESP32 file changed between the transfer check and binary start
- The saved download recovery information does not match this file path
- The original PC file is no longer available
- The original PC file changed after the interruption
- The saved download has no destination path
- The saved transfer type is not supported for recovery
- No matching staged upload or offset
- Fast download must start at the beginning of a file
The saved transfer no longer matches the file or destination.
What to try Use the original unchanged file or start a fresh transfer to a known destination.
The ESP32 server does not support batch downloads yet
- The selected folders contain no files to transfer
- The batch archive did not contain
- The batch archive contains duplicate filenames
- The selected items contain duplicate or invalid name
A batch feature is unavailable or the selected items and archive entries do not match.
What to try Check the firmware version and try transferring the items one at a time.
Absolute path inside the batch archive
- Unsafe path inside the batch archive
- Path outside the chosen download folder
The app rejected an archive path that could write outside the chosen folder or could not be used safely.
What to try Refresh the board file list and try the affected files individually. Keep the original archive and error details if it repeats.
ZIP creation failed
- Upload failed
- Download failed
- Download failed after drop
- Rename failed
- Undo failed
- Redo failed
The app reports the operation that failed. The text after that label gives the underlying reason.
What to try Search for the rest of the message. For local I/O errors, check the source path, free space and write permissions.
Editor and application
The text editor supports files up to 10 MB
- Text editor failed
- Could not edit file
- File changed on ESP32
The editor reached its size limit, could not read or save the file, or detected a newer copy on the board.
What to try Use Download for files larger than 10 MB. If the file changed, check the newer copy before overwriting.
Operation in progress
- Transfer in progress
- Wait for the current file operation to finish
The app is already handling another file operation.
What to try Wait for the current operation to complete or use its Cancel control if available.
The download progress window did not start
- The download progress window could not start
- the selected COM port could not be remembered
A desktop window or local app setting could not be started or saved.
What to try Restart the app. If the connection succeeded, you can still select the port manually next time.
Upload cancelled
- Download cancelled
- Resume cancelled
- Batch download cancelled
The operation was cancelled. The message may indicate that the existing file or partial transfer was kept.
What to try Check the destination or use the resume prompt when you are ready.