8000 mpremote cp -r command fails with "mpremote: cp: -r not specified; omitting directory" · Issue #17173 · micropython/micropython · GitHub
[go: up one dir, main page]
Skip to content

mpremote cp -r command fails with "mpremote: cp: -r not specified; omitting directory" #17173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
jabelone opened this issue Apr 23, 2025 · 0 comments
Open

mpremote cp -r command fails with "mpremote: cp: -r not specified; omitting directory" #17173

jabelone opened this issue Apr 23, 2025 · 0 comments
Labels
bug

Comments

@jabelone
Copy link
jabelone commented Apr 23, 2025 •
edited
Loading

Port, board and/or hardware

ESP32 on a custom designed ESP32-s3 board

MicroPython version

MicroPython v1.25.0 on 2025-04-15; Generic ESP32S3 module with ESP32S3

Reproduction

  1. install mpremote using the instructions here.
  2. run the command mpremote connect /dev/cu.usbserial-A5069RR4 cp -r configuration/ :configuration/ to recursively copy the configuration directory to the board.

Expected behaviour

I expected the command to recursively copy all files within the configuration directory over to the board to a folder located at /configuration, and to create that folder if it doesn't exist. This expectation comes from the documentation on this page.

mpremote cp -r utils/ :utils/ + soft-reset repl
Same as above, but update the entire utils directory first.

Observed behaviour

The tool returns the following error:

$ mpremote connect /dev/cu.usbserial-A5069RR4 cp -r configuration/ :configuration/
cp configuration/ :configuration/
mpremote: cp: -r not specified; omitting directory

Additional Information

Running on a M1 MacBook Pro, macOS Sequoia 15.3.2.
Using mpremote 1.25.0.

Code of Conduct

Yes, I agree
@jabelone jabelone added the bug label Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jabelone
0