Open mischif opened 5 months ago
causes the process to error out
Please give some more details about this means: what exactly do you do, and what error output do you see?
A soft reset (i.e. Ctrl-D in the REPL) will still disconnect the USB port each time, because the runtime USB interface objects have to all be freed and recreated.
A hard reset (i.e. plugging the rp2 in, or calling machine.reset()
) should come up immediately with the two CDC ports.
The only difference between boot.py and main.py is that the first time the device boots from a hard reset, it runs boot.py before it initialises USB. If you put the code in main.py instead of boot.py then the rp2 would first try create a device using the default USB interface, then immediately switch to the custom USB interface. This can show up on the host as connect/disconnect/connect cycle, or as an error depending on the timing.
With the init line commented out in boot.py:
mpremote fs cp boot.py :
mpremote run main.py
I see the print statements I expect:
9600/8N1 rts=False dtr=False
9600/8N1 rts=False dtr=False
[...]
With the init line uncommented in boot.py:
mpremote fs cp boot.py :
mpremote run main.py
I do not see the print statements I expect:
Traceback (most recent call last):
[...]
File "/home/mischif/.local/lib/python3.10/site-packages/serial/serialposix.py", line 549, in in_waiting
s = fcntl.ioctl(self.fd, TIOCINQ, TIOCM_zero_str)
OSError: [Errno 5] Input/output error
I get dropped back to the terminal, and connecting with mpremote a0
yields no output. Attempting to replace boot.py even after unplugging/replugging the pico also yields the above OSError; I have to drop to a shell and use os.unlink()
.
Ah snap, mpremote run
does a soft reset before it runs the provided file. Because boot.py has loaded the custom USB interface, it disconnects the USB port every time (then boot.py runs and adds it back, so you end up where you started.)
If you copy both boot.py and main.py to the filesystem then main.py works and you can use mpremote a0
to view the output, but you still can't use mpremote run
any more.
I think the fix for this will be the planned work to have mpremote detect when the USB port is in a disconnect/reconnect cycle, and recover from it instead of erroring out.
Is there a timeline for when the planned work might be finished?
Not at the moment, I'm afraid.
I assume this is impacting mpremote connect
as well (also including a soft reset)? Running similar as the OP above, I'm finding that I can connect directly to REPL by connecting to its COM port - but not using mpremote connect
.
I tested this on a pico running MP 1.23 and the latest release of usb-device-cdc.
boot.py:
main.py:
Running this as-is,
IFACE_TWO
does show up in main.py, but uncommenting the init function causes the process to error out. This discord post suggests you can callusb.device.get.init()
in boot.py, is this no longer true?