Sat Oct 27 15:07:51 CEST 2007
make hub board, first for serial, then for I2C. the idea is that a hub
board can be placed inbetween a normal serial board and a PC host:
it's only goal is to provide control over the serial slaves.
the condition is that all slaves have identical code, which means that
host indeed can switch without problems between different slaves:
[ PC ] --- [ HUB ] === [ S1 ] === [ S2 ] === ...
* the interface that implements this should be transparent: there
should be no need for calling code on the hub directly. (except for
debugging the hub where the host has just hub's dictionary).
i suggest to do this we use the next slot of 16 interpreter commands
to pass through monitor commands to the hub.
again: if i manage to get things working this way (async serial hub) i
have no need for I2C to do networking.. in fact, in order to get I2C
working i better build a proper debug network!
and more: if i get this serial passthrough to work, moving to a
synchronous 1-wire approach should be no problem.
ok, i have 50 solutions now..
- make it work for serial = standard
- use serial to bootstrap 1-wire
- MAYBE use I2C after that, probably too complicated