I have an intel x86 desktop from which I ssh in to a zero w over wifi. The zero w power input I am not sure of but it is at least 2.5 A on the power in usb port. The zero w data usb port is connected to the pico micro usb port. The pico gets power and exchanges data on the zero usb data port. When I ssh from the intel desktop to the zero, from raspbian on the zero I can use the linux "screen" terminal emulator command to view /dev/ttyACM0 which shows me what is going on on the pico.
So I want to normally have the zero turned off. The pico does get power from the zero even when the zero is powered off.
If I boot the zero and never run screen then I can turn the zero on and off and all the while the pico runs normally.
If I boot the zero and run screen then when I turn the zero off the pico locks up. It could be a power supply thing but I doubt it.
The pico communicates with the intel x86 desktop (or another computer) over a socket over wifi. That's how I know the pico is locked up when the zero is off.
The pico and zero both run circuitpython. I think what is happening may be that the screen command "kills" the pico when screen gets the interrupt signal on shutdown. I wish it would just close /dev/ttyACM0. I think there is no problem when using "cat /dev/ttyACM0" instead of screen. If screen is sending CTRL-C to circuitpython on the pico that would explain it. How can I tell?
So I want to normally have the zero turned off. The pico does get power from the zero even when the zero is powered off.
If I boot the zero and never run screen then I can turn the zero on and off and all the while the pico runs normally.
If I boot the zero and run screen then when I turn the zero off the pico locks up. It could be a power supply thing but I doubt it.
The pico communicates with the intel x86 desktop (or another computer) over a socket over wifi. That's how I know the pico is locked up when the zero is off.
The pico and zero both run circuitpython. I think what is happening may be that the screen command "kills" the pico when screen gets the interrupt signal on shutdown. I wish it would just close /dev/ttyACM0. I think there is no problem when using "cat /dev/ttyACM0" instead of screen. If screen is sending CTRL-C to circuitpython on the pico that would explain it. How can I tell?
Statistics: Posted by garberw — Sun Oct 06, 2024 6:33 am