Hi all,
>Datasheet says that 0x20, 0x23, 0x24, 0x43..0x45, and 0x4a..0x4d are
>all
>zero on the EMC2300. Most interesting would be 0x45, 0x4b, and 0x4d,
>which are initialized with 0x00 on the EMC2300 but 0xff for the
>EMC6D103S.
>all
>zero on the EMC2300. Most interesting would be 0x45, 0x4b, and 0x4d,
>which are initialized with 0x00 on the EMC2300 but 0xff for the
>EMC6D103S.
The datasheet lies :-)
They return the same as the EMC6D103S, i.e. 0xff for 0x45, 0x4b, and 0x4d.
>> > EMC2300 doesn't have all the voltage inputs that EMC6D103S has,
>> > so reports in0, in3 and in4 all as zero.
>>
>> Wouldn't this be good way to differentiate between the parts? What
>> values are returned by the EMC2300 for registers 0x20, 0x23, 0x24,
>> 0x44, 0x45, 0x4a, 0x4b 0x4c and 0x4d?
>> > so reports in0, in3 and in4 all as zero.
>>
>> Wouldn't this be good way to differentiate between the parts? What
>> values are returned by the EMC2300 for registers 0x20, 0x23, 0x24,
>> 0x44, 0x45, 0x4a, 0x4b 0x4c and 0x4d?
I thought of this, yes the missing voltage inputs all always return 0. I don't have an EMC6D103S handy though, so I'm not able to check its behaviour if those pins are either not connected or connected to ground. Presumably it could also return 0 in some cases so the detection would not be 100% foolproof?
I figured the safe option was to leave the extra inputs visible, as I didn't want to risk blocking access to them on parts where they're present.
>> BTW, if you could provide a register dump for the EMC2300 (using
>the
>> i2c-dev kernel driver and i2cdump tool from the i2c-tools package)
>that
>> would be appreciated.
I'll see if I can get this dump for you tomorrow.
Steve
_______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
