Skip to content

ymodem: a file in use is left out, the batch goes on - #64

Merged
JohnAmadis merged 1 commit into
mainfrom
fix/ymodem-skip-in-use
Oct 12, 2026
Merged

JohnAmadis merged 1 commit into
mainfrom
fix/ymodem-skip-in-use

Conversation

@JaxCalder

@JaxCalder JaxCalder commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Summary

This continues #63, which was merged before this commit was pushed.

A file that another program keeps open, such as the MP3 being played, cannot be opened for writing for as long as it is open. #63's 2 s of retries cannot help there, and the whole batch was cancelled at that file. Uploading a music folder stopped at the track that was playing.

Now such a file is received anyway, its blocks are not written, and the batch goes on. The file on the card stays as it was. The summary names what was not written:

ymodem: 1 file(s), 13 bytes; 1 not written (in use?): Alexander.mp3

dmod-boot's ymodem_send.py shows this and exits with an error (choco-technologies/dmod-boot#128).

Test plan

  • Builds for Cortex-M7
  • STM32F746G-DISCO: the MP3 being played plus a small file. The small file is written, the MP3 is reported as not written, and the sender exits 1. A track that was not playing (9.4 MB) is overwritten.

🤖 Generated with Claude Code

A file another program keeps open - the MP3 being played - cannot be
opened for writing for as long as it plays, and the whole batch was
cancelled at it. It is received and left out now (as it was on the card);
the batch goes on, and the summary names what was not written:

    ymodem: 1 file(s), 13 bytes; 1 not written (in use?): Alexander.mp3

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@JohnAmadis
JohnAmadis merged commit be93fc9 into main Oct 12, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants