I'm thinking of adding this to my updated Master MOS versions as a *CONFIGURE option. I'm thinking have it repeatedly poll for Tube presence, rather than delay then test the once, so that it can accommodate longer Tube bootup time but equally can also get going as soon as the Tube is ready.
There'll have to be a timeout of some kind. The MOS can't poll indefinitely, because that would interfere with ordinary bootup if you've got *CONFIGURE TUBE but no copros, or *CONFIGURE EXTUBE but with only the internal copro present or vice versa. And it should really be optional, I think, because if you use the original copros then you never need the unnecessary additional waits.
How long does the PiTube take to boot? Will some fixed amount of time be sufficient, or will the number of seconds need to be configurable?
I'd be hoping to put in some kind of please-wait type of message, so you'd see something on screen while it's waiting for the 2nd processor to become detectable.
--Tom
There'll have to be a timeout of some kind. The MOS can't poll indefinitely, because that would interfere with ordinary bootup if you've got *CONFIGURE TUBE but no copros, or *CONFIGURE EXTUBE but with only the internal copro present or vice versa. And it should really be optional, I think, because if you use the original copros then you never need the unnecessary additional waits.
How long does the PiTube take to boot? Will some fixed amount of time be sufficient, or will the number of seconds need to be configurable?
I'd be hoping to put in some kind of please-wait type of message, so you'd see something on screen while it's waiting for the 2nd processor to become detectable.
--Tom
Statistics: Posted by tom_seddon — Tue Feb 04, 2025 1:48 am