Closed JonathanVusich closed 2 years ago
I have the same error when running against on an STM32WB55 with a daily build of 1.12, running on Windows 10.
I suspect the issue is that the source path for the copy looks incorrect on this platform when fed into rshell
. Using rshell
and directly connecting to the device:
firmware> ls /pyboard/stubs
Cannot access '/pyboard/stubs': No such file or directory
firmware> ls /flash/stubs
pyboard_v1_12/
firmware> ls /pyboard/flash/stubs
pyboard_v1_12/
Note that /pyboard/stubs
is invalid but flash/stubs
or /pyboard/flash/stubs
seem correct.
Dirty hack/workaround...modify pybwrapper.py:63 (installed here: [virtual-env]\Lib\site-packages\micropy\utils\pybwrapper.py
) from:
pyb_path = f"{self.pyb_root}{_path}"
to
pyb_path = f"/flash/{_path}"
micropy stubs create [COMX]
will then successfully complete.
A more correct solution appears to be to modify the return of rsh.find_serial_device_by_port()
or pyb_root()
.
Dirty hack/workaround...modify pybwrapper.py:63 (installed here:
[virtual-env]\Lib\site-packages\micropy\utils\pybwrapper.py
) from:
pyb_path = f"{self.pyb_root}{_path}"
to
pyb_path = f"/flash/{_path}"
micropy stubs create [COMX]
will then successfully complete.A more correct solution appears to be to modify the return of
rsh.find_serial_device_by_port()
orpyb_root()
.
This worked for me on the stock pyboard 1.1 with 1.13 firmware and windows 10.
Interesting as V1.13.0 has a [bug] (https://github.com/micropython/micropython/issues/6493) that prevents the subbing process to work. Are you sure that it was not a nightly build 103 or later?
If you need the stubs for 1.13.0-103 you can grab a copy at https://github.com/josverl/micropython-stubs
I tried creating stubs for my WiPy, but got this error message at the end. Any ideas on what may cause this?