I actually wonder why you’re using PowerShell in this case. There is no PowerShell code at all. It’s obviously an external executable with its command line arguments.
It tells you PowerShell cannot parse it. And that’s logic because it is not PowerShell code. You could try to tell PowerShell to stop parsing by adding the stop parsing operator --% right in front of all command line arguments.
I don’t understand what you mean by powershell code. I’m just trying to enter a command line that executes mklittlefs with some params. Isn’t this like a bash command line?
I’m getting the exact same error in a cmd window. So there is some parsing error in both powershell and cmd. I need help to understand it. Here is the command and result again (some was missing earlier) …/
"C:\Users\mark\.platformio\packages\tool-mklittlefs\mklittlefs" -b 8192 -p 256 --unpack "unpacked_fs" "C:\Users\mark\apps\tiny\downloaded_fs_0x300000_0xfa000.bin"
'-b' is not recognized as an internal or external command,
operable program or batch file.
I get a help menu from the program mklittlefs so I know it exists and runs. The problem command line is choking on the -b param. Is that not how windows handles params?
That’s not a PowerShell issue
I didn’t claim there was a problem with powershell. I fully understand the command has some syntax problem which is my fault. I ammanually entering this command in powershell, python is not running at all. The command was originally issued by python but I copied it.
Please tell me why it chokes on -b. Thanks in advance.