From: Andrew Jamieson <andrew.jamieson_at_projectlab.net>
Date: Thu, 10 Oct 2002 12:05:31 +1000

This looks quite good, and falls basically in line with what I was thinking
about. All this discussion, and we've been thinking of the same circuit!
The only thing I would like to see added is a _power_ bus state, which is
where the Archos provides power to the remote. This would require the Achos
to occasionally enable the Idle state to allow comms (forcing the remote to
run from the battery), but this could be done frequently enough, and for a
short enough period, to be of draw only marginal current from the battery.
The remote could determine the difference between Idle and power by staying
in deep-sleep during the power mode, and waking up on the Px transition to
low. If then switches to Idle, and sends any data it needs to, waits for a
time-out on the Archos sending data, and switches to deep-sleep (at which
point the Archos switches to power).

Comments?

A

> Bus modes: Active (communication in progress), Idle (System running but
> not communicating), Deep sleep (disconnected or player powered down).
Received on 2002-10-10