USB problem on RPi pico
I have an issue with rshell that seems to be caused by the USB comms.
If I issue the command cp ports/rp2/examples/* /pyboard then rshell will hang, typically on the first file.
If I add some statements in the recv_file_from_host function in rshell (this is the part that runs on the pico) that opens a UART and logs some additional information to the UART, then the copies all succeed.
I tried adding 20 msec delays each place that there was log statement, but that doesn't seem to make things work either.
Sorry I don't have a simpler test case, but I figured I'd log the issue and see if I can create a simple program which reproduces the hang/crash.
Sometimes, things hang, and sometimes the serial port is forcibly closed (I suspect that this might be a crash on the pico side).
rp2 More USB woes
I raise this in case it sheds any more light on the USB issues.
I am using rp2-pico-20210209-unstable-v1.14-11-gc7aaee2b2.uf2.
I have a substantial uasyncio application developed on Pyboards and ported to the Pico. The test script outputs regular messages via print statements. The application maintains a heartbeat LED via a coroutine on the Pico.
It runs fine if I suppress all print output.
With print statements enabled it also runs so long as I periodically press a key on the keyboard (in rshell or in miniterm). If I don't, it runs for a while then stops. The heartbeat stops flashing until I press a key, when running resumes. The code has evidently stalled.
Unfortunately my attempts to create a trivial test case have so far failed. I have never encountered this behaviour on Pyboards, ESP8266 or ESP32.