Make chip object less powerful to enhance multi-chip module operation
The much too powerful chip object might have been handy at the beginning; but creates troubles when command lines are shared for module operation.
The reason is, that only commands with variable data are filtered with the chip_id
feature. But, some commands are always executed (ECR
, global_pulse
, SYNC patterns
, ...). These are now executed during init
for each chip of a module for all chips repeatedly.
Especially, communication initialization is module business and not chip business.
We should not call spezialized inits in the chip object anymore and leave it to the scan_base
to initìalize a module. We can still keep the feature of single chip operation by putting the commands into something like: chip.init_stand_alone()
.