On 28 March 2017 23:21, quoth Asier Tamayo: > After some debug, we have finally got the system working properly. We had > to define EC_SII_ASSIGN in the config.h file and recompile the EtherLab > master.
The right way to define this is not to modify config.h directly, but to specify --enable-sii-assign when running configure. (You can run configure --help to see the options.) > Does anyone know if defining EC_SII_ASIGN has any side effect? We have > found very little information about it. All this does is to assign control of the SII EEPROM to the slave device at specific points during the configuration process. This is required by some complex slaves that store additional settings in the SII EEPROM; it's disabled by default presumably just because it's a little slower and most common slaves don't need it. (There are some bugs in its implementation and it doesn't quite follow the standard, but that's mostly around treatment of the BOOT state and most people won't notice or care about that as it's only used for firmware programming.) _______________________________________________ etherlab-users mailing list [email protected] http://lists.etherlab.org/mailman/listinfo/etherlab-users
