Yashraj, thanks for your reply. I don't want to be a grumpy bum, but I have spent a lot of time and effort and cash trying to get the TLE493D-A2B6 working, and I would like to say the following.
1. The datasheet could be improved a lot.
2. Simple example code would help a lot.
3. The reset code on your Github page is not finished !!!
4. But worst of all is the seemingly inconsistent behavior of the device. Let me explain.
On power up I reset the device by sending 0xFF 0xFF 0x00 0x00 with the start and stop conditions. (This is very badly explained in the datasheet imo btw.)
Next I configure the registers CONFIG and MOD1. I leave MOD2 alone as it has just one bit to change, and I can leave it at default.
The device is now working... I can read data from it, get the VERsion data etc.
However, if I add to my setup code a modification to MOD2, any subsequent reading of the device fails, except for one case that I have found.
If I set bit 7 (write 0x80) ---> subsequent reads fail.
If I send 0xFF, 0xE0, 0xC0, 0x00, these all cause read failure.
The only exceptions I can find is if I send 0x01 or nothing to MOD2. In these cases the device seems to work fine.
Now, perhaps I am doing something silly in my code, or perhaps MOD2 is broken, which would not surprise given how the poor design of the A1B6 device whose ADC randomly locked up requiring reset.
Very unhappy customer here.
So what exactly is hidden in MOD2 that would cause writes to it to break reads from the device?
