> CP/M programs often behave in ways which would be damaging to modern hardware -- endless input-checking loops at full CPU speed, for example. To be honest, I do not know if this kind of thing would be damaging to a Pico, but I don't want to risk it. CPICOM has a number of pause points built in, to give the microcontroller time to idle. These do slow the system down even further, and I'm not sure whether they're necessary.
This shouldn't be necessary on an MCU. Any kind of sleep call is probably just spinning the CPU anyway. There's often support for deeper power saving states, but MCUs are generally designed to be run full speed all the time.
This shouldn't be necessary on an MCU. Any kind of sleep call is probably just spinning the CPU anyway. There's often support for deeper power saving states, but MCUs are generally designed to be run full speed all the time.