Skip to content
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.

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

Problems when writing a single file from Windows with git bash #25

Open
justM4D opened this issue Apr 1, 2024 · 0 comments
Open

Problems when writing a single file from Windows with git bash #25

justM4D opened this issue Apr 1, 2024 · 0 comments

Comments

@justM4D
Copy link

justM4D commented Apr 1, 2024

I'm on Windows 10 and tend to use the git bash for everything I do cmdline wise.

Trying to flash the OTA Service pack, I found that due to the combination, it interprets the cc_filename as a whole (local) system path, instead of a target filepath.

image

This is reproducable, even when explicitly using "cc_filename=/sys/servicepack.ucf" as argument and with all kinds of combinations of single and double quotes around the name.

In all instances, git bash seems to expand the path and feeds it to the cc3200tool.
So this may be more of a git bash problem, but maybe something could be done to prevent this here as well?

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

No branches or pull requests

1 participant